This bug was fixed in the package grub2 - 2.02~beta2-36ubuntu3.20 --------------- grub2 (2.02~beta2-36ubuntu3.20) xenial; urgency=medium
* debian/patches/linuxefi_fix_relocate_coff.patch: fix typo in relocate_coff() causing issues with relocation of code in chainload. (LP: #1792575) * debian/patches/linuxefi_truncate_overlong_reloc_section.patch: The Windows 7 bootloader has inconsistent headers; truncate to the smaller, correct size to fix chainloading Windows 7. (LP: #1792575) grub2 (2.02~beta2-36ubuntu3.19) xenial; urgency=medium * debian/patches/0001-i386-linux-Add-support-for-ext_lfb_base.patch: Add support for ext_lfb_base. (LP: #1785033) -- Mathieu Trudel-Lapierre <cypher...@ubuntu.com> Fri, 02 Nov 2018 13:08:47 -0400 ** Changed in: grub2 (Ubuntu Xenial) Status: Fix Committed => Fix Released ** Changed in: grub2-signed (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1792575 Title: Boot failure with efi shims from 20180913.0 Status in MAAS: Invalid Status in grub2 package in Ubuntu: Fix Released Status in grub2-signed package in Ubuntu: Fix Released Status in shim package in Ubuntu: Invalid Status in shim-signed package in Ubuntu: Invalid Status in grub2 source package in Xenial: Fix Released Status in grub2-signed source package in Xenial: Fix Released Status in shim source package in Xenial: Invalid Status in shim-signed source package in Xenial: Confirmed Status in grub2 source package in Bionic: Fix Released Status in grub2-signed source package in Bionic: Fix Released Status in shim source package in Bionic: Invalid Status in shim-signed source package in Bionic: Fix Released Bug description: [Impact] Chainloading grub via grub in a netboot context using MAAS's Boot to local disk feature. [Test cases] 1) Deploy UEFI system using MAAS 2) After deployment, have the system reboot to local disk (via netboot). [Regression potential] It is possible that the changes to chainloading logic that evaluates the sizes for various sections of code that gets copied to memory to load the next bootloader might fail to correctly evaluate the sections, or otherwise copy sections incorrectly, but this regression scenario is indistinguishable from the current case, there the system fails to load the next bootloader anyway. Error messages may vary, but the net result for a regression would be an incorrectly loaded bootloader, and thus error messages at boot from grub. --- We have had several nodes that had been deployed on Sept. 12 and were booting correctly fail to boot. On the console and during tracing we could see they were getting dhcp and pxe information, but then errored out with "relocation failed", dropping into a fallback grub menu with a Local boot option. After copying over bootx64.efi grubx64.efi from https://images.maas.io/ephemeral-v3/daily/bootloaders/uefi/amd64/20180906.0/ instead of 20180913.0/ and rebooting, boot would commence successfully. Hardware: Dell R640 maas 2.3.5-6511-gf466fdb-0ubuntu1~16.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1792575/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp