Bug 50800
Summary: | choosing grub with update leaves unbootable system | ||
---|---|---|---|
Product: | [Retired] Red Hat Public Beta | Reporter: | Gerald Henriksen <ghenriks> |
Component: | anaconda | Assignee: | Jeremy Katz <katzj> |
Status: | CLOSED RAWHIDE | QA Contact: | Brock Organ <borgan> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | roswell | CC: | rh |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2001-08-07 02:56:30 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Gerald Henriksen
2001-08-03 14:00:14 UTC
Sounds like you used to have LILO on /dev/hda and installed grub on /dev/hda1, so the old LILO still tried to run. Also the floppy disk error just sounds like you have a bad floppy I have always installed lilo on the MBR, and I specified grub to be installed on the MBR record also during the install process. Just now I tried "grub-install /dev/hda" which I take to be the equivalent of running lilo. I got the following error message: /dev/hdb5 does not have any corresponding BIOS drive and grub thus failed to install. I am guessing this same problem occurred when anaconda tried to install grub, but the install process did not give me any indication that their was a problem. Just for info hda1 is a primary partition with Win98, hda2 is extended, hda5 is Windows 2000, hdb1 is an extended partition, and hdb5 is my linux installation. This has been constant through several upgrades of Red Hat Linux. Floppy disk sounds like a disk error... all too common =\ What does your /boot/grub/grub.conf look like? (you should be able to boot with a boot image and using rescue mode if nothing else). We (Red Hat) should try to fix this for the next release. Note that grub apparently does not get installed at all as lilo still works. /boot/grub/grub.conf as requested: #boot=/dev/hda default=0 timeout=30 splashimage=(hd1,4)/boot/grub/splash.xpm.gz title Red Hat Linux (2.4.6-3.1) root (hd1,4) kernel /boot/vmlinuz-2.4.6-3.1 ro root=/dev/hdb5 initrd /boot/initrd-2.4.6-3.1.img title w2k rootnoverify (hd0,4) makeactive chainloader +1 title DOS rootnoverify (hd0,0) makeactive chainloader +1 If you add a line to /boot/grub/device.map of (hd1) /dev/hdb and run `/sbin/grub-install /dev/hda`, that should fix the problem. Fixed in CVS as well Problem is fixed. Thanks. *** Bug 51780 has been marked as a duplicate of this bug. *** Editing device.map and running '/sbin/grub-install /dev/hda' corrected my problem too (bug 51780). After I updated my RH9 system with the latest security patches (kernel), GRUB doesn't start anymore. All what I get is "GRUB _" on the screen and the PC stops. GRUB is on hdc2 (/boot). linux.bin in on hda1, launched by W2K boot manager. I have reinstalled GRUB many times (grub-install /dev/hdc2) with no result. Everything worked OK before update. How could I switch to LILO ? Dan |