Hello, I have a problem with installing OpenSUSE, the installation proceeds without errors, however, the disk with OpenSUSE installed is not detected as bootable in UEFI, so I cannot boot the system, what should I do with this case?
I’ve already tried doing the following things:
Copying /boot/efi/EFI/opensuse/grubx64.efi to /boot/efi/EFI/BOOT/BOOTX64.EFI - nothing changed.
Checking for the Protective MBR flag on the disk - the flag is not set.
When you boot the openSUSE installation media and select “Boot from hard disk …” will that start your installed system?
Regards
susejunky
Yes, the system boots normally.
Fine.
So when you are running your installed openSUSE Tumbleweed system open a console and do (as root)
efibootmgr -v
and show the results here; i.e. show the command line + all results + the next empty command prompt. Enclose all this in code tags (the “#”-button in the forum editor).
Regards
susejunky
localhost:/home/unnamed # efibootmgr -v
BootCurrent: 0000
Timeout: 0 seconds
BootOrder: 2001,2002,2003
Boot0000* USB HDD: UFD 2.0 Silicon-Power8G PciRoot(0x0)/Pci(0x14,0x0)/USB(1,0)/HD(2,GPT,50602dbd-9a23-20ff-bfcd-bb8a3d99536c,0xe5c9d8,0x10000)RC
Boot0001* Unknown Device: HD(1,GPT,64e32b15-d9c8-44d2-8d0c-de43743e66ca,0x800,0x100000)/File(\EFI\opensuse\grubx64.efi)RC
Boot0002* opensuse-secureboot HD(1,GPT,1348566b-52f7-4066-bc06-6ad53780b5f5,0x800,0x100000)/File(\EFI\opensuse\shim.efi)
Boot0003* Unknown Device: HD(1,GPT,1126ebcb-f615-464d-b74b-988c845385b9,0x1000,0x96000)/File(\EFI\opensuse\grubx64.efi)RC
Boot2001* EFI USB Device RC
Boot2002* EFI DVD/CDROM RC
Boot2003* EFI Network RC
localhost:/home/unnamed #
Try:
efibootmgr -o 0002,2001
Reboot and see if it works.
If not, are there any (error) messages during startup?
What you can try as well:
Use your UEFIs boot selection. To reach it you have to press a special key (usually an “F-key” or “DEL”, see your motherboards manual for details) directly after reboot. That should provide you with a list of all UEFI-bootable systems installed on your machine.
Regards
susejunky
Did not help.
“No Bootable Device”
What exact computer do you have (vendor, model)?
You have three lines in boot options and each has different GUID; post output of “blkid” to compare what you actually have.
Acer Aspire E5-575G-39M5
localhost:/home/unnamed # blkid
/dev/sda1: UUID="6CAC-4B47" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="64e32b15-d9c8-44d2-8d0c-de43743e66ca"
/dev/sda2: UUID="eb8021b3-4754-4a8c-b255-f88d397c598c" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="26ad7b6a-8c44-417b-b1b2-8465a3865f0e"
/dev/sdb1: LABEL="Ventoy" UUID="ABD6-7E8E" BLOCK_SIZE="512" TYPE="exfat" PTTYPE="dos" PARTLABEL="Ventoy" PARTUUID="b9d65fd6-c5bd-f377-19a3-1a1e4e8b635a"
/dev/sdb2: SEC_TYPE="msdos" LABEL_FATBOOT="VTOYEFI" LABEL="VTOYEFI" UUID="7502-2467" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="VTOYEFI" PARTUUID="50602dbd-9a23-20ff-bfcd-bb8a3d99536c"
localhost:/home/unnamed #
Is /dev/sda1 your ESP and /dev/sda2 your openSUSE Tumbleweed root partition?
Have you already tried whether reinstalling the bootloader will help?
Regards
susejunky
Yes.
Tried doing it via grub2-install --target=x86_64-efi --efi-directory=/boot/efi, nothing has changed.
The problem has been resolved.
It was solved by the following methods:
1)Removing the /boot/efi/EFI/opensuse folder.
2)Removing Boot Entry pointing to opensuse/grubx64.efi via efibootmgr.
3)Installing the bootloader to the removable path by specifying --removable in the grub2-install parameters.
After all this, the disk with the installed system finally began to be detected as bootable.
You never told us that you had installed to a removable media?!
Nevertheless good to hear that your problem is solved.
Regards
susejunky
No, I have a non-removable drive, and I have to install the bootloader in the removable path because of the bugged UEFI, which can load bootloaders only from the removable path.
As I understand it, due to errors in UEFI, it also cannot normally detect the disk if there is more than one bootloader in the efi directory.
You have a buggy implementation of UEFI. It apparently doesn’t properly handle NVRAM entries. But it does handle the default which you set with your “–removable” install.
You might need to occasionally redo this, if a future update breaks booting.
Try to update BIOS.
Try to use CSM mode for booting if available.