[Bug 1761895] Re: Post-install boot loop: "System BootOrder not found."

[Mathieu Trudel-Lapierre]

Sadly, I looked into that already, and we don't have that option: the
firmware does not let us know that it really didn't create the entry.

Closing as "Invalid" since the issue was reportedly fixed by disabling
Boot Order Lock.

** Changed in: grub2 (Ubuntu)
       Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to grub2 in Ubuntu.
https://bugs.launchpad.net/bugs/1761895

Title:
  Post-install boot loop: "System BootOrder not found."

Status in grub2 package in Ubuntu:
  Invalid

Bug description:
  Bionic Beaver Final Beta doesn't install properly on my computer
  (Thinkpad E480 with an NVMe SSD, no SATA disk). After finishing the
  installation, the machine repeatedly shows these messages and reboots:

  System BootOrder not found. Initializing defaults.
  Creating boot entry "Boot0000" with label "ubuntu" for file "\EFI\ubuntu\shimx64.efi"
  Reset System

  This happens both with automatic and manual partitioning. Setting the
  "UEFI/Legacy" switch in the BIOS to "Both" or "UEFI Only" also doesn't
  make a difference. (The installer doesn't boot at all when choosing
  "Legacy Only".)

  I checked the EFI partition and the file "\EFI\ubuntu\shimx64.efi"
  does exist.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1761895/+subscriptions