Error: Bootloader not detected. /etc/sysconfig/bootloader has LOADER_TYPE="grub2-efi", but only "systemd-boot" or "grub2-bls" are recognized.
This happened on one of my systems after updating them this morning (the others are fine with grub2-efi as the bootloader) and I can't seem to find out what it is actually complaining about or which package to (re-)install to get it fixed. Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
I had the same but oddly enough only on one machine. Thankfully reboot seems to have worked without issues. On Sat, 12 Oct 2024, 13:06 ASSI, <Stromeko@nexgo.de> wrote:
This happened on one of my systems after updating them this morning (the others are fine with grub2-efi as the bootloader) and I can't seem to find out what it is actually complaining about or which package to (re-)install to get it fixed.
Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
12.10.2024 13:06, ASSI wrote:
This happened on one of my systems after updating them this morning (the others are fine with grub2-efi as the bootloader) and I can't seem to find out what it is actually complaining about or which package to (re-)install to get it fixed.
Achim.
Why do you have sdbootutil installed if you are not using systemd-boot? But yes, sdbootutil could handle it more gracefully. Package really must check the configured bootloader in the trigger and skip update if bootloader is not handled by sdbootutil. Care to open bug report or issue on github?
Andrei Borzenkov writes:
Why do you have sdbootutil installed if you are not using systemd-boot?
I don't know. I had to manually remove it at some time (based on advice on this list) and either I forgot to do it on this machine (this is an older system that I don't use regularly anymore) or it got pulled in again at a later time. Removing it manbually resolves the issue and no error message is shown when installing a kernel. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ SD adaptations for KORG EX-800 and Poly-800MkII V0.9: http://Synth.Stromeko.net/Downloads.html#KorgSDada
I have three aarch64 (Raspberry Pi 4b) Tumbleweed systems that recently started showing the "Bootloader no detected" error. I didn't worry about it, as the systems didn't seem to have any other issues. With the discussion of sdbootutil being installed, though, I looked, and it's installed on all three. I also noticed that zypper shows sdbootutil's status as "i", not "i+", so I assume it was installed by default. So, I have questions... Is it safe to remove sdbootutil on the Raspberry Pi's? Will it simply be reinstalled on the next dup? Should it be removed? Is there any harm in leaving it alone and waiting for a more "graceful" sdbootutil? Thanks. David On 10/12/24 8:40 AM, ASSI wrote:
Why do you have sdbootutil installed if you are not using systemd-boot? I don't know. I had to manually remove it at some time (based on advice on this list) and either I forgot to do it on this machine (this is an
Andrei Borzenkov writes: older system that I don't use regularly anymore) or it got pulled in again at a later time. Removing it manbually resolves the issue and no error message is shown when installing a kernel.
Regards, Achim.
ASSI writes:
Andrei Borzenkov writes:
Why do you have sdbootutil installed if you are not using systemd-boot?
I don't know. I had to manually remove it at some time (based on advice on this list) and either I forgot to do it on this machine (this is an older system that I don't use regularly anymore) or it got pulled in again at a later time. Removing it manbually resolves the issue and no error message is shown when installing a kernel.
I updated that system again today and the same thing happened, as something has pulled in sdbootutil again. Since I can cleanly remove it, it is either a recommendation or a weak dependency, how do find out what is causing sdbootutil to get installed on this machine? Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ SD adaptations for Waldorf Q V3.00R3 and Q+ V3.54R2: http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
01.11.2024 19:47, ASSI wrote:
ASSI writes:
Andrei Borzenkov writes:
Why do you have sdbootutil installed if you are not using systemd-boot?
I don't know. I had to manually remove it at some time (based on advice on this list) and either I forgot to do it on this machine (this is an older system that I don't use regularly anymore) or it got pulled in again at a later time. Removing it manbually resolves the issue and no error message is shown when installing a kernel.
I updated that system again today and the same thing happened, as something has pulled in sdbootutil again. Since I can cleanly remove it, it is either a recommendation or a weak dependency, how do find out what is causing sdbootutil to get installed on this machine?
man zypper zypper search --recommends zypper info --supplements
Regards, Achim.
sdbootutil reappeared on my aarch64 systems, but not my x86_64 systems. On all systems... > zypper info --supplements sdbootutil Loading repository data... Reading installed packages... Information for package sdbootutil: ----------------------------------- Repository : openSUSE-Tumbleweed-Oss Name : sdbootutil Version : 1+git20241017.34ee974-1.1 Arch : aarch64 Vendor : openSUSE Installed Size : 75.9 KiB Installed : Yes (automatically) Status : up-to-date Source package : sdbootutil-1+git20241017.34ee974-1.1.src Upstream URL : https://en.opensuse.org/openSUSE:Usr_merge Summary : script to install shim with sd-boot Description : Hook scripts to install shim along with systemd-boot Supplements : [2] (grub2-x86_64-efi-bls and shim) (systemd-boot and shim) On the aarch64 systems... > zypper se -x grub2-x86_64-efi-bls shim systemd-boot Loading repository data... Reading installed packages... S | Name | Summary | Type ---+--------------+----------------------------+-------- i+ | shim | UEFI shim loader | package i | systemd-boot | A simple UEFI boot manager | package On the x86_64 systems... > zypper se -x grub2-x86_64-efi-bls shim systemd-boot Loading repository data... Reading installed packages... S | Name | Summary | Type ---+----------------------+--------------------------------------------+-------- | grub2-x86_64-efi-bls | Image for Boot Loader Specification (BLS-> | package i+ | shim | UEFI shim loader | package | systemd-boot | A simple UEFI boot manager | package I pretty sure I didn't install systemd-boot on the aarch64 systems (and its status is "i", not "i+"). I'm not sure how to read the " (systemd-boot and shim)" under Supplements, but I'm guessing the presence of systemd-boot, along with shim, is what's causing the installation of sdbootutil. David On 11/1/24 10:17 AM, Andrei Borzenkov wrote:
01.11.2024 19:47, ASSI wrote:
ASSI writes:
Andrei Borzenkov writes:
Why do you have sdbootutil installed if you are not using systemd-boot?
I don't know. I had to manually remove it at some time (based on advice on this list) and either I forgot to do it on this machine (this is an older system that I don't use regularly anymore) or it got pulled in again at a later time. Removing it manbually resolves the issue and no error message is shown when installing a kernel.
I updated that system again today and the same thing happened, as something has pulled in sdbootutil again. Since I can cleanly remove it, it is either a recommendation or a weak dependency, how do find out what is causing sdbootutil to get installed on this machine?
man zypper zypper search --recommends zypper info --supplements
Regards, Achim.
01.11.2024 21:00, David Walker wrote:
I pretty sure I didn't install systemd-boot on the aarch64 systems (and its status is "i", not "i+"). I'm not sure how to read the " (systemd-boot and shim)" under Supplements, but I'm guessing the presence of systemd-boot, along with shim, is what's causing the installation of sdbootutil.
Correct.
Andrei Borzenkov writes:
man zypper zypper search --recommends zypper info --supplements
Hmmm. Doesn't seem to tell me where the whole thing started, but at least I found that systemd-boot was also installed (have yet to find out why) and that was what kept pulling sdbootutil in (alongside shim which of course is actually needed to facilitate UEFI secure boot). Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Samples for the Waldorf Blofeld: http://Synth.Stromeko.net/Downloads.html#BlofeldSamplesExtra
Is your system also aarch64, Achim? I'm wondering if it seems that systemd-boot is installed by default on aarch64 but not x86_64, or if I've done something that caused it to be installed. David On 11/1/24 1:31 PM, ASSI wrote:
Andrei Borzenkov writes:
man zypper zypper search --recommends zypper info --supplements Hmmm. Doesn't seem to tell me where the whole thing started, but at least I found that systemd-boot was also installed (have yet to find out why) and that was what kept pulling sdbootutil in (alongside shim which of course is actually needed to facilitate UEFI secure boot).
Regards, Achim.
David Walker writes:
Is your system also aarch64, Achim? I'm wondering if it seems that systemd-boot is installed by default on aarch64 but not x86_64, or if I've done something that caused it to be installed.
No, x86_64; only one of my systems had this problem. It's also very similar to another one, the difference is that the system with the problem gets updated less often, so I think there was some packaging error in the past that somehow led to the situation. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Waldorf MIDI Implementation & additional documentation: http://Synth.Stromeko.net/Downloads.html#WaldorfDocs
On 11/1/24 11:26 PM, David Walker wrote:
Is your system also aarch64, Achim? I'm wondering if it seems that systemd-boot is installed by default on aarch64 but not x86_64, or if I've done something that caused it to be installed.
David
On 11/1/24 1:31 PM, ASSI wrote:
Andrei Borzenkov writes:
man zypper zypper search --recommends zypper info --supplements Hmmm. Doesn't seem to tell me where the whole thing started, but at least I found that systemd-boot was also installed (have yet to find out why) and that was what kept pulling sdbootutil in (alongside shim which of course is actually needed to facilitate UEFI secure boot).
Regards, Achim.
FWIW, I had a friend have this issue around 6 months ago. For some reason which we could not determine why it kept getting reinstalling as we could not find any dependencies that would have caused it. They would get a message when they ran snapper because sdbootutil needed another plugin pkg which was for snapshots which was not being installed. Each time we'd remove the packages but next dup they'd come back. I believe we ended up locking those packages to prevent installation and no other issues have occurred. Her system / setup is similar to one of my systems but I have not seen that issue on any of my systems so the mystery lives on. -- Regards, Joe
On 11/2/24 4:17 PM, Carlos E. R. wrote:
On 2024-11-02 17:49, Joe Salmeri wrote:
Each time we'd remove the packages but next dup they'd come back.
Have you tried to taboo it?
Hi Carlos, Yes, after removing we locked them so they could not be installed but that doesn't explain why they were auto installed on her system or what the dependencies was that triggered it. I thought when we locked them a future update would fail the solver and point to the culprit but it never happened. -- Regards, Joe
participants (6)
-
Alin Marin Elena -
Andrei Borzenkov -
ASSI -
Carlos E. R. -
David Walker -
Joe Salmeri