Re: Brocken Raid & LUKS

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Am 25.02.2013 19:31, schrieb Stone:
Am 24.02.2013 21:44, schrieb Phil Turmel:
On 02/24/2013 03:38 PM, Stone wrote:
if i can copy data. is there a way to check the files of consistency?
thx
I'm not sure which files' consistency you mean here...  the dd image in
your nas?  If so, you compute md5sums of each entire disk (rather time
consuming).

If you mean the data inside your encrypted array...  You can only use
whatever consistency mechanisms you already have for those files, like
"par2" Reed-Solomon checksums.

Phil
i have a backup from the three devices and i switched back to partion case 1 and i fire up the fsck:

fsck -y /dev/mapper/md2_nas
fsck from util-linux 2.19.1
e2fsck 1.41.14 (22-Dec-2010)
fsck.ext4: Group descriptors look bad... trying backup blocks...
The filesystem size (according to the superblock) is 1465134336 blocks
The physical size of the device is 1465133568 blocks
Either the superblock or the partition table is likely to be corrupt!
Abort? yes

thats all?
is my chance on case 1 over?
should i try a fsck -a?
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux RAID Wiki]     [ATA RAID]     [Linux SCSI Target Infrastructure]     [Linux Block]     [Linux IDE]     [Linux SCSI]     [Linux Hams]     [Device Mapper]     [Device Mapper Cryptographics]     [Kernel]     [Linux Admin]     [Linux Net]     [GFS]     [RPM]     [git]     [Yosemite Forum]


  Powered by Linux