On Tue, May 19, 2020 at 08:59:46PM -0000, Lee Trager wrote: > Based on the MAAS logs the halt happens after the remote shim, grub, and > grub.cfg have been loaded. I didn't see anything in the console to show > grub running but it may have been cleared before I could see it.
> Console output: > Booting local disk... > Failed to open \efi\boot\grubx64.efi - Not Found > Failed to load image \efi\boot\grubx64.efi: Not Found > start_image() returned Not Found > Bootloader has not verified loaded image. > System is compromised. halting. Doesn't this output show that it has successfully chained to the local shim, since it's shim that is loading \efi\boot\grubx64.efi and those messages are from shim? What I don't currently understand is why this should behave any differently with or without SecureBoot enabled; that will need digging into. But the specific error "Not found" certainly implies there is a difference in the path resolution when secureboot is on. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1865515 Title: Chainbooting from grub over the network to local shim breaks chain of trust To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1865515/+subscriptions -- ubuntu-bugs mailing list email@example.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs