Red Hat Bugzilla – Bug 184599
anaconda creates incomplete grub device.map
Last modified: 2008-03-10 21:19:32 EDT
Description of problem: I have tried a couple of times to install FC5test3 on my second hard drive (/dev/hdb). In both cases, the installer runs perfectly normally and installs everything properly, but when I then reboot the system, I'm presented with a broken grub installation. I believe this is because anaconda appears to be creating a /boot/grub/device.map file which is missing /dev/hdb. Grub therefore fails to install properly because it cannot find a BIOS map for the drive on which the new FC5 system has been installed. If I boot in rescue mode and run 'grub-install /dev/hda', it complains about the missing info for hdb. If I run 'grub-install --recheck /dev/hda' it re-generates the device.map file correctly (including hdb) and is able to install just fine. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Install FC5 on /dev/hdb 2. Reboot 3. Actual results: Grub is not installed Expected results: Bootable system Additional info:
Created attachment 125924 [details] device.map created by anaconda
Created attachment 125925 [details] device.map created by grub
This is a regression. I understand that only Red Hat can change Issue Tracker descriptions. Red Hat, please annotate this bug and its associated Issue Tracker with [REG].
George. Which Issue Tracker #?
I think this is fixed in RHEL5, but I am not sure if the fix made it in rawhide?
Fedora Core 5 and Fedora Core 6 are, as we're sure you've noticed, no longer test releases. We're cleaning up the bug database and making sure important bug reports filed against these test releases don't get lost. It would be helpful if you could test this issue with a released version of Fedora or with the latest development / test release. Thanks for your help and for your patience. [This is a bulk message for all open FC5/FC6 test release bugs. I'm adding myself to the CC list for each bug, so I'll see any comments you make after this and do my best to make sure every issue gets proper attention.]
The information we've requested above is required in order to review this problem report further and diagnose/fix the issue if it is still present. Since there have not been any updates to the report since thirty (30) days or more since we requested additional information, we're assuming the problem is either no longer present in the current Fedora release, or that there is no longer any interest in tracking the problem. Setting status to "INSUFFICIENT_DATA". If you still experience this problem after updating to our latest Fedora release and can provide the information previously requested, please feel free to reopen the bug report. Thank you in advance.