Re: Brocken Raid & LUKS

[Phil Turmel <philip@turmel.org>]

On 02/23/2013 05:26 PM, Stone wrote:

> i have a secound storage system with enough space to copy all there.
> this is my plan. to mount the device and copy as fast as i can all my
> data to my secound system and after this i take the cheap drives and
> drive with my car over it ;-)

Good plan for the first part.  But I wouldn't get rid of the cheap
drives.  They may lack features needed for best use in a raid array, but
they are fine for solo duties.  I have some similarly annoying Seagate
drives.  I use them one-by-one for off-site rotating backups.

> for x in /dev/sd[bce] ; do parted $x unit s print ; done
> Model: ATA WDC WD20EARS-00M (scsi)
> Disk /dev/sdb: 3907029168s
> Sector size (logical/physical): 512B/512B
> Partition Table: gpt
> 
> Number  Start  End          Size         File system  Name  Flags
>  1      34s    3907029118s  3907029085s                     raid
> 
> Model: ATA WDC WD20EARS-00M (scsi)
> Disk /dev/sdc: 3907029168s
> Sector size (logical/physical): 512B/512B
> Partition Table: gpt
> 
> Number  Start  End          Size         File system  Name  Flags
>  1      2048s  3907028991s  3907026944s
> 
> Model: ATA WDC WD20EARS-00M (scsi)
> Disk /dev/sde: 3907029168s
> Sector size (logical/physical): 512B/512B
> Partition Table: gpt
> 
> Number  Start  End          Size         File system  Name  Flags
>  1      34s    3907029118s  3907029085s                     raid
>>
>> The partition structure on /dev/sdc is causing the array to be too short
>> for the filesystem.  There are two possibilities:
>>
>> 1) The partition doesn't go far enough to the end of the disk,

For this, repartition /dev/sdc to start at sector 2048 and end at
3907029118.  Then re-create the array, open luks, and do "fsck -n" and
show the results.

>>
>> 2) The partition starts too far into the disk (move start sector to 34
>> like sdb and sde).

For this, repartition /dev/sdc to start at 34 and end at 3907029118.
This makes it match sdb and sde.  Then re-create the array, open luks,
and do "fsck -n" and show the results.

>> ps.  I hope this odyssey has emphasized to all lurkers how terrible it
>> can be to use "mdadm --create" without careful, thorough preparation.

> @ ps: sorry that i do this and thx for your help!

You're welcome.

Phil