"System BootOrder not found. Initializing defaults" can be worked around with "Boot from file" #563

eriksjolund · 2020-07-08T16:54:03Z

On a newly bought laptop HP Elitebook 850 G6 (without Windows but with FreeDos) I can boot

CentOS-8.1.1911-x86_64-dvd1.iso

from a USB stick just fine but when I try boot

fedora-coreos-32.20200601.3.0-live.x86_64.iso

this text is shown on the monitor

System BootOrder not found. Initializing defaults.
Creating boot entry "Boot0009" with label "Fedora" for file "\EFI\fedora\shimx64.efi"

Reset System

and after about one second the computer is automatically rebooted.

When I enter the BIOS I can see that the setting: Configure Legacy Support and Secure Boot is set to Legacy Support Disable and Secure Boot Disable.

(That setting has not been changed since the computer came delivered)

It is possible to change that setting to either:
Legacy Support Enable and Secure Boot Disable
or
Legacy Support Disable and Secure Boot Enable

If I change to
Legacy Support Enable and Secure Boot Disable
a warning is shown that other settings in the BIOS need to be changed (for instance regarding Thunderbolt security) so I decided not to change that setting.

I restarted the computer and and pressed F9 to enter the Boot Menu.
Previously I had selected

UEFI - Kingston DataTraveler 3.0 60A44 ...

but this time I chose

Boot from file

which gave me the possibility to navigate in the file system down to the file shim64.efi

Select PciRoot(0x0)/Pci(0x14,0x0)/USB(0xC,0x0)/HD(1,MBR,0x6E2CF7 ....
Select EFI
Select fedora
Select shimx64.efi

Now Fedora CoreOS booted up just fine.

Is this a bug or expected behavior?

How the 2 USB sticks were created:

To write the 2 USB sticks, I used the commands

sudo su -c "cat /tmp/fedora-coreos-32.20200601.3.0-live.x86_64.iso > /dev/sda"

and

sudo su -c "cat /tmp/CentOS-8.1.1911-x86_64-dvd1.iso > /dev/sda"

on a Fedora 32 computer.

The text was updated successfully, but these errors were encountered:

junjiequ · 2020-07-09T12:24:01Z

+1
I have exactly the same question.
I did almost the same to install the live image on a HP machine.
What I did differently was I flashed the ISO file using balenaEtcher from a windows client.

cgwalters · 2020-07-09T15:05:38Z

I see this too on a recent Lenovo laptop. I am not sure if it's related, but the laptop also emits an incredibly loud beep when this happens.

jlebon · 2020-07-09T19:00:59Z

Might be unrelated, though an issue with the same final error message showed up yesterday too in Silverblue: https://bugzilla.redhat.com/show_bug.cgi?id=1855116.

dustymabe · 2020-11-11T17:21:02Z

Anyone still able to reproduce this? When it does happen, does it happen every boot or is it intermittent?

alexhochreiter · 2020-12-10T19:25:34Z

Same error after live installation here on my second hand Thinkpad t560.
Secureboot was disabled in the bios.
Steps to reproduce on my machine:

Boot Fedora 33 Workstation from USB.
Create GPT partition table on hard disk.
Allow Installer to automatic partition layouting with personal encrypted data.
Installation finishes, clicks shutdown, removes usb drive, powers on laptop and is never able to boot.

bgilbert · 2020-12-10T19:42:46Z

@axed Are you installing Fedora CoreOS or Fedora Workstation?

alexhochreiter · 2020-12-10T19:46:56Z

@bgilbert Workstation - aaah sorry, i must have overread that this thread was CoreOS specific after digging through so many pages looking for a solution. But since workstation isnt working, i can take the time to test Fedora CoreOS as well... just to see if the result is the same
Update on the CoreOS 32.20201104.3.0 Image:
Can't even get it to boot from the USB on my t560 - boots just fine on my x230.
No error message no nothing, just quickly returns to the laptop's boot menu.
BIOS/UEFI Settings:

Secure Boot          [Disabled]
Platform Mode        [Setup Mode / User Mode] (tested both)
Secure Boot Mode     [Custom Mode / Standard Mode] (tested both)

Update 2:
I disabled the TPM Chip, now Workstation prints OP's error message just like previously, but continues to boot normally. Fed. CoreOS still doesnt even boot from usb.

eriksjolund · 2020-12-10T20:37:29Z

I made a new test on the same HP Elitebook 850 G6 laptop as in #563 (comment) but with the latest next release. The same thing happens as before. It happens every time. (At least the three times in a row that I now tested). A few months ago I tested it many more times. Also then it happened every time.

[erik@laptop ~]$ coreos-installer download -s next -f iso
gpg: Signature made Tue 01 Dec 2020 10:30:36 PM CET
gpg:                using RSA key 963A2BEB02009608FE67EA4249FD77499570FF31
gpg: Good signature from "Fedora (33) <[email protected]>" [ultimate]
> Read disk 750.0 MiB/750.0 MiB (100%)   
./fedora-coreos-33.20201130.1.0-live.x86_64.iso
[erik@laptop ~]$

I wrote the iso file to a USB stick

[root@laptop ~]# cat ~erik/fedora-coreos-33.20201130.1.0-live.x86_64.iso > /dev/sda
[root@laptop ~]# echo $?
0
[root@laptop ~]#

The new test:

The HP Elitebook 850 G6 is turned off
Insert the USB stick
Press the power button
Press F9 to get the boot menu
This text is shown:
(a bit abbreviated)

Boot Menu

 * UEFI - Fedora
 * UEFI - Kingston DataTraveler 3.0 60A44.............
 * UEFI N/W - IPV4 Network - .....
 * UEFI N/W - IPV6 Network - .....
 * Boot from file

Press arrow down
Press enter to select UEFI - Kingston DataTraveler 3.0 60A44
This text is shown on the monitor for 1 second

System BootOrder not found. Initializing defaults.
Creating boot entry "Boot0009" with label "Fedora" for file "\EFI\fedora\shimx64.efi"

Reset System
and after about one second the computer is automatically rebooted.

The computer is automatically rebooted.

Regarding the beep mentioned in another comment

I don't hear any beep as described in #563 (comment)

There are some audio related settings in the BIOS:

Audio Device
Microphone
Internal Speakers

sar · 2021-04-23T01:13:15Z

Anyone still able to reproduce this? When it does happen, does it happen every boot or is it intermittent?

Seems like it's still there, was able to replicate this on a Mac using FCOS revision 33.20210328.3.0 which hits Boot0009: BootOrder not found.

I can access the GRUB prompt, on Mac it defaults to the path /EFI/BOOT/BOOTX64.EFI.

boniek83 · 2021-05-18T02:33:43Z

Still there:
33.20210426.3.0 iso "burned" using dd or rufus (no difference)
HP 600 G4, UEFI boot, latest bios (2.15)
Fedora Server 34 boots normally though.

dustymabe · 2021-05-18T15:24:11Z

Thanks for the data points. Please keep reporting when you hit this and on what hardware. Eventually we'll get a developer with some hardware that can reproduce and be able to drill down to where the problem actually is.

eriksjolund · 2021-12-07T20:25:43Z

It's not reproducible with fedora-coreos-35.20211203.1.0-live.x86_64.iso.
(I use the same laptop as in the original bug report #563 (comment))

To me it seems the bug has been fixed.

dustymabe · 2021-12-07T21:02:55Z

Thanks @eriksjolund - I think this may be a result of #946 (comment) (implemented in coreos/coreos-assembler#2435). @bgilbert - does that sound right?

bgilbert · 2021-12-07T21:42:07Z

Awesome, thanks for the update. Yup, that sounds right. It turns out that shim's fallback.efi was adding the CD to the boot order, and on systems with a TPM, rebooting the machine afterward.

eriksjolund mentioned this issue Jul 9, 2020

How to boot a Fedora CoreOS Live USB stick without the workaround using "Boot from file"? eriksjolund/install-linux-hp-elitebook-850-g5#11

Closed

dustymabe mentioned this issue Sep 1, 2021

Stale UEFI boot entry left behind after reprovisioning #946

Open

dustymabe closed this as completed Dec 7, 2021

rgl mentioned this issue Aug 10, 2022

Execute wipefs before ignition in live iso environment coreos/coreos-installer#947

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

"System BootOrder not found. Initializing defaults" can be worked around with "Boot from file" #563

"System BootOrder not found. Initializing defaults" can be worked around with "Boot from file" #563

eriksjolund commented Jul 8, 2020 •

edited

Loading

junjiequ commented Jul 9, 2020

cgwalters commented Jul 9, 2020

jlebon commented Jul 9, 2020

dustymabe commented Nov 11, 2020

alexhochreiter commented Dec 10, 2020 •

edited

Loading

bgilbert commented Dec 10, 2020

alexhochreiter commented Dec 10, 2020 •

edited

Loading

eriksjolund commented Dec 10, 2020 •

edited

Loading

sar commented Apr 23, 2021

boniek83 commented May 18, 2021 •

edited

Loading

dustymabe commented May 18, 2021

eriksjolund commented Dec 7, 2021 •

edited

Loading

dustymabe commented Dec 7, 2021

bgilbert commented Dec 7, 2021

"System BootOrder not found. Initializing defaults" can be worked around with "Boot from file" #563

"System BootOrder not found. Initializing defaults" can be worked around with "Boot from file" #563

Comments

eriksjolund commented Jul 8, 2020 • edited Loading

How the 2 USB sticks were created:

junjiequ commented Jul 9, 2020

cgwalters commented Jul 9, 2020

jlebon commented Jul 9, 2020

dustymabe commented Nov 11, 2020

alexhochreiter commented Dec 10, 2020 • edited Loading

bgilbert commented Dec 10, 2020

alexhochreiter commented Dec 10, 2020 • edited Loading

eriksjolund commented Dec 10, 2020 • edited Loading

Regarding the beep mentioned in another comment

sar commented Apr 23, 2021

boniek83 commented May 18, 2021 • edited Loading

dustymabe commented May 18, 2021

eriksjolund commented Dec 7, 2021 • edited Loading

dustymabe commented Dec 7, 2021

bgilbert commented Dec 7, 2021

eriksjolund commented Jul 8, 2020 •

edited

Loading

alexhochreiter commented Dec 10, 2020 •

edited

Loading

alexhochreiter commented Dec 10, 2020 •

edited

Loading

eriksjolund commented Dec 10, 2020 •

edited

Loading

boniek83 commented May 18, 2021 •

edited

Loading

eriksjolund commented Dec 7, 2021 •

edited

Loading