Red Hat Bugzilla – Bug 50988
Grub sometimes put on wrong disk for RAID configs
Last modified: 2007-04-18 12:35:30 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.01; Windows NT 5.0)
Description of problem:
Anaconda tends to put the disks for the /boot md device in the wrong order
in /etc/raidtab. Grub is then installed on raid-disk 0 (not /dev/hda, in
some cases) & the machine can't boot.
Steps to Reproduce:
1. Place /boot on an md device, RAID1
Actual Results: System is sometimes unbootable. Suppose /dev/md2
contains /boot. Anaconda tends to generate this (apparently bad) entry
Grub is subsequently installed on (hd1,0)
Expected Results: /etc/raidtab should probably always list /dev/hda as
This happened twice, on two seperate roswell installs. Generally it
happened when I started with no partition tables, but I have no recipe to
reproduce this one.
It happened 50% of the time for me (2 out of 4). Linux (grub, really) was
We (Red Hat) really need to fix this defect before next release.
Fixed in CVS so that we make sure that raid members are always sorted