Re: Brocken Raid & LUKS

[Stone <stone@heisl.org>]

Am 21.02.2013 18:17, schrieb Stone:
> Am 21.02.2013 17:54, schrieb Phil Turmel:
>> On 02/21/2013 11:51 AM, Stone wrote:
>>
>>> the dead-key was pressed
>>> here the output:
>>> root@bender:~# dd if=/dev/zero bs=1024 count=12 seek=1073006628
>>> of=/dev/sdc1
>>> 12+0 records in
>>> 12+0 records out
>>> 12288 bytes (12 kB) copied, 0,00019109 s, 64,3 MB/s
>>> root@bender:~# dd if=/dev/zero bs=1024 count=12 seek=1073101016
>>> of=/dev/sdc1
>>> 12+0 records in
>>> 12+0 records out
>>> 12288 bytes (12 kB) copied, 0,00017799 s, 69,0 MB/s
>>> root@bender:~# dd if=/dev/zero bs=1024 count=8 seek=1335739456 
>>> of=/dev/sdc1
>>> 8+0 records in
>>> 8+0 records out
>>> 8192 bytes (8,2 kB) copied, 0,000159338 s, 51,4 MB/s
>>> root@bender:~# dd if=/dev/zero bs=1024 count=8 seek=1346771164 
>>> of=/dev/sdc1
>>> 8+0 records in
>>> 8+0 records out
>>> 8192 bytes (8,2 kB) copied, 0,000161977 s, 50,6 MB/s
>>> root@bender:~# dd if=/dev/zero bs=1024 count=8 seek=1348581732 
>>> of=/dev/sdc1
>>> 8+0 records in
>>> 8+0 records out
>>> 8192 bytes (8,2 kB) copied, 0,000157825 s, 51,9 MB/s
>> Very good.
>>
>>> now i boot my server with a live cd and recreate my raid.
>>> if this was successfully i open the LUKS and check it.
>>> here my commands for this step:
>>> mdadm --create /dev/md2 --assume-clean --verbose --level=5
>>> --raid-devices=4 /dev/sdc1 /dev/sdd1 missing /dev/sdf1
>>> cryptsetup luksOpen /dev/md2 md2_nas
>>> fsck -n /dev/md2
>> Looks good.
>>
>> Phil
> i created the raid successfulle and the LUKS is open!
> this is the output of my fsck
> fsck -n /dev/mapper/md2_nas
> fsck from util-linux 2.19.1
> e2fsck 1.41.14 (22-Dec-2010)
> fsck.ext2: Superblock invalid, trying backup blocks...
> fsck.ext2: Bad magic number in super-block 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>
i coud try to restore the superblock. the filesystem is ext4....
is this the right way?
mke2fs -n -j /dev/mapper/md2_nas
mke2fs 1.41.14 (22-Dec-2010)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=128 blocks, Stripe width=384 blocks
366288896 inodes, 1465133568 blocks
73256678 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=0
44713 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
         32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 
2654208,
         4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968,
         102400000, 214990848, 512000000, 550731776, 644972544