Summary: | "grub_is_shim_lock_enabled not found" boot error after upgrade to 182 from 181 | ||
---|---|---|---|
Product: | IPFire | Reporter: | Scott Beaman <sbeaman2010> |
Component: | --- | Assignee: | Arne.F <arne.fitzenreiter> |
Status: | CLOSED FIXED | QA Contact: | |
Severity: | Crash | ||
Priority: | - Unknown - | CC: | adolf.belka, dsihling, michael.tremer |
Version: | 2 | ||
Hardware: | x86_64 | ||
OS: | Unspecified | ||
Attachments: | Picture of screen on boot after upgrade from 181 to 182 |
Im not sure what happens here. Looks like grub or the uEFI/bios triggers a bug that grub think the system is Secure-Boot enabled. At my test i never run in such problems. But in the archlinux and ubuntu forums some users experience the same problem with grub-2.12-rc1. As workaround you can try to enable CSM and boot the system in legacy mode if this is supported. Tried a clean install of IPFire 182 from ISO. That failed to boot with the error, Unable to find valid image. This also sounds like a uEFI/bios bug in conjunction with the new grub. I will retest core182 with the official build image. (At my tests i never run in problems booting the installer from my nightly builds.) An FYI update: After more testing, yes Grub 2.12-rc1 appears to be the issue. Never could get 182 working regardless of UEFI status in the Bios. Just tested Upgrade from 181 to 183-master/02aa0f99 and install from ISO of core183-master/02aa0f99. TLDR - With UEFI enabled both fail. With UEFI disabled both work fine. For Upgrade from 181 to 183-master/02aa0f99 with UEFI enabled: - The upgrade completes without issue. - After reboot a blank screen is displayed. - The Grub menu never appears. (Seems to lockup trying to load Grub) - The good news, if you get the blank screen, you can disable UEFI in the bios and core183-master/02aa0f99 will then boot. For clean install from ISO of core182-master/02aa0f99: - Used: dd if=/dev/zero of=/dev/sda to clean the hard drive. - The install worked without issue up to the point the install asks to reboot. - After reboot the system reports, "A bootable device has not been detected" - The good news, if this happens, you can disable UEFI in the bios and core183-master/02aa0f99 will then boot and continue with the installation/configuration. Note: None of these issues occur on core181 and earlier. (In reply to Scott Beaman from comment #2) > An FYI update: > After more testing, yes Grub 2.12-rc1 appears to be the issue. Never could > get 182 working regardless of UEFI status in the Bios. > Core Update 182 has had the grub version reverted back to the one in Core Update 181 so that version would now be used for any update going to Core Update 182. Can you test out doing a fresh install of Core Update 181 and doing an update to Core Update 182 with the stable branch and confirm that it works for you now. Just tested upgrading from 181 to the new 182 with UEFI enabled. It WORKS!!!!!!!! Thank You. This issue can be closed as fixed. Should I move the testing with 183-master/02aa0f99 out of this issue and into its own issue report? (Since it is really a new issue) (In reply to Scott Beaman from comment #4) > > Should I move the testing with 183-master/02aa0f99 out of this issue and > into its own issue report? (Since it is really a new issue) Before you do that, I note that the master/02aa0f99 version is no longer listed in the master nightly runs list. Could you try a fresh install of Core Update 181 and then change to the Testing branch and do an Update to the latest Core Update 183 Testing. If you still have the same problem then I would suggest starting a new bug for that and we can close this one off with regard to Core Update 182. That we keep the two issues separate. Tested Upgrade 181 to 183-master/8c43d148 with UEFI enabled (Failed): - Used `dd if=/dev/zero of=/dev/sda` to wipe hard drive - Installed 181 from ISO - Upgraded to 183-master/8c43d148 - Rebooted - After reboot had error: "grub_is_shim_lock_enabled not found" Tested Upgrade 182 to 183-master/8c43d148 with UEFI enabled (Failed): - Used `dd if=/dev/zero of=/dev/sda` to wipe hard drive - Installed 181 from ISO - Upgraded to 182 - Rebooted - Upgraded to 183-master/8c43d148 - Rebooted - After reboot a blank screen with cursor was displayed. Grub menu never appeared. The original issue of this bug report has been resolved so this issue can be closed. As for the upgrade to 183-master/8c43d148 issues, do you prefer one or two bug reports. (Since they appear to be two symptoms of the same core issue with grub 2.12.) (In reply to Scott Beaman from comment #6) > > The original issue of this bug report has been resolved so this issue can be > closed. I will close it then. > As for the upgrade to 183-master/8c43d148 issues, do you prefer one or two > bug reports. (Since they appear to be two symptoms of the same core issue > with grub 2.12.) If there are two symptoms but they come from the same root cause then a single bug report would make sense. However if the root cause for the two symptoms is different, even though from the same package, then it makes sense to have two bug entries. You don't want to fix one root cause but the bug report has to stay open because the other root cause is not yet fixed. |
Created attachment 1438 [details] Picture of screen on boot after upgrade from 181 to 182 After upgrading, from 181 to 182, the firewall no longer booted. All that was on the screen was: Loading Linux 6.1.61-ipfire ... error: 'symbol_is_shim_lock_enabled' not found Loading initial ramdisk ... error: 'symbol_is_shim_lock_enabled' not found Press any key to Continue Hitting a key reboots and shows the same message. The version of grub installed, after the upgrade, was listed as a release candidate (.rc1). (Not a production release of Grub, if that matters) Tried a clean install of IPFire 182 from ISO. That failed to boot with the error, Unable to find valid image. Did a clean install of 181 from ISO and everything is working again. My fireinfo profile ID is: 5d978938cd9db8331ba7a9a5ea58cb727117d9e2 Processor: "Intel(R) Atom(TM) CPU D2500 @ 1.86GHz" RAM: 4GB