Red Hat Bugzilla – Bug 886270
Anaconda Grub2-mkconfig does not detect Fedora 17 on a second drive
Last modified: 2012-12-12 18:35:57 EST
Description of problem:
Two disk system. /dev/sda is empty (my test drive) and /dev/sdb is my regular drive
The regular drive has Ubuntu, and Fedora 17.
During the anacona installation, grub.cfg is created with
Fedora 18 first,
and no Fedora 17
manually running grub2-mkconfig from root picks up all three operating systems.
This may be a situation where anaconda has the wrong grub2-mkconfig or wrong os-prober software.
Version-Release number of selected component (if applicable):
Do a DVD installation according to my disk layout.
Steps to Reproduce:
Probably a duplicate of a bug I can't find. I'm sure Hedayat know where it is.
Is Fedora 17 installed on LVM or not?
Fedora 17 is installed with lvm ext4, as a vanilla DVD installation.
One quirk, it was a Fedora 16 upgrade to Fedora 17, using the pre and post upgrades.
But Ubuntu detected F17 and so did F18 using grub2-mkconfig
I have no idea if the os-prober used by anaconda from the installation DVD is as current as the os-prober version that installed.
I can always wipe the drive and redo the test.
Thank you for the description; the problem is not with the upgrade or os-prober version, it is about your Fedora 17 LVM partitions being inactive when the config is generated.
*** This bug has been marked as a duplicate of bug 825236 ***