Am 21.02.2013 16:04, schrieb Phil Turmel:

On 02/21/2013 09:19 AM, stone@heisl.org wrote:

quoted

o greate idea :)

Whoops!  Not a great idea.  This is a member device.

quoted

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>

Ignore this.  As long as badblocks was using 4096, then the dd command
is correct.

Phil

dd if=/dev/zero bs=4096 count=1 seek=1073006628 of=/dev/sdc1
dd: `/dev/sdc1': cannot seek: Invalid argument
0+0 records in
0+0 records out
0 bytes (0 B) copied, 0,000493485 s, 0,0 kB/s

is there a problem with the bs parameter?
shoud i try dd if=/dev/zero bs=512 count=8 seek=1073006628 of=/dev/sdc1
?

thx.