Description of problem: I am getting the following error when trying to boot into Win 10: error...../grub-core/command/search.c 296 no such device 8A70-33E6. error...../grub-core/fs/fshelp.c:257:file /efi/Microsoft/Boot/bootmgfw.efi No problem booting into Win 10 when I run grub2-mkconfig manually. The thread trying to sort out the problem is located here: https://ask.fedoraproject.org/t/anomalous-grub2-update-behavior-on-triple-boot-system-with-fedora-32-jam-dominant-system/7414 New to Fedora and have never fiddled with Grub2, so I can't provide any more info... Press any key... Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Hi, I'm the one trying to help the OP debug the issue in that Discourse thread, I thought I'd add some details to this report, because the thread has grown too long and the information is not in the most logical order. This is a UEFI installation and efibootmgr can boot windows successfully. When he reported the issue, he had these packages installed: grub2-common-1:2.04-18.fc32.noarch grub2-efi-ia32-1:2.04-18.fc32.x86_64 grub2-efi-ia32-cdboot-1:2.04-18.fc32.x86_64 grub2-efi-x64-1:2.04-18.fc32.x86_64 grub2-efi-x64-cdboot-1:2.04-18.fc32.x86_64 grub2-pc-1:2.04-18.fc32.x86_64 grub2-pc-modules-1:2.04-18.fc32.noarch grub2-tools-1:2.04-18.fc32.x86_64 grub2-tools-efi-1:2.04-18.fc32.x86_64 grub2-tools-extra-1:2.04-18.fc32.x86_64 grub2-tools-minimal-1:2.04-18.fc32.x86_64 The update to 2.04-19 did not change anything. I'm not sure if it was 2.04-18 that introduced the regression, it might have been an earlier version. grub-customizer was installed on the system, so I asked him to remove it as well as any files it had placed in /etc/grub.d/ and then reinstall the grub2-* packages, to restore the original scripts. That did not help either, but oddly, when the kernel was reinstalled, in the generated /boot/efi/EFI/fedora/grub.cfg the section that is usually created by the 30_os-prober script, still mentioned 30_os-prober_proxy. That file did not exist anymore though. Regardless of how the stanza is created, this is what it looks like: menuentry "Windows Boot Manager (on /dev/nvme0n1p2)" --class windows --class os $menuentry_id_option 'osprober-efi-8A70-33E6' { insmod part_gpt insmod fat if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root 8A70-33E6 else search --no-floppy --fs-uuid --set=root 8A70-33E6 fi chainloader /efi/Microsoft/Boot/bootmgfw.efi } (Why is there always an extra space between --set=root and the UUID in the first part of the conditional statement?) Would there be any output during the dnf transaction if something failed to run or if there was a problem with any hooks? His /etc/default/grub looks normal: GRUB_TIMEOUT="5" GRUB_DISTRIBUTOR="$(sed 's, release .*$,,g' /etc/system-release)" GRUB_DEFAULT="saved" GRUB_DISABLE_SUBMENU="true" GRUB_TERMINAL_OUTPUT="console" GRUB_CMDLINE_LINUX="rd.driver.blacklist=nouveau modprobe.blacklist=nouveau nvidia-drm.modeset=1 resume=UUID=6cc96bf2-900f-43b3-b02c-dba29e90b3cf rhgb quiet" GRUB_DISABLE_RECOVERY="true" GRUB_ENABLE_BLSCFG="true" There is BZ#1813213 detailing a very similar situation, albeit with version 2.02-78.el8_1.1, but the error message appears to be the same one: error: ../../grub-core/commands/search.c:296:no such device: B443-3F20 error: ../../grub-core/fs/fshelp.c:258:file `/EFI/Microsoft/Boot/bootmgfw.efi' not found.
This message is a reminder that Fedora 32 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25. 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 '32'. 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 32 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 package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.
Fedora 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 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.