Red Hat Bugzilla – Bug 444692
system won't boot after install
Last modified: 2008-06-03 10:21:28 EDT
Description of problem:
I created two software raid partitions on my scsi drives sdc and sdd. /dev/md0
contains the boot partition, /dev/md1 contains the root LVM. Both devices are
RAID 1, and the whole setup was created with the disk druid portion of anaconda.
After installation, the root partition cannot be found. I have to install grub
on hd2 and hd3. Then I need to modify /boot/grub/grub.conf because it points to
(hd1,0) instead of (hd2,0) or (hd3,0)
Version-Release number of selected component (if applicable):
Fedora 9 Preview, grub-0.97-33.fc9.x86_64
Every time. Correcting the bios drive order in the installer didn't help.
Steps to Reproduce:
1. Configure disks and reinstall
Either the grub console, or just the word "GRUB"
Needed to boot from the rescue CD to fix everything if the grub stage 1.5 didn't
Anaconda should load grub onto the MBR of the drive containing /boot, or should
prompt with more advanced menus if the user selects custom partitioning scheme.
This bug took a while to sort out.
If you do a custom partitioning scheme, then on the bootloader screen, there
already is the support for reordering the drives.
Unfortunately, this is an area of x86 hardware that really sucks and we
generally can't figure it out automatically :(
Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here: