Red Hat Bugzilla – Bug 64609
redhat 7.3 upgrade from 7.2 messed up boot drive info
Last modified: 2008-05-01 11:38:02 EDT
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9) Gecko/20020408 Description of problem: I don't have all the details, but basically I had to modify the grub.config file and do a grub-install in order to get grub running properly after doing an upgrade form 7.2 to 7.3. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1.have your system boot from a scsi disk (sda) 2.install a promise technologies tx2 raid controller, have a disk running off of it. 3.upgrade from 7.2 to 7.3 Actual Results: the grub part of the install thought the boot disk was the ide drive I had hanging off my promis tx2 ata raid controller. Therefore, grub wasn't able to boot linux. (Had to create a boot floopy to fix the problem.) Additional info: my guess is that what ever software is used to determine which is the boot drive, didn't work well. I'm not sure if this is grubs fault or the redhat upgrade software's fault. I even tried the following. After doing the full upgrade and my system wouldn't boot, I reinstalled (or better said re-upgrade) redhat 7.3. (I forced the installation of the kernel packages since the grub part of the install needs this info to build a grub.config file) At the point of the installation where it asks what it should do regarding the boot loader, I chose the 3rd option, which was to completely reinstall grub. This didn't work. finally after booting from the boot disk, I modified the grub.config file by hand, did a grub-install and now my system is working
Created attachment 56685 [details] working grub.conf file, the one I edited by hand
Created attachment 56686 [details] broken grub.conf file. The one generated by the upgrade
*** Bug 64610 has been marked as a duplicate of this bug. ***
I experienced this as well... upgrading from a 7.2 system that I think had grub on it... I picked Upgrade Bootloader during the upgrade... and then I had Lilo. I could be mistaken... but in any event Lilo was the default bootloader. I did a grub-install. The /etc/grub.conf file was not valid. I had to edit it to get it working. Other upgrades worked fine as did a clean install. Sorry for the vague information but I don't have much to go on after an upgrade.
What does the /boot/grub/device.map contain? Also, unfortunately, PC hardware doesn't really expose what bios order is so this is hard to guess, so in future releases, we will have a way to change what the bios order of your drives is while installing.
[root@newadler root]# cat /boot/grub/device.map # this device map was generated by anaconda (fd0) /dev/fd0 (hd0) /dev/sda
This should be fixed with current rawhide-ish packages