[Bug 2089320] Re: Secure boot variables full, unable to boot
Pedro Avalos
2089320 at bugs.launchpad.net
Fri Nov 22 20:52:21 UTC 2024
I don't see `tpm_measure_variable` stuff. I do see at least one
`mok.c:803:mirror_one_mok_variable() tpm_log_event(0x7186A718, 1, 14,
"MokListTrusted")->Volume Full`.
I've attached what I could capture from attempting to boot 24.04 on
capella. Let me know if you need anything else!
** Attachment added: "mok.log"
https://bugs.launchpad.net/ubuntu/+source/shim/+bug/2089320/+attachment/5839550/+files/mok.log
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to shim in Ubuntu.
https://bugs.launchpad.net/bugs/2089320
Title:
Secure boot variables full, unable to boot
Status in shim package in Ubuntu:
New
Bug description:
Deploying 22.04 fills up the secure boot variable Forbidden
Signatures. The system is still able to boot, but there are warnings
when booting. However, deploying with 24.04 seems to fill the secure
boot variable so much that the Ubuntu install is unable to start.
This behavior was noticed when deploying through MAAS to a Supermicro
- SYS-6028U-TR4+
(https://www.supermicro.com/products/system/2u/6028/SYS-6028U-TR4_.cfm?parts=SHOW)
system.
This is the output I was able to capture from the terminal:
```
Could not create MokListTrustedRT: Volume full
Something has gone seriously wrong: import_mok_state() failed: Volume full
```
The error messages were similar to the ones found in this upstream
issue: https://github.com/rhboot/shim/issues/654.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shim/+bug/2089320/+subscriptions
More information about the foundations-bugs
mailing list