In a dual-boot setup, the menu entries generated by grub2-mkconfig for other partitions will not list kernel names. So we get 4 identical lines: Fedora 25 (Workstation Edition) (on /dev/nvme0n1p7) Fedora 25 (Workstation Edition) (on /dev/nvme0n1p7) Fedora 25 (Workstation Edition) (on /dev/nvme0n1p7) Fedora 25 (Workstation Edition) (on /dev/nvme0n1p7) This is not helpful. We should include kernel version numbers so we can distinguish these lines. The attached patch to /etc/grub.d/30_os-prober is one possible fix. It only works if the other boot partition is also Fedora, but it has the advantage that the format matches that used for the default partition. It can be generalized or tweaked as desired.
This bug appears to have been reported against 'rawhide' during the Fedora 27 development cycle. Changing version to '27'.
Hi Jan I have /dev/sda --Fedora 28 Rawhide, /dev/sdc Fedora 27 KDE and /dev/sde F27 Gnome What I have noticed is the following: when I run grub2-mkconfig for my /dev/sde, it fails to show other Fedora distributions on /dev/sda and /dev/sdc. The other two distributions are not appearing. It seems to me that if one of the other Fedora Linux versions has an unclean (partition not marked as clean), os-prober fails. So, in my cases (trying to resolve issues) /dev/sda was not clean, mounting it and then runing grub2-mkconfig produces correct results. /dev/sdb -- my data disk had a partition that not marked as "clean" os-prober failed /dev/sdc os-prober had quit with /dev/sdb. The KDE version of Fedora on this disk was not picked up and as well, lost is the /dev/sda. /dev/sde --Fedora 27, my daily Fedora 27 is not showing /dev/sda or /dev/sdc Fedora Linux versions Yet with a new kernel installed, all Fedora installations appear. Since this is a grub2 bug report, also fix grub2-mkconfig for /etc/grub.d/15_ostree crashing grub2-mkconfig. Why do I run grub2-mkconfig, well after I install the latest kernel updates to the other two distributions, I need to update the grub.cfg for /dev/sde.
grub.cfg was missing entries for all but the booted distribution. From my Fedoraforum posting here is a bug resolution for grub2-mkconfig /dev/sda Fedora 28 Rawhide. /dev/sdb is purely my data Disk, , no operating system. /dev/sdc is where the second Fedora, F27 KDE was installed /dev/sdd is purely my data Disk2 /dev/sde is my primary Fedora 27 Gnome «-- the default daily distribution When running grub.cfg from /dev/sde, both rawhide and kde dists were skipped over. Grub menu did not show the either the Rawhide or the KDE distribution entries at all. Advice I got... mount the root partitions for the skipped over distributions and rerun grub2-mkconfig. I tested twice before mounting the KDE root partition. Thereafter, it was included in the grub.cfg. Ditto for the Rawhide root partition. I subsequently unmounted these two partitions and tested again, The kde and rawhide versions continued to be included in the grub.cfg All the / partitions are of type ext4 (in case that makes a difference). The system hardware is a non-uefi 8 gig 64bit. This problem leads me to suspect that on Fedora shutdown (gnome or kde), something is causing the problem that has the distribution's / partition set as not writeable. On booting, my own root partition is writable and grub includes it as it normally does, as first in the list. My next test will be to boot the rawhide and kde Fedoras one after the other, to perform a normal shutdown, and check the grub.cfg that is generated. Just waiting for a kernel update to have to do this test.
This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. 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 '27'. 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 27 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.
Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 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.