Red Hat Bugzilla – Bug 402151
grub-install can't install to MBR on cciss devices
Last modified: 2011-09-08 10:44:24 EDT
Description of problem:
While using the grub-install script, if specifying a base device
of '/dev/cciss/c0d0', the script reports an error, yet claims to have finished
[root@box ~]# grub-install /dev/cciss/c0d0
expr: non-numeric argument
Installation finished. No error reported.
This is the contents of the device map /boot/grub/device.map.
Check if this is correct or not. If any of the lines is incorrect,
fix it and re-run the script `grub-install'.
# this device map was generated by anaconda
Steps to Reproduce:
On a system with /dev/cciss devices (specifically an HP Proliant DL380) using
the grub-0.97-13 package, run:
The script runs, an error is displayed, and the script claims to exit
successfully. The result is that GRUB is not actually installed, or is not
installed to the MBR of the device provided.
GRUB should be installed as expected.
Proposed fix is attached as a patch.
Created attachment 270681 [details]
Patch to detect if disk and partition are the same, and install on MBR
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update
*** Bug 429187 has been marked as a duplicate of this bug. ***
Fixed in grub-0.97-13.1 .
The fix breaks dmraid; need to respin this with a slightly different solution.
Fixed again in grub-0.97-13.2 .
One workaround with grub-0.97-13 is to run "grub-install hd0". This works if hd0
is mapped to the correct cciss device in /boot/grub/device.map.
Verified with RHEL5.2-Server-20080402.nightly / grub-0.97-13.2
on a HP Proliant DL360 system.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.