Bug 124725 - Alternate GRUB entries removed by installer
Summary: Alternate GRUB entries removed by installer
Alias: None
Product: Fedora
Classification: Fedora
Component: mkinitrd
Version: rawhide
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Peter Jones
QA Contact: Mike McLean
Depends On:
TreeView+ depends on / blocked
Reported: 2004-05-28 20:47 UTC by Phil Schaffner
Modified: 2007-11-30 22:10 UTC (History)
0 users

Clone Of:
Last Closed: 2006-08-20 10:47:12 UTC

Attachments (Terms of Use)
grub.conf before and after upgrade (.FC1 and .FC2) (690 bytes, application/octet-stream)
2004-06-03 14:22 UTC, Phil Schaffner
no flags Details

Description Phil Schaffner 2004-05-28 20:47:26 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040510

Description of problem:
During upgrades from FC1 or RH to FC2 anaconda removes the GRUB
entries for the alternate installation partitions.  Leaves W2K or XP
entries in the new /boot/grub/grub.conf 

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.  Upgrade to FC2 with multiple instances of FC1 or RH.

Actual Results:  The grub entries for alternate installations of FC or
RH are removed.

Expected Results:  Only the entries for the root/boot partition[s]
being upgraded should be touched.  Alternate entries should be preserved.

Additional info:

Comment 1 Jeremy Katz 2004-06-01 19:52:25 UTC
Did you select upgrade boot loader or install new boot loader?  What
did your grub.conf look like before and after?

Comment 2 Phil Schaffner 2004-06-03 14:17:57 UTC
Selected to upgrade the boot loader.  Will create an attachment with
(reconstructed as closely as possible) FC1 grub.conf and post-upgrade
FC2 grub.conf.

Comment 3 Phil Schaffner 2004-06-03 14:22:17 UTC
Created attachment 100831 [details]
grub.conf before and after upgrade (.FC1 and .FC2)

Had to reconstruct the before (grub.conf.FC1) file from the one on the
alternate boot partition as the original was clobbered by the upgrade.

Comment 4 Jeremy Katz 2004-06-04 20:31:05 UTC
Were the other kernels in this config installed via RPM?  ie, do the
vmlinuz files still exist?

Comment 5 Phil Schaffner 2004-06-07 13:21:29 UTC
The kernel files in /boot on the alternate FC1 installation are still
present, both RPM installs and custom-build.  On the upgraded /boot,
the RPM-installed kernel files were removed, the custom-built ones are
still present, but all other FC1 GRUB boot stanzas for both partitions
were removed.  Only the FC2-installed biit entries and the one for W2K

Comment 6 Phil Schaffner 2004-06-07 16:37:58 UTC
Fat-fingered that one - should (obviously?) have been "boot" not "biit'.

Comment 7 Michal Jaegermann 2004-12-16 18:08:52 UTC
In a situation with multiple alternate installations I found
that the most practical way to organize booting is not to drop
everything into one "monster menu" but to have "the main" grub
menu which really is only a dispatcher and does
'chainload ...' for any of a "second tier" particular OS specific
loader installed on boot partitions for every (sub)installation.
For Linux this will be a separate for each installation copy of
grub; not even necessarily the same grub version.

Now any changes by update tools (anaconda, yum, whatever ... )
affect only what is relevant and these tools are not even aware of
other stuff.  As a side effect you may now have not only a default
boot entry in the top menu but also a default entry for every of
subinstallations. Much easier to maintain the whole structure as you
never have to worry what belongs to what.

Comment 8 Phil Schaffner 2006-08-20 10:47:12 UTC
OK - Lets get this one off the books.

Note You need to log in before you can comment on or make changes to this bug.