LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Newbie (http://www.linuxquestions.org/questions/linux-newbie-8/)
-   -   After BIOS update, raid 1 root won't boot (http://www.linuxquestions.org/questions/linux-newbie-8/after-bios-update-raid-1-root-wont-boot-707279/)

Daemo 02-24-2009 08:51 PM

After BIOS update, raid 1 root won't boot
 
Hello

I had a perfectly normal Fedora 8 system running happily with a RAID1 / and /boot. After updating the BIOS to diagnose a potential disk problem, the boot sequence doesn't get very far.

The POST runs, the GRUB menu is displayed, and boots the default kernel. Then I get this:

Code:

Booting 'Fedora (2.6.26.8-57.fc8)'
root(hd0,0)
 Filesystem type is ext2fs, partition type 0xfd
kernel /vmlinuz-2.6.26.8-57.fc8 ro root=/dev/md1 rhdg quiet
  [Linux_bzImage, setup=0x3000, size=0x205da0]
initrd /initrd-2.6.26.8-57.fc8.img
Decompressing Linux... Parsing ELF... done.
Booting the kernel.
Red Hat nash version 6.0.19 starting...
mdadm: no devices found for /dev/md1
mdadm: no devices found for /dev/md2
EXT3-fs: unable to read superblock
mount: error mounting /dev/root on /sysroot as ext3: Invalid argument
setuproot: moving /dev failed: No such file or directory
setuproot: error mounting /proc: No such file or directory
setuproot: error mounting /sys: No such file or directory
switchroot: mount failed: No such file or directory

...and that's where it stops.

I only use md's. I do not use LVM.

I have booted with the rescue CD, and surprisingly it finds all the disk devices, assembles the raid devices and mounts everything just fine. The /etc/mdadm.conf is set up correctly, verified with a
Code:

mdadm --details --scan
From the rescue shell, I have tried running:
Code:

# chroot /mnt/sysimage
# /sbin/mkinitrd -v /boot/initrd-2.6.26.8-57.fc8.img 2.6.26.8-57.fc8

...and rebooted to exactly the same error.

I have tried reverting to the previous version of the BIOS to no avail. So I once again upgraded the BIOS and it now has the latest version.

Where do I go to from here?

Thanks for any help.

-D

Daemo 02-24-2009 09:27 PM

Okay, solved my own problem!

The issue was that I didn't specify that the initrd image should have the raid1 drivers preloaded. I needed to change the command from:
Quote:

/sbin/mkinitrd -v /boot/initrd-2.6.26.8-57.fc8.img 2.6.26.8-57.fc8
to
Quote:

/sbin/mkinitrd --preload=raid1 -v /boot/initrd-2.6.26.8-57.fc8.img 2.6.26.8-57.fc8
..and that did the trick.

-D


All times are GMT -5. The time now is 03:00 AM.