Raid, fsck, superblock could not be found

[rds <rustydstone@yahoo.com>]

Debian / sarge / testing

debian:~# uname -a
Linux debian 2.6.8-2-686 #1 Mon Jan 24 03:58:38 EST 2005 i686 GNU/Linux

Hi,

Have a server running a combination of raid1 and raid5. Whenever I reboot the
box I get the following error when the system is starting up:

...
Calculating dependencies... done
Loading modules...
  ide_cd
  ide_detect
FATAL: Module ide_detect not found.
All modules loaded
Capability LSM initialized

Checking all file systems...
fsck 1.35 (28-Feb-2004)
fsck.ext: Invalid argument while trying to open /dev/md1
/dev/md1:
The superblock could not be read or does not describe 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 e2fs with an alternative superblock
  e2fsck -b 8193 < >

fsck failed. Please repair manually.
CONTROL-D will exit from this shell and continue with system start up.


If I continue with CONTROL-D, the system will boot but /boot is not mounted and
/dev/md1 is not started and needs to be assembled.

# cat /etc/fstab
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
proc            /proc           proc    defaults        0       0
/dev/md1        /boot           ext3    defaults,errors=remount-ro 0       2
/dev/md2        /               ext3    defaults,errors=remount-ro 0       1
/dev/md3        none            swap    sw              0       0
/dev/hdc        /media/cdrom0   iso9660 ro,user,noauto  0       0
/dev/fd0        /media/floppy0  auto    rw,user,noauto  0       0

# cat /proc/mdstat 
Personalities : [raid0] [raid1] [raid5] 
md2 : active raid5 sda2[0] sdc2[2] sdb2[1]
      486351616 blocks level 5, 64k chunk, algorithm 2 [3/3] [UUU]
      
md3 : active raid5 sda3[0] sdc3[2] sdb3[1]
      1959680 blocks level 5, 64k chunk, algorithm 2 [3/3] [UUU]
      
unused devices: <none>

# mdadm --assemble /dev/md1 /dev/sd[abc]1
mdadm: /dev/md1 has been started with 3 drives.

# fsck.ext3 /dev/md1
e2fsck 1.35 (28-Feb-2004)
/dev/md1: clean, 27/10040 files, 17051/40064 blocks

So, it appears that fsck fails because /dev/md1 is not started when fsck runs
against it. But /dev/md2 does not appears to have any problems with fsck on
reboot.

Any ideas? Thanks


--




		
__________________________________ 
Do you Yahoo!? 
Yahoo! Small Business - Try our new resources site!
http://smallbusiness.yahoo.com/resources/