Something has gone seriously wrong: import_mok_state0 failed

[Seth Arnold]

This may be related to bug 1798171.

I booted my new Lenovo X1 carbon 6th generation from a memory stick using:

$ ls -l disco-desktop-amd64.iso ; sha256sum ./disco-desktop-amd64.iso
-rw-rw-r-- 1 sarnold sarnold 2030043136 Mar 5 09:51 disco-desktop-amd64.iso
2fe72e17a2dc575ee90bd7f932e345975f04546ebe2154870198153f80de5336 ./disco-desktop-amd64.iso

I updated the BIOS using the Lenovo-supplied Windows BIOS update tools before booting Ubuntu.

The live session worked fine for a few days.

I started the installer, clicked boxes for turning on secure boot, typed in a secure boot password, and when I didn't see anything about ZFS in the disk partitioning page, I cancelled out of the installer.

The next reboot into the memory stick gave these messages before turning off:

Failed to open \EFI\BOOT\mmx64.efi - Not Found
Failed to load image \EFI\BOOT\mmx64.efi: Not Found
Failed to start MokManager: Not Found
Something has gone seriously wrong: import_mok_state0 failed
: Not Found

I cannot boot into the Ubuntu live memory stick any more. These messages repeat then the system turns off again. Windows still boots, which is encouraging, but I don't know how to use Windows.

Thanks

[Seth Arnold (seth-arnold)]

I can't boot arch on a memory stick, either, but there's no error message. It just returns to the uefi boot menu:

1f3541cbaa93ac64c9bf474ec7927d8274654ea01de046a75f39fdf972ad2a0d archlinux-2019.03.01-x86_64.iso

Thanks

[Seth Arnold (seth-arnold)]

Hmm, the 'current' symlink still points to the march 5 image: http://cdimage.ubuntu.com/daily-live/current/

Is there enough chance that a newer, not-current, image would let me boot again?

Thanks

[Seth Arnold (seth-arnold)]

The Lenovo setup interface has put Secure Boot and UEFI/Legacy Boot on different pages even though the two prompts interact with each other. Turning Secure Boot off on one screen will then let you switch to Legacy Boot, and then the memory stick will boot again. More tomorrow.

Thanks

[Mathieu Trudel-Lapierre (cyphermox)]

\EFI\BOOT\mmx64.efi should be on all the images; we should investigate this in case it was somehow dropped.

The issue seems to be that we immediately go apply the changes when people configure Secure Boot in the installer, but this requires MokManager to run at the very next boot -- if it's not available anywhere, we should fail more gracefully than we currently do though. Still, MokManager is supposed to be on the images.

[Steve Langasek (vorlon)]

This is probably fixed in the disco dailies (and in disco beta), which now include /EFI/BOOT/mmx64.efi on the image - a recent change. Is this problem reproducible for you with the current image?

If it is, we'll need to reassign it somewhere other than ubiquity.

[Seth Arnold (seth-arnold)]

Thanks for fixing up the missing /EFI/BOOT/mmx64.efi.

With the disco beta image I was able to re-enable the secure boot setting in my bios. I'll try to fiddle around with the installer and try to spot if the 'cancel' button doesn't undo pending changes. (But I'm not sure how to test that.)

Thanks

[Launchpad Janitor (janitor)]

[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.]