Hello,

 I'm novice to linux-raid and of cource felt into problems...
 What did i did?
    1. created /etc/raidtab
        raiddev /dev/md0
        raid-level              1
        nr-raid-disks   2
        nr-spare-disks  0
        chunk-size              64
        persistent-superblock   1
        device                  /dev/sda4
        raid-disk               0
        device                  /dev/sdb4
        raid-disk               1
    2. ran mkraid /dev/md0
        few experiments with: --realy-force
        [root@oratest /root]# mkraid --really-force /dev/md0
DESTROYING the contents of /dev/md0 in 5 seconds, Ctrl-C if unsure!
handling MD device /dev/md0
analyzing super-block
disk 0: /dev/sda4, 7638907kB, raid superblock at 7638784kB
disk 1: /dev/sdb4, 7638907kB, raid superblock at 7638784kB
bind<sda4,1>
bind<sdb4,2>
sdb4's event counter: 00000000
sda4's event counter: 00000000
md: md0: raid array is not clean -- starting background reconstruction
raid1: raid set md0 not clean; reconstructing mirrors
sdb4 [events: 00000001](write) sdb4's sb offset: 7638784
sda4 [events: 00000001](write) sda4's sb offset: 7638784
    3. cat /proc/mdstat
        says all is ok, will be rebuilded in such and such time.
    4. runing    e2fsck /dev/md0    i'm getting an error
        e2fsck 1.19, 13-Jul-2000 for EXT2 FS 0.5b, 95/08/09
The filesystem size (according to the superblock) is 1909726 blocks
The physical size of the device is 1909696 blocks
Either the superblock or the partition table is likely to be corrupt!
Abort<y>? yes

    Why superblock anounces as corrput? I can't mount my md0 on boot...
if i'am including it in /etc/fstab.

 Thank you

 Dovydas


Reply via email to