Install keeps failing at 93% (Installing Boot Manager!)

[oldcpu]

@please_try_again

From the same Wiki page:

UEFI does not launch any boot code in the MBR whether it exists or not. Instead it uses a special partition in the partition table called “EFI SYSTEM PARTITION” in which files required to be launched by the firmware is stored. Each vendor can store its files under <EFI SYSTEM PARTITION>/EFI/<VENDOR NAME>/ folder and can use the firmware or its shell (UEFI shell) to launch the boot program. An EFI System Partition is usually formatted as FAT32.

From this page: Hybrid MBRs:

GRUB Legacy and GRUB 2—These workhorse boot loaders, which are very popular on Linux, work well with both MBR and GPT disks (although you need a patched GRUB 0.97 or GRUB2 for GPT support).

And according to this:

@6tr6tr

Thanks now I’m getting an issue at the install step of “disk”. It says it needs a partition at the beginning which is EFI Boot and of type FAT and mounted at /boot/efi. I am unable to create this myself in the installation step, so I thought I’d try to alter the installation partitioning they suggest. But I am unable to create an extended partition in the openSUSE installer! Any idea how to do this? Otherwise, I’m stuck.

I get the impression that openSUSE’s Legacy Grub has been patched. Actually it has been patched several times over the years. I’m able to identify openSUSE’s from other distros’ Legacy Grub (in findgrub) from the Grub signature’s offset, meaning if it’s farther/closer, the boot code is longer/shorter. So it has been patched… but to do what? I don’t know.

Interesting … from which I at first speculated to myself that if one ‘blows’ away the content of a PC’s pre-installed OS (including the EFI system partition) to install GNU/Linux on a PC with EFI/UEFI and GPT that one could have a problem. But if one sets up a dual boot (which keeps the exisiting partitions) there may not be a problem. … Unless of course GNU/Linux GRUB and or partition manager is setup to create the special partition in the partition table (called “EFI SYSTEM PARTITION” ) in which files required to be launched by the firmware is stored.

I’m not sure I’m happy, thou, with my speculation, as I am left asking myself, what happens if one adds a new hard drive (to replace an old drive) on a PC with an EFI/UEFI BIOS ?

Ergo I think my speculation not accurate.