Hello, I couldn't send an email and finally figured out that yesterday's update of Emacs was the cause. In the Message; Subject : Re: Shim error message about "blocked executable in ESP" Message-ID : <2986485.JigTtRx2U3@silversurfer> Date & Time: Sun, 09 Jun 2024 13:25:25 +0200 Stakanov via openSUSE Users <users@lists.opensuse.org> has written:
In data domenica 9 giugno 2024 06:41:54 CEST, Andrei Borzenkov ha scritto:
On 09.06.2024 00:25, Stakanov via openSUSE Users wrote:
In data sabato 8 giugno 2024 13:10:05 CEST, Masaru Nomiya ha scritto:
Please do this;
$ fwupdtool esp-list --verbose
Selected volume: /org/freedesktop/UDisks2/block_devices/sda1 /boot/efi/EFI/boot/bootx64.efi /boot/efi/EFI/boot/fallback.efi /boot/efi/EFI/boot/MokManager.efi /boot/efi/EFI/opensuse/shim.efi /boot/efi/EFI/opensuse/MokManager.efi /boot/efi/EFI/opensuse/grub.efi /boot/efi/EFI/opensuse/boot.csv /boot/efi/EFI/opensuse/grub.cfg /boot/efi/EFI/opensuse/grubx64.efi /boot/efi/EFI/grub/shim.efi /boot/efi/EFI/grub/MokManager.efi /boot/efi/EFI/grub/grub.efi /boot/efi/EFI/grub/boot.csv /boot/efi/EFI/grub/grub.cfg
That is quite a lot, I think she has multiple entries on her machine. How would one decide which one is the right one or better the broken one?
The path to the broken one was in your very first post. Thank you for pointing to this. Remains the second obvious question: can I check with ease which one of the entries she is using when booting and which is the back up of the one she is using. So if she is not using the culprit, it should be save to eliminate it? Or should I simply force the update of it and the error will be gone? I wonder why the machine has so many entries, I installed it years ago and since then only normal zypper dup operations. Nothing fancy, no experiments. Maybe at one point we went from legacy to uefi, but I do not recall to be honest. That could have doubled the entries..... Years ago, I really do not recall.
Have a look; https://www.suse.com/ja-jp/support/kb/doc/?id=000019909 That is, If there was a bootloader update error during patching or otherwise, it should be logged in /var/log/pbl.log. Solution is 'reinstall of GRUB bootloader. I strongly recommend reinstalling with YasT2 to be on the safe side. YaST2 --> System --> Boot Loader --> Boot Code Options --> Protective MBR flag rmove -- (then) --> set Best Regards & Good Night. --- ┏━━┓彡 野宮 賢 mail-to: nomiya @ lake.dti.ne.jp ┃＼／彡 ┗━━┛ "Maddox hopes that empowering users to pick their own algorithms will get them to think more about what’s involved in making them. " -- Bluesky's Custom Algorithms Could Be the Future of Social Media --