Re: Brocken Raid & LUKS

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

 



On 02/22/2013 03:43 PM, Stone wrote:
> so hello again.
> the script was running and i looked at my logs.
> 
> this results i have
> with chunk-size 8,16,32,64,128 i have always the same error: Enter
> passphrase for /dev/md2: No key available with this passphrase.
> 
> the first time to open it is possible with chunk 256
> 
> i send you some logs from 256 and 512
> 
> at 512 i get the first results with checksum errors.
> i think the right size is 512?! but the filesystem is brocken?!

Damage near the beginning of your filesystem is expected, remember?
Lots of damage further in is not expected, once we have the right settings.

Very interesting.  Especially this with sdb-sdc-missing-sde:

> 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? no


I think this is the right device order, and the right chunk size.  It
also best matches what we know of your original setup.  But the total
size of the array device is 768 blocks smaller than it should be.  This
should be solved.

Please recreate the array with this combination, then show:

mdadm -D /dev/md2
mdadm -E /dev/sd[bce]1
cat /proc/partitions
for x in /dev/sd[bce] ; do fdisk -l $x ; done

Phil
--
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