Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: grub2-efi-x64 creates the file /boot/grub2/grubenv as a symlink to ../efi/EFI/ferora/grubenv. That file resides on a different partition and therefore the grubenv file cannot be read by grub2 when started by the legacy bios. This means that $kernelopts is not passed to the kernel, among which the "root=" parameter. Booting will therefore fail. Version-Release number of selected component (if applicable): grub2-efi-x64-2.02-81.fc30.x86_64 How reproducible: 100% Steps to Reproduce: 1. Upgrade an UEFI system to F30. 2. Boot the system via the legacy BIOS option. Actual results: You are dropped to an emergency shell because pivot-root fails. Expected results: Booting to a working system. Additional info: I only found this because the upgrade to F30 actually broke the UEFI boot option on my desktop. That will be another bugzilla, once I find out how and why.
Strike that remark about F30 breaking the UEFI boot option. This desktop machine was reinstalled last december and although all the grub2 efi pachages were installed, apparantly the legacy boot mechanism was the one really in use since the reinstall. I missed that.
This should had been fixed in grub2-2.02-72.fc30.x86_64, the grubenv is not replaced by a symlink when installing the grub2-efi-x64 package. *** This bug has been marked as a duplicate of bug 1687323 ***
Please reopen. This bug is definitely NOT a duplicate of bug 1687323. That bug was about a symlink to a non-existent or empty file, this bug is about a file being the symlink to a different partition, which is unreadable at boot time. I filed this bug against grub2-2.02-81.fc30.x86_64. The grubenv file in /boot/grub2/ definitely still IS a symlink after upgrading to this version, on all my efi systems. Please compare to bug 1622646. The file grub.cfg has been both in /boot/grub2/ and in /boot/efi/EFI/fedora for years. There were updating mechanisms in place to update both. That is because /boot and /boot/efi are different partitions on efi systems, as you know. This is the same problem. On an EFI system the grunenv file should be in both directories and both files should be updated by kernel install and systemd. Having one being a symlink to the other will never work for people switching between legacy and efi boot.
This message is a reminder that Fedora 30 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26. 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 '30'. 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 30 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.
This message is a reminder that Fedora 31 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24. 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 '31'. 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 31 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 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 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.