On 2023-03-19 21:16, Carlos E.R. wrote:
On 2023-03-19 19:57, Neil Rickert wrote:
On Sun, 19 Mar 2023 04:28:02 +0100 "Carlos E. R." <> wrote:
On 2023-03-19 02:25, Neil Rickert wrote:
I don't mix. I don't create nor ever touch that directory. I don't know how to tell the system to create it again.
There should be a command to do it?
...
Telcontar:~ # tree -sD /boot/efi/EFI/ /boot/efi/EFI/ ├── [ 8192 Mar 20 2020] auxiliary <== leap 15.2 │ ├── [ 846096 Mar 18 23:09] MokManager.efi │ ├── [ 60 Mar 18 23:09] boot.csv │ ├── [ 125 Mar 18 23:09] grub.cfg │ ├── [ 1193840 Mar 18 23:09] grub.efi │ ├── [ 139264 Mar 18 23:09] grubx64.efi │ └── [ 934024 Mar 18 23:09] shim.efi ├── [ 8192 Aug 10 2020] boot │ ├── [ 1208968 Aug 10 2020] bootx64.efi │ └── [ 358768 Aug 10 2020] fallback.efi └── [ 8192 Aug 10 2020] main-os <== leap 15.4 ├── [ 846240 Mar 18 21:45] MokManager.efi ├── [ 56 Mar 18 21:45] boot.csv ├── [ 120 Mar 18 21:45] grub.cfg ├── [ 1275904 Mar 18 21:45] grub.efi ├── [ 143360 Mar 18 21:45] grubx64.efi └── [ 934680 Mar 18 21:45] shim.efi
My guess is that the bios wanted to boot /boot/efi/EFI/boot because the partition filesystem was corrupt. So, the question is, what creates the "/boot/efi/EFI/boot" directory, how to repopulate it? I'm googling for: what creates "fallback.efi" in opensuse The wiki says that it is created on the first installation. No mention so far of what command creates it, how to recreate it so that it works correctly. https://en.opensuse.org/openSUSE:UEFI https://en.opensuse.org/Systemd-boot This one finally gives some information, on comment 12: https://www.linuxquestions.org/questions/linux-hardware-18/reinstating-boot-... and points to https://www.rodsbooks.com/efi-bootloaders/fallback.html for more information. But there were no answer to his questions, so no subsequent instructions. He wanted: $ sudo efibootmgr -v $ ls -lR /boot/efi The explanation at https://www.rodsbooks.com/efi-bootloaders/fallback.html is nice, but the description it does of "BOOT.CSV" doesn't match openSUSE, because apparently it should be a text file in UCS-2 or UTF-16, and what I see appears a binary. There must be a susefied method somewhere of repairing/recreating this emergency directory. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)