Description of problem: Neither the regular iso, or the live iso will produce a bootable install. The bios cannot find a bootable hard drive on a newer computer. This is the case on two computers I have. One was built when Mageia 7 was current. Mageia 7 and 8 installs worked fine, but Mageia 9 does not. On a new build, Mageia 9 will not boot either. On this computer, a hard drive from a 13 year old computer with a known working Mageia 9 install is available to boot from. That cannot be found either. In all cases, the Mageia 9 installs proceeded smoothly without error. Also, all installs, including the working install from the 13 year old machine, are EFI boot. The model of motherboard on the slightly older computer is not immediately available. The new build has a TUF Gaming Z790-pro wifi mother board with bios version 1601. And a core i7-12700KF CPU. Version-Release number of selected component (if applicable): 9 How reproducible: Unknown Steps to Reproduce: 1.perform install on affected hardware 2. 3.
Just out if curiosity, does any other installer load? Ubuntu? Asahi? If they load just fine I think the problem lies within our installer drakx.
CC: (none) => lovaren
Did you ensure the iso image used to do the install was itself booted in efi mode? https://doc.mageia.org/installer/9/en/content/installer.html#d4e308
CC: (none) => davidwhodgins
I would have to try again and double check to be sure how 9 install is booting, but in general, Mageia install has been booting in EFI mode for me by default since 7, and when I specifically paid attention this time around, it was. It is doing EFI installs with the EFI boot partition. As for other distros, I did install Ubuntu on the slightly older machine, and it is working fine.
https://doc.mageia.org/installer/9/en/content/setupBootloader.html#d4e1069 Is the second checkbox checked?
I have verified that the installer is booting in uefi mode. I have tried using grub2 and refind with and without the install to /EFI/boot option selected. No luck.
As the initial description is unclear ( mixing different machines and drives…): do the affected machines have more than one HDD/SSD?
To be clear, there are two computers at issue. 1) This machine was built when Mageia 7 was current. Mageia 7 and 8 worked fine. Mageia 9 does not. It has a single ssd, not nvme though. 2) This machine is a new build to replace a 13 year old computer that failed. It has a nvme hard drive, plus the hard drive from the old computer. The old computer had mageia 9 running in EFI mode. This machine is not bootable from either the new install on the nvme drive, or the old drive. This machine will boot from a mageia 9 live iso on a usb stick.
I'm inclined to suspect something is wrong in the bios/uefi settings, possibly having been reset back to default settings. Check things such as the sata mode which must be ahci. Other then that, I'm out of ideas.
I think this calls for Martin's opinion, so CC'ing him.
CC: (none) => lewyssmith, mageia
Using a Mageia 9 Live ISO, open a terminal window and run su - blkid efibootmgr and post the output from those commands here. Do either of your BIOSs have the option to select an EFI file to boot from? If so, try navigating to the disk/partition for the Mageia 9 ESP and selecting one of the .efi files. Given your experiments, you should have .efi files in the \EFI\BOOT, \EFI\mageia, and \EFI\refind directories.
I was able to get this to work. I removed all other hard drives and let the installer have its way with my new drive with the use entire disk option. Thankfully, I had a new drive and the installer produced a partition layout I could live with. This did produce an install that I could boot. It seems that the installer for Mageia 9 is producing broken EFI installs when instructed to use existing (or custom) partitions without generating any errors.
> It seems > that the installer for Mageia 9 is producing broken EFI installs when > instructed to use existing (or custom) partitions without generating any > errors. I do not think this is generally true, since many users (myself included) do just this. > the installer produced a partition layout I could live with You are always free to adjust it during installation! Since you have a working system, and we cannot sensibly progress this because the detailed information is lacking, closing.
Status: NEW => RESOLVEDResolution: (none) => WORKSFORME