Public bug reported:
This may or may not be relevant, but is supicious
I have a laptop runnning 26.04.1 with one of the PKFail keys (AMI "DO NOT
TRUST" = AMI Test PK)
Recently, fwupmgr updated
UEFI CA (2011 -> 2023)
and
UEFI dbx (20230501 -> 20260402)
Upon reboot, grub refused to load and I could not boot
The menu would not display, it simply immediately emitted:
Could not create MokListRT: VolumeFull
Could not create MokListXRT: VolumeFull
Could not create SBatLevelRT: VolumeFull
Could not create MokListTrustedRT: VolumeFull
Something has gone seriously wrong: import_mok_state() failed: VolumeFull
and then powered off
The machine had gotten systemd-boot-efi as part of the 26.04.1
update, so I tried to select the systemd "Linux Boot Manager" from BIOS to boot
This worked - it complained quickly in some red text but quickly booted
The machine has CSM disabled
The machine also has Secure Boot Disabled at BIOS level
Enabling Secure Boot from BIOS, grub behaved identically, systemd announced
security failure.
/sys/firmware/efi/efivars/ has none of the bloaty suspects; the largest two
files are:
-rw-r--r-- 1 root root 25992 Nov 4 00:36
dbx-d719b2cb-3d3a-4596-a3bc-dad00e67656f
-rw-r--r-- 1 root root 6142 Nov 4 00:36
db-d719b2cb-3d3a-4596-a3bc-dad00e67656f
Suspecting some kind of new grub problem introduced by the dbx update, I
tried
$ sudo grub-install --no-uefi-secure-boot
$ sudo update-grub
With that configuration, I can boot into grub and thus Ubuntu, as long as
system BIOS is set
to disable secure boot.
ProblemType: Bug
DistroRelease: Ubuntu 26.04
Package: grub-efi-amd64-bin 2.14-2ubuntu1
ProcVersionSignature: Ubuntu 7.0.0-42.42-generic 7.0.14
Uname: Linux 7.0.0-42-generic x86_64
ApportVersion: 2.34.1-0ubuntu0.1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: LXQt
Date: Wed Nov 4 08:56:51 2026
InstallationDate: Installed on 2020-06-04 (2345 days ago)
InstallationMedia: Lubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64
(20200203)
SourcePackage: grub2-unsigned
UpgradeStatus: Upgraded to resolute on 2026-10-23 (12 days ago)
** Affects: grub2-unsigned (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug resolute
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2173004
Title:
grub on EFI boot with secure boot disabled refuses to load with
"Something has gone seriously wrong" error; grub installed with --no-
uefi-secure-boot still works
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2-unsigned/+bug/2173004/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
