Bug 1053594 - Other Linux installations are not added to Grub2 menus.
Summary: Other Linux installations are not added to Grub2 menus.
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: grub2
Version: 20
Hardware: x86_64
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Peter Jones
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-01-15 13:22 UTC by Jean Francois Martinez
Modified: 2015-06-29 14:28 UTC (History)
10 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-06-29 14:28:24 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
anaconda.program.log (10.99 KB, application/x-gzip)
2014-01-15 16:56 UTC, Jean Francois Martinez
no flags Details

Description Jean Francois Martinez 2014-01-15 13:22:50 UTC
Description of problem:
Other Linux distributions are seen in Anaconda's partitionning screen but when you reboot the only entries prent in Grub's menu are the Fedora 20 ones.  If then, ie aftyer rebooting on Fedora 20, you run grub2-mkconfig by hand then you get a correct, ie with entries for other distribution, menu.  This a _big_ public relaations problem: users willing to try fedora and unaware of Grub2's intrincacies will become angry, will find themselves unable to boot their other distro, will possibly reinstall it and will badmouth Fedora to anyone listening.


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


How reproducible:
Always

Steps to Reproduce:
1.  Install Fedora 20 (or Fedora 19)
2.  Reboot.  
3.  

Actual results:
Your other Linux installations don't show up in Grub menus.

Expected results:
To be able to boot my previous Linux installations right out of the box.

Additional info:
Could be that anaconda fails to run grub2-osprove or it could be that grub2-osprobe fails to mount other partitions when grub2-mkconfig is run by anaconda (SELinux problem?).

Comment 1 Vratislav Podzimek 2014-01-15 16:18:44 UTC
Please provide the /var/log/anaconda/program.log so that we can check it for potential errors when running grub2-mkconfig.

Comment 2 Jean Francois Martinez 2014-01-15 16:56:21 UTC
Created attachment 850591 [details]
anaconda.program.log

Comment 3 Vratislav Podzimek 2014-01-16 09:05:10 UTC
15:31:18,796 INFO program: Running... grub2-install --no-floppy /dev/sda
15:31:28,818 INFO program: Installation finished. No error reported.
15:31:28,836 DEBUG program: Return code: 0
15:31:29,036 INFO program: Running... grub2-set-default Fedora Linux, with Linux 3.11.10-301.fc20.x86_64
15:31:29,441 DEBUG program: Return code: 0
15:31:29,443 INFO program: Running... grub2-mkconfig -o /boot/grub2/grub.cfg
15:31:42,896 INFO program: Generating grub.cfg ...
15:31:42,897 INFO program: Found linux image: /boot/vmlinuz-3.11.10-301.fc20.x86_64
15:31:42,898 INFO program: Found initrd image: /boot/initramfs-3.11.10-301.fc20.x86_64.img
15:31:42,899 INFO program: Found linux image: /boot/vmlinuz-0-rescue-acd2095bd1cc47a1a396aafd46d84f14
15:31:42,900 INFO program: Found initrd image: /boot/initramfs-0-rescue-acd2095bd1cc47a1a396aafd46d84f14.img
15:31:42,901 INFO program: Found linux image: /boot/vmlinuz-0-rescue-61f6d7db65b244dbbe35f91e3331b140
15:31:42,901 INFO program: Found initrd image: /boot/initramfs-0-rescue-61f6d7db65b244dbbe35f91e3331b140.img

Cannot see any issues. Reassigning to grub. If anaconda does something wrong, please provide additional information and reassing the bug back to anaconda.

Comment 4 Mads Kiilerich 2014-01-26 12:50:03 UTC
Which other linux distros do not show up? Which filesystem stacks to they use?

It is probably the old issue where anaconda doesn't initialize raids and lvs it doesn't use and where os-prober thus can't see the disks.

(The boot entries it created would however probably not be very useful. It would try to create clever entries instead of using chainloading or configfile.)

Comment 5 Jean Francois Martinez 2014-01-26 20:34:34 UTC
It is a Centos 6.x.  Root filesystem is on a Logical Volume.  Boot filesytem is, of course, on a normal partition (from memory RHEL/Centos 6 ship with Grub 1)

Comment 6 Fedora End Of Life 2015-05-29 10:30:50 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 7 Fedora End Of Life 2015-06-29 14:28:24 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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