Arch Linux

Yeatz

Member

Registered: 2024-11-23

Posts: 1

How to fix Arch not booting into OS after installation

I've had this problem for a long time like when the installation is done and it reboots it just errors but i found a fix for it.

If you use archinstall try this:

-When you can select the bootloader DO NOT use grub use systemd bootloader, as there are some errors that have been reported recently then after the installation is finished go into your boot menu and select the HDD/SSD (DO NOT USE THE USB FLASH DRIVE) where you installed Arch on and then you should see a screen with Arch linux and installation. Select installation and the process will be started again. BUT if you can select your Bootloader a second time use Limine Bootloader. Finish the installation again and use the same HDD where you booted from before. Reboot your pc and go into your Boot Menu again (Only if dual boot, if not you will probably see the limine bootloader) select arch linux and you will boot into your new OS.

If you use manual installation try:

-When you install the bootloader DO NOT use grub as said in the begining! Install systemd first or limine.

I HOPE THIS WILL FIX YOUR PROBLEM WITH NOT INSTALLING

cryptearth

Member

Registered: 2024-02-03

Posts: 1,084

Re: How to fix Arch not booting into OS after installation

first: archinstall is meant as a tool for experienced users familiar with the manual install - for users new to arch it's recommended to follow the manual install guide anyway

as for grub vs systemd-boot (vs any other boot-loader/-manager): although there're quite a number of topics about users encounter issues these can often traced back to (mostly) user error or some bugs in a systems firmware implementation (often laptops)
the rest is complete nonesense and can likely again either traced back to mistakes you made or to some weird issues of the uefi of your hardware - but when broken down into "that's a you-problem at your end" and "oh yea, that's a known issue with bootloader X, try Y instead" it's hardly the latter one

so, if you have troubles with grub, I recommend you rather investigating on your end instead of wrongly accusing grub to be the general issue and give that bad advice to use systemd-boot instead
fun fact: systemd-boot requires the user to write thier own config for which they're required to correctly identify a unique identifier like a (part-)uuid or label - and although that's not an issue for someone who did this a dozen times for a beginner this can be the deal braker between fiddle with systemd-boot and not get it done and just use grub and has its grub-mkconfig do its thing

fun fact: when you build a uki and place it on the esp you can even use the windows efi bootmgfw to chain it and don't need any linux specific bootloader at all - although a uki can (and should) booted directly from the uefi itself - my point here is to give yet another bootloader as an example why I doubt to issue is grub but guess it's an issue at your end

Last edited by cryptearth (2024-11-23 12:07:14)

Head_on_a_Stick

Member

From: The Wirral

Registered: 2014-02-20

Posts: 8,480

Website

Re: How to fix Arch not booting into OS after installation

When you install the bootloader DO NOT use grub as said in the begining! Install systemd first or limine

I am presuming your UEFI firmware is buggy and so requires the --removable option for the grub-install command, which copies GRUB's core.img to /EFI/BOOT/Bootx64.efi on the EFI system partition; systemd-boot does this automatically, which is why that worked for you, and I presume Limine does the same.

GRUB's method is better (IMO) because it doesn't automatically overwrite the UEFI loader for other operating systems such as the BSDs, 9front & Haiku, all of which use bootx64.efi.

Relevant wiki entry: https://wiki.archlinux.org/title/GRUB#D … _boot_path

Note that the wiki is the correct location for advice such as this because your post will soon be lost in the noise here on the boards.

---

Para todos todo, para nosotros nada