[Bug 1747889] Re: (Acer Aspire V3-372) System not booting after update

[Yogesh Pathade]

I have got this as well with latest update on Ubuntu 17.10 last week.
I am running X1 Carbon Gen 5 really well until last week things got bad after running the software update.

The system keeps on rebooting with

System BootOrder not found. Initializing defaults.
Reset system

I have tried the boot-repair but didnt help. Tried to set the boot order
and boot in bios with no help.

Reinstalled the root but seems to be not helping in any way.


Here is the boot repair log
http://paste.ubuntu.com/%3Dd9NfmbjBrM/

Has anyone managed to boot back with any workaround?

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

Title:
  (Acer Aspire V3-372) System not booting after update

Status in shim-signed package in Ubuntu:
  Confirmed

Bug description:
  After installing the latest updates for Ubuntu 17.10, my computer
  (Acer Aspire V3-372) was no longer able to boot. It got stuck in a
  loop, displaying the following error message for a few milliseconds,
  then restarting again:

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

  I suspect this has something to do with the update to shim-signed
  1.33.1~17.10.1 as "Failure to boot or validate validly signed EFI
  binaries" is listed as a potential regression on
  https://bugs.launchpad.net/ubuntu/+source/shim/+bug/1708245/+editstatus

  There was also a very similar bug reported for Fedora 27:
  https://bugzilla.redhat.com/show_bug.cgi?id=1512410

  Selecting any (new) UEFI files as trusted did not solve the issue,
  neither did disabling secure boot or resetting the secure boot option
  in BIOS to factory default and it's still not working after adding
  EFI/ubuntu/shimx64.efi to trusted files again.

  The workaround I've found for now, is selecting "EFI File Boot 0"
  (which is the previously added trusted file) as primary boot device.
  But that's just a workaround, I think I should be able to just boot
  from my SSD as before.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1747889/+subscriptions