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

[Alexander Dietrich]

I found the reason for this problem: it turned out to be the BIOS
setting "Boot Order Lock". After disabling it, I saw the above message
one more time, then Ubuntu started properly (and a new boot entry called
"ubuntu" appeared in the BIOS).

I don't know if this is possible, but it would be a good idea to detect
that the "ubuntu" boot entry wasn't actually created and display an
error message. If it's not possible, an additional hint about "Boot
Order Lock" or similar BIOS settings might be helpful (as well as
showing the message for more than a split-second).


** Package changed: ubiquity (Ubuntu) => grub2 (Ubuntu)

-- 
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:
  New

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