After boot up I can't boot from RAID array.

webguyinternet · 10-05-2006, 02:41 PM

I have a Supermicro Superserver system (Pentium D) running Fedora Core 4 (2.6.16-1.2111_FC4). It is running a software RAID array (2 Drives). It was running great for several months but then last week the power supply failed on the unit and it brought the server down. I have now replaced the power supply with a new one and the system now boots correctly... till you get to the kernel bootup. Here is the error I recieve:

Code:

Filesystem type is ext2fs, partition type 0x83
kernel /vmlinuz-2.6.16-1.2111_FC4 ro root=/dev/md0 rhgb quiet
   [Linux-bzImage, setup=0x1e00, size=0x1841e1]
initrd /initrd-2.6.16-1.2111_FC4.img
   [Linux-initrd @ 0x37ec2000, 0x12dd1e bytes]

Uncompressing Linux... Ok, booting kernel.
PCI: Cannot allocate resource region 7 of bridge 000:00:1c.0
PCI: Cannot allocate resource region 8 of bridge 000:00:1c.0
PCI: Cannot allocate resource region 9 of bridge 000:00:1c.0
Rad Hat nash version 4.2.15 starting
EXT3-fs: unable to read superblock
mount: error 22 mounting ext3
ERROR opening /dev/console!!!!: 2
error dup2'ing fd of 0 to 0
error dup2'ing fd of 0 to 1
error dup2'ing fd of 0 to 2
switchroot: mount failed: 22
Kernel panic - not syncing: Attempted to kill init!

P.S. I have a very nice screen shot of this but the Bulletin Board will not allow me to post outside URl's. Very annoying.

I'm not sure if the PCI errors were there before but I'm thinking that the actual problem might actually be with the superblock error, not the PCI errors.

I can boot the system with the Fedora Core 4 Rescue CD and the entire filesystem mounts up correctly. I can see the contents of the RAID array and the /boot partition as well. I have forced a full "fsck" scan on all of the drives and all were clean.

How do I verify the integrity of the superblock and/or do you think that is where my problem lies

Electro · 10-05-2006, 03:04 PM

Go into rescue mode and make a device node named console in the device directory. It is major 5 and minor 1. It may correct other problems too.

webguyinternet · 10-06-2006, 10:22 AM

Ok... I tried that but no difference. Besides when I boot into rescue mode and mount the drives there the /mnt/sysimage/dev/console file already exists. I think the problem is that it cannot find the /dev/console device because it cannot mount the root "/" or /dev partition after it loads the kernel. Do you think that is right? I'm not necessartily an expert here but I think the issue goes back to the "superblock" error. If I can get that fixed It can mount the drives and proceed from there.