Hi Lachu,
I ran into the same error after zypper dup.
In the end, the cause turned out to be the following: the LoaderDevicePartUUID variable was missing from efivars.
- The EFI entry
openSUSE Boot Managerpointed to:
EFI\SYSTEMD\SHIM.EFI
shimlaunched the sameSYSTEMD-BOOTX64.EFI, but without the correct systemd-boot EFI variables context;sysefi-generatorin the initrd could not findLoaderDevicePartUUID;- a fallback was selected:
/dev/disk/by-designator/esp; - this caused a conflict between services, and one of the services was disabled after a timeout. After that, the boot process continued normally.
After upgrading to the newer systemd version during the latest update, this became an issue. With the previous version, everything worked as expected.
Please check:
ls /sys/firmware/efi/efivars | grep LoaderDevice
In the end, I ran:
sudo bootctl install
As a result, I got another boot menu entry:
Boot0002 Linux Boot Manager
It directly loads:
EFI\SYSTEMD\SYSTEMD-BOOTX64.EFI
and should work correctly.
Now the normal boot path goes through this chain:
UEFI
└─ Boot0002
----└─ EFI\SYSTEMD\SYSTEMD-BOOTX64.EFI
--------└─ LoaderDevicePartUUID = 01b85e5d-b970-400d-a409-08e6ae029415
------------└─ BLS entry
-----------------└─ kernel + initrd
There is " -----------------" insteed spaces because formatting problem.
The old problematic path:
Boot0001
└─ EFI\SYSTEMD\SHIM.EFI
is now only used as a backup.