Am 24.02.2013 00:49, schrieb Phil Turmel:

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

quoted

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.

this was my secound time to buy WD devices. i bought 5 harddisk from the 
green series and all disks have very dangerous smart values. two devices 
i send back within one year :(
my new server have segate drives and i have with segate rarely problems 
over years and the performance is very good. i hope with this drives are 
that same.

quoted

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

quoted

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.

roger that.
i would do this:
parted /dev/sdc
unit s
resize 1 2048 3907029118
parted /dev/sdc unit s print -> to check my new settings
recreate the md2 device with chunk 512 and the order we find out.
open luks
check it with fsck -n and report you my (errors) result.

quoted

quoted

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.

this is the next step if you say step one is the wrong one.
parted /dev/sdc
unit s
resize 1 34 3907029118
parted /dev/sdc1 unit s print -> to check my new settings
recreate the md2 device with chunk 512 and the order we find out.
open luks
check it with fsck -n and report you again my (errors) result.

quoted

quoted

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

please verify my steps.
thx