During boot - System bootorder not found

Bug #1835639 reported by Marcel Beerli
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Ubuntu
Confirmed
Undecided
Unassigned

Bug Description

On HP Laptop Elitebook G1 after upgrade from 18.04 to 19.04 I get displayed very early on
System Bootorder not found, Initializing defaults (next line)
Creating boot entry "boot0001" with label "ubuntu" for file /EFI/ubuntu/shimx64.efi

then it waits 30sec and boots

Next boot it sais boot0002 and so on

rbeerli@GS6:~$ efibootmgr .v
BootCurrent: 0000
Timeout: 0 seconds
BootOrder: 0004
Boot0000* Notebook Hard Drive
Boot0001* Notebook Ethernet
Boot0002* ubuntu
Boot0003* ubuntu
Boot0004* ubuntu

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: gnome-terminal 3.32.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
Uname: Linux 5.0.0-20-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Jul 7 05:45:25 2019
ExecutablePath: /usr/lib/gnome-terminal/gnome-terminal-server
InstallationDate: Installed on 2019-04-03 (94 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
SourcePackage: gnome-terminal
UpgradeStatus: Upgraded to disco on 2019-07-06 (0 days ago)

Revision history for this message
Marcel Beerli (493pocbrcycmdw7yksonho9o2qzzq06652mtv6nw76-admin-d18ecat4t1b76tkfi3vttrkfngli4hci2jxl2sxy9j) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gnome-terminal (Ubuntu):
status: New → Confirmed
affects: gnome-terminal (Ubuntu) → ubuntu
Revision history for this message
Josep Pujadas-Jubany (jpujades) wrote :

We made a fresh 18.04 LTS Lubuntu 64 bits install + updates on Acer TravelMate B118-M (2019), booting with Secure Boot Disabled. Ok!

We clone this installation to Acer TravelMate B117-M (2018, 2017), booting with Legacy mode. We had the problem.

We can boot ours B117-M pressing Esc at boot. And we found as workaround:

sudo su
rm -R /boot/efi/EFI/BOOT
reboot

After that, we made the same change to the original (B118-M) and we booted without problems.

So, it seems like /boot/efi/EFI/BOOT folder is the cause of the problem. Machines are booting correctly from /boot/efi/EFI/ubuntu folder.

We have the rest of ours B117-M with 16.04 LTS. The folder BOOT doesn't exist on 16.04 installations.

efibootmgr outputs at:
https://drive.google.com/drive/folders/1IM0DAxhKIQphl8fWp13xIFhIvHKwr72_

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.