Red Hat Bugzilla – Bug 126290
Grub fails to see past 8 drives
Last modified: 2007-11-30 17:07:02 EST
Description of problem:
Grub fails to see past 8 devices
Version-Release number of selected component (if applicable):
grub-0.93-4 (all versions)
Steps to Reproduce:
1. install as3 on dell poweredge 2650
2. install dell power vault 220s fully loaded with 14 drives
3. grub will fail and not re-install
device.map will not accept (hd0) /dev/sdo
grub-intall --recheck fails due to number of drives.
How does it fail?
grub will not be able to address any drives beyond 8 devices. If you
are hooking up an external array, grub will not locate the drive it is
installed on, due to drives being reordered. Starting the device.map
at the drive in which it is installed on (hd0) /dev/sdo also fails.
Claims invalid device.
The latest ROM update from DELL for the PERC controllers modify the
load order on the PowerEdge 2650's. This appears to resolve the issue
for now. To duplicate you may have to back rev the PERC controller to
an older ROM. GRUB however, will still locate only 8 drives.
What screen is showing you the 8 drives?
The source code.
/dev/sdi through /dev/sdp in this case, grub cant recognize.
Please show me the output of "grub-intall --recheck" when it fails.
I don't have the problem described here but I just came across this
remark in the Fujitsu-Siemens manual:
Linux drivers for PRIMERY servers, Revision 1.9, 23rd Aug 2004
pp 33 ff:
6.4.3. Booting fails on systems with GRUB and more than 9 hard disks.
Problem: The installation of the GRUB bootloader fails
Solution: GRUB supports only 9 (!) (sic) hard disk drives. Make sure no
more drives are specified in the GRUB device map. (...) Delete any lines
other than (hd0)-(hd8). Then re-run grub (...)
This bug is filed against RHEL 3, which is in maintenance phase.
During the maintenance phase, only security errata and select mission
critical bug fixes will be released for enterprise products. Since
this bug does not meet that criteria, it is now being closed.
For more information of the RHEL errata support policy, please visit:
If you feel this bug is indeed mission critical, please contact your
support representative. You may be asked to provide detailed
information on how this bug is affecting you.