Re: Brocken Raid & LUKS

Am 21.02.2013 14:29, schrieb Phil Turmel:

On 02/21/2013 04:42 AM, stone@heisl.org wrote:

quoted

i think this is the right way -> dd if=/dev/zero of=/dev/sdc1 bs=4096
count=1 seek=1073006628 (result of badblocks in my case 48 piece's)?

Yes, but for safety when typing a command line, I always put of= last.
Just in case I hit the <enter> key accidentally:

Thx for the hint ;-)

quoted

dd if=/dev/zero bs=4096 count=1 seek=1073006628 of=/dev/sdc1

quoted

and this for all badblocks?

Yes.

You should double-check the filesystem blocksize--it is usually 4096 but
ext4 allows you to change it.  "fsck -n" will report the total size of
the filesystem in its blocks.  Divide that into the total size of the
device to get the block size.

Phil

o greate idea :)
but i dont get a good result
fsck -n /dev/sdc1
fsck from util-linux 2.20.1
fsck: fsck.linux_raid_member: not found
fsck: error 2 while executing fsck.linux_raid_member for /dev/sdc1

fsck -n /dev/md2
fsck from util-linux 2.20.1
e2fsck 1.42 (29-Nov-2011)
fsck.ext2: Superblock invalid, trying backup blocks...
fsck.ext2: Bad magic number in super-block while trying to open /dev/md2

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>