[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Pb with sw RAID on boot



*** Hello list,

I've been mostly lurking on this list until last week when I decided to
setup software RAID on a test system and was confronted with a foolish
problem I can't seem to understand:

Here's the test setup:

raiddev /dev/md9
   raid-level                   1
   nr-raid-disks                2
   nr-spare-disks               0
   persistent-superblock        1
   chunk-size                   8
   device                       /dev/hda11
   raid-disk                    0
   device                       /dev/hdc11
   raid-disk                    1

Here's the fstab:

proc            /proc           proc    defaults        0       0
/dev/hda1       /               ext3    defaults,errors=remount-ro 0       1
/dev/hda3       /boot           ext3    defaults        0       2
/dev/hda10      /home           ext3    defaults        0       2
/dev/hda5       /root           ext3    defaults        0       2
/dev/hda8       /tmp            ext3    defaults        0       2
/dev/hda9       /usr            ext3    defaults        0       2
/dev/hda6       /var            ext3    defaults        0       2
/dev/hda7       /var/log        ext3    defaults        0       2
/dev/md9        /var/www        ext2    defaults        0       2
/dev/hda2       none            swap    sw              0       0
/dev/scd0       /media/cdrom0   iso9660 ro,user,noauto  0       0
/dev/fd0        /media/floppy0  auto    rw,user,noauto  0       0
/dev/sda        /media/usb0     auto    rw,user,noauto  0       0

The system runs on an IBM Blade server (HS20) and systematically drops to a
shell with a fsck error about superblock mismatch.

The kernel used is a 2.4.25-1-686-smp and the RAID is loaded as a module
(raid1 & md).

Result of lsmod:

Module                  Size  Used by    Not tainted
ext2                   53736   1  (autoclean)
raid1                  14384   1  (autoclean)
md                     61440   2  (autoclean) [raid1]
mousedev                4440   0  (unused)
keybdev                 2276   0  (unused)
hid                    21476   0  (unused)
input                   3872   0  [mousedev keybdev hid]
rtc                     7784   0  (autoclean)
usb-ohci               19944   0  (unused)
usbcore                66636   1  [hid usb-ohci]
tg3                    54124   1
dm-mod                 29992   0  (unused)
sr_mod                 14616   0  (unused)
sd_mod                 12076   0  (unused)
scsi_mod               97664   2  [sr_mod sd_mod]
ide-cd                 32512   0
cdrom                  29472   0  [sr_mod ide-cd]
ext3                   86216   8  (autoclean)
jbd                    46744   8  (autoclean) [ext3]
ide-detect               288   0  (autoclean) (unused)
serverworks             8412   1  (autoclean)
ide-disk               17184  11  (autoclean)
ide-core              115164  11  (autoclean) [ide-cd ide-detect serverworks
ide-disk]
unix                   17324   8  (autoclean)


What I have noticed at boot is that fsck checks the FS **before** md has
loaded the driver, so I understand it barks with an error: It tries to check
a FS that doesn't "exist".

I've used the
http://unthought.net/Software-RAID.HOWTO/Software-RAID.HOWTO.html#toc7 to
setup the RAID.

The only thing I can see is that "md" should maybe be compiled in the
kernel?

Any feedback is welcome. :-)

Zoran.



Reply to: