Description of problem: I broke my grub, so I made a chroot on an x64 fedora 27 live cd with /dev/ /proc/ /sys set up with --bind and /boot/ and /boot/efi from the physical partitions, and then I followed this guide to repair it: http://fedoraproject.org/wiki/GRUB_2#Updating_GRUB_2_configuration_on_UEFI_systems However, doing dnf reinstall grub2-efi shim and grub2-mkconfig as instructed at fedoraproject.org/wiki/GRUB_2 makes linux16/initrd16 boot entries. (which don't work) I can boot by manually editing on each boot in grub to linuxefi/initrdefi, but I suppose this should probably be fixed. Version-Release number of selected component (if applicable): grub2-pc-2.02-19.fc27 grub2-efi-x64-2.02-19.fc27 How reproducible: not sure, I don't break my boot THAT often Steps to Reproduce: 1. Reinstall grub2-efi shim from livecd 2. grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg 2. Reboot Actual results: doesn't boot, grub complains linux16 command is missing, manual edit to linuxefi/initrdefi fixes it Expected results: boots Additional info:
A kickstart install of Fedora 28 ends up writing incorrect values to the grub config file. To get the system to boot I had to manually change linux16 & initrd16 to linuxefi & initrdefi respectively via the grub boot menu editor. The file /boot/efi/EFI/fedora/grub.cfg is the one containing the incorrect entries. Once the system has booted, running the command: grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg rewrites the file correctly.
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.