System BootOrder not Found
 

I am posting here because I have boot issues with every distro I tried, and they all give a similar error, so I think that this is a hardware (BIOS) issue?

Ever since I removed Windows from my laptop ( https://www.amazon.com/Toshiba-Satel...&redirect=true ), I have had boot issues-galore. I am finally posting here because I don't want something to break.

A while back, I removed Windows, and installed a flavor of linux (don't remember). I have had boot issues-- boot delays, blank screens, no-booting-at-all, hardware lockups, etc since. I have been distro hopping to see if it is the distro's fault or not. It isn't. I have tried about 15 distros and they all get some sort of error. I have tried installing with/without secureboot, and in legacy (csm) mode. I couldn't install linux in uefi mode for the longest time until I reset my BIOS. Now it works but with errors. I would just be using legacy mode all this time to avoid all these troubles, but a few things don't work right in csm mode (acpi is one of them).

For the real issue: please check the picture attatched. This has been happening ever since I updated Fedora recently ( I've been using Fedora for some time, but with a huge boot delay and cpu lockups). Because of the error in the picture, I keep getting a new boot entry at every boot. Eventually, my computer wouldn't boot (tried fixing grub... grub wouldn't even load). So I installed OpenSUSE Leap recently to see if it was just Fedora since things update more often in Fedora-land. I deleted the 20+ Fedora entries via efibootmgr. Then I installed OpenSUSE. I still get the error from the picture, but at least now I don't have a long boot delay and cpu lockups like in Fedora. So I am happy that OpenSUSE works with this boot-entry issue. I came here for help to see if anyone knew what could be done before OpenSUSE doesn't boot anymore (from too many entries?) like Fedora did earlier.

FYI: I installed Fedora (from earlier) in UEFI mode with secureboot disabled. I currently only have OpenSUSE installed with secureboot enabled.

Has anyone had this issue? Is it because my MBR keeps looking for Windows even though it isn't there (one of those crappy dependent computers)? Is this an indication of a hardware issue? Can anyone help me fix this? Because I like OpenSUSE... it works. Thanks!

Hmm... fdisk mentions "Microsoft". Sketchy...
Sorry if the image attatched is blurry. :-/

You should try to disable the following:
336ms bluetooth.service
268ms plymouth-read-write.service
13ms iscsi.service
181ms wpa_supplicant.service

How would that solve anything ?. I don't think the OP is worried about a delay of less than a second.

@Ererer, how did you remove Win ? - did you remove the directory from the EFI partition ?. Let's see what is in that partition (just a ls from Suse will do).

Since that was quite some time ago... I do remember that I kept the efi partition, but that gave me errors as to "error reading from sector efx0 (or whatever is was) on hd1". So my computer was still looking for Windows after it was removed. This caused a big boot delay and sometimes non-boot of the distros I remember. Eventually I just wiped everything to try and fix it, but that was when I couldn't boot with uefi mode anymore.

I have to add this for reference: eventually I got tired of using the buggy csm mode (I had to use it just to boot and use my computer) so I wiped everything by installing Windows again (the tech preview for 10). I then "reset" (and updated) my BIOS from Windows. Then I removed Windows, completely wiped everything, and installed a distro. Now I have been able to boot with uefi mode enabled, but with errors, lockups, and non-boots here and there. At least I don't get the "error reading from sector efx0 (or whatever is was) on hd1" anymore...

Hope it's the right info :/

@Keruskerfuerst thanks for "reminding" me... I needed to disable bluetooth.service anyways since it wastes precious battery on this laptop. ;-D

That answers one query - whether the machine would boot without the Win entry. Maybe the update did it.

Might be worth running a long smart test against the disk.

Can you disable secure boot or similar in the Bios?

This is strange:

BootOrder: 0008,0016,0001,0002,0003,0004,0005,0006,0007,0000
Boot0000 opensuse-secureboot Vendor(99e275e7-75a0-4b37-a2e6-c5385e6c00cb,)
Boot0001* opensuse-secureboot Vendor(99e275e7-75a0-4b37-a2e6-c5385e6c00cb,)
Boot0002* opensuse-secureboot Vendor(99e275e7-75a0-4b37-a2e6-c5385e6c00cb,)

Fixed!!
 

Sorry I couldn't reply sooner... went on a tech-free vacation.

The error is gone now, and everything boots well. efibootmgr is normal; entries aren't added anymore for no reason! How I did it:

-Deleted duplicate entries in efibootmgr (except current one)
-Set boot order (efibootmgr -o 000C, OO16)
-Updated grub

Now everything works great. From me setting the boot order must have reset something. Also, I noticed that uefi: built in efi shell boots before opensuse (as seen below). That might have been the issue this whole time?
FYI: I don't get cpu lockups (boot delay) with opensuse, as I have with ome other distros. I will just assume that it is a kernel issue and be happy ;-) So... I'm sticking with Opensuse. I don't want to touch anything else. I'm pretty sure it's my favorite anyways ;-D