You are not logged in.

#1 2024-09-10 07:50:13

hhhou
Member
Registered: 2024-09-10
Posts: 3

The system is unable to boot. (Solved)

I recently installed Arch Linux, and when I ran `efibootmgr` from the installation medium’s live CD, the output was:

Boot0001* GRUB  HD(2,GPT,7fd0185c-03b8-492b-b07d-9b64e4f23b6d,0x200800,0x100000)/\EFI\GRUB\grubx64.efi

However, when I exit the installation medium and attempt to boot the system, selecting the boot entry just takes me back to the boot menu. After re-entering the installation medium and checking `efibootmgr` again, the output changes to:

Boot0025* UEFI  SOLIDIGM SSDPFKKW020X7, Partition 2 PciRoot(0x0)/xxxxxxx (x indicates several more characters and /\EFI\GRUB\grubx64.efi is missing from the tail)

I am using the Gigabyte MS03-6L0, and there are no settings related to CSM/UEFI in the BIOS. Secure boot is also disabled.

How should I resolve this issue?

Last edited by hhhou (2024-09-27 09:22:24)

Offline

#2 2024-09-10 08:38:41

cryptearth
Member
Registered: 2024-02-03
Posts: 919

Re: The system is unable to boot. (Solved)

That's quite a hefty board you have - rather new as it looks
could be an issue with the uefi imolementation
I recently rented a new root server at OVH and did my setup via the impi kvm konsole
I ran into a similar issue where the grub entry either not worked or won't stick
I switched to install grub with --no-nvram --removable so it ended up on the fallback path EFI\BOOT\BOOTx64.efi without adding a boot entry at all but gets auto discovered during POST
maybe contact gigabyte support about this issues

Offline

#3 2024-09-10 14:44:12

hhhou
Member
Registered: 2024-09-10
Posts: 3

Re: The system is unable to boot. (Solved)

cryptearth wrote:

That's quite a hefty board you have - rather new as it looks
could be an issue with the uefi imolementation
I recently rented a new root server at OVH and did my setup via the impi kvm konsole
I ran into a similar issue where the grub entry either not worked or won't stick
I switched to install grub with --no-nvram --removable so it ended up on the fallback path EFI\BOOT\BOOTx64.efi without adding a boot entry at all but gets auto discovered during POST
maybe contact gigabyte support about this issues

That works for me! Thanks!

Last edited by hhhou (2024-09-10 14:45:50)

Offline

#4 2024-09-27 05:51:40

hhhou
Member
Registered: 2024-09-10
Posts: 3

Re: The system is unable to boot. (Solved)

Update.

I got a reply from gigabyte and they suggested me to update bios to the latest version, which solved this.

Offline

#5 2024-09-27 07:09:26

seth
Member
Registered: 2012-09-03
Posts: 58,299

Re: The system is unable to boot. (Solved)

\o/
Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

Offline

Board footer

Powered by FluxBB