On 02/21/2013 01:29 PM, Stone wrote: > Am 21.02.2013 19:11, schrieb Phil Turmel: >> On 02/21/2013 01:08 PM, Stone wrote: >> >>> ok i have checked all superblocks but i get always the same message. >>> here one sample: >>> fsck.ext4 -n -b 644972544 /dev/mapper/md2_nas >>> e2fsck 1.41.14 (22-Dec-2010) >>> fsck.ext4: Invalid argument while trying to open /dev/mapper/md2_nas >>> >>> The superblock could not be read or does not describe a correct ext2 >>> filesystem. If the device is valid and it really contains an ext2 >>> filesystem (and not swap or ufs or something else), then the superblock >>> is corrupt, and you might try running e2fsck with an alternate >>> superblock: >>> e2fsck -b 8193 <device> >> You very likely have the wrong chunk size. >> >> Close luks, stop md2, and re-create with --chunk=64 >> >> And then try to fsck again. (Without -b at first.) >> >> Phil > ok. with --chunk=64 i cannot open the luks. > in witch steps (chunk) should i continue? That is a big surprise. The luks signature should not move with chunk size. Please use "mdadm -E /dev/sdc1" to recheck your data offset. If that wasn't it, please show the hexdump for the entire luks signature. I'd like to see its payload offset. Also, if you go back to --chunk=512, open the luks, you could run the following command to find possible superblock locations: hexdump -C /dev/mapper/md2_nas |egrep '^[0-9a-f]+30 .+ 53 ef' >sb.lst (May take a long time to read the whole array) 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
