Red Hat Bugzilla – Bug 494103
Anaconda does not detect older Fedoras (in grub.conf)
Last modified: 2009-06-02 10:02:20 EDT
Description of problem:
Installing F11 on a system with F10. I chose my to use my older /boot partition, and NOT to format it. F11 overwritten F10's grub.conf and did not append to it!
Version-Release number of selected component (if applicable):
Can only test once
Steps to Reproduce:
1. Install F11 on a system with F10, choose your existing /boot patition
2. F11 installer finishes, rebooting into the new system, the entries for F10 are lost!
F10 grub.conf entries are lost
F11 appends to F10's grub.conf and I can boot either F10 or F11
*** Bug 501063 has been marked as a duplicate of this bug. ***
Ahmed: so you are installing on top of F10 and choosing to use, but *not* reformat, the existing '/boot' partition. If that is the case, I don't believe you can expect any existing bootloader configuration to remain intact since anaconda will install a new bootloader.
If you wish to add entries for existing boot targets, you can do that in the anaconda bootloader screen, or by hand post-install.
I multi-boot all the time using a common /boot, so I'm quite familiar with how anaconda/grub handles installing the bootloader when there's already one installed and configured.
1. There's only one MBR, so there can be only one binary.
The stage files get overwritten to match what's in the MBR.
That's the way you *want* it to be.
2. The existing grub.conf and menu.lst are moved to grub.conf.rpmsave and
menu.lst.rpmsave. They're not deleted. menu.lst is a logical link, so
it doesn't make a lot of sense to mv it, but it doesn't hurt anything.
(Remember that grub.conf is really in /boot/grub, not in /etc, just
where you *want* it to be, eh?)
After you boot into the new OS, just run
cat grub.conf.rpmsave >> grub.conf
then vi it to get rid of the duplicate header lines and "rm *rpmsave"
Getting anaconda and/or grub to edit the existing grub.conf rather than mv it would be nice, but it works fine the way it is. That's also the way it's always worked since grub has been the bootloader. (lilo.conf really did go in /etc, but you could pull some link fakery like grub does now, too.)
If the old grub.conf really did get blown away, there'd be a lot of angry folks racing you to file a bug on it. As it is, I'd say this one is a WORKSFORME (alpha through preview so far).
comment #3 sounds pretty much right.
Another thing you could do (What I do in my installs) is to tell anaconda not to install a bootloader. This will skip the installation of the grub package and avoid all the grub.conf.rpmsave stuff. You do have to edit the grub.conf with the parameters of your new install though.
+1 for WORKSFORME
Closing this bug out. Comment#3 and Comment#4 offer recommendations to retain any existing bootloader configuration when reinstalling without formatting '/boot'.
Please file a new bug should any problems be encountered while testing the suggested solutions.