Arch Boot Issue

theonlyone · 2024-12-14 13:16:01

my Arch Boot Entry is not showing up in Firmware Boot Order F10 i have to manually go into Boot Options F9 and it is listed there as EFI HARDDRIVE before it was listed as Linux Boot Manager, I can still boot into arch by manually going into boot options but it doesn't auto launch this issue started when i reinstalled arch due to some mess up, i tried reinstalling fresh arch with systemd boot then with grub i thought maybe i was configuring something wrong then i used archinstall to auto configure boot loader but still same issue. i installed fedora to see if it has a similar issue but fedora gets recognized in the boot order, i even used to sbctl to sign the keys thinking that was the problem but no. after reinstalling 10 times im losing it.
current boot loader is systemd boot

mkfs.fat -F32 /dev/sda1
mkswap /dev/sda2
swapon /dev/sda2
mkfs.ext4 /dev/sda3
mkfs.ext4 /dev/sda4

mount /dev/sda3 /mnt
mkdir /mnt/boot
mkdir /mnt/home
mount /dev/sda1 /mnt/boot
mount /dev/sda4 /mnt/home
lsblk

mount -t efivarfs efivarfs /sys/firmware/efi/efivars
ls /sys/firmware/efi/efivars

bootctl install
nano /boot/loader/entries/arch.conf
title Arch
linux /vmlinuz-linux
initrd /initramfs-linux.img

echo "options root=PARTUUID=$(blkid -s PARTUUID -o value /dev/sda3) rw" >> /boot/loader/entries/arch.conf

Last edited by theonlyone (2024-12-14 14:08:15)

Head_on_a_Stick · 2024-12-14 13:29:10

theonlyone wrote:

i have to manually go into Boot Options F9 and it is listed there as EFI HARDDRIVE

Does that option boot automatically if you remove all other NVRAM entries with efibootmgr(8)?

Share the output of `efibootmgr -u` here if you're not sure what to delete.

EDIT: please open a new thread if you need help with your non-functional <return> key

Last edited by Head_on_a_Stick (2024-12-14 13:29:58)

theonlyone · 2024-12-14 13:33:27

[user@arch ~]$ efibootmgr -u
BootCurrent: 0001
Timeout: 0 seconds
BootOrder: 0002,0001,2001,3002,2002,2004
Boot0000* USB Hard Drive (UEFI) - VendorC ProductCode (VendorC ProductCode) PciRoot(0x0)/Pci(0x14,0x0)/USB(0,0)/HD(2,MBR,0x81712206,0x3a88000,0x10000)䍒
Boot0001* EFI Hard Drive (WDS240G3G0A-00BJG0) PciRoot(0x0)/Pci(0x17,0x0)/Sata(1,32768,0)/HD(1,GPT,591548fb-503f-4b3d-91d5-14698215a6d3,0x800,0x200000)䍒
Boot0002* Windows Boot Manager HD(1,GPT,f4df9c98-1a78-4bac-a442-84282ec783a6,0x800,0x32000)/\EFI\Microsoft\Boot\bootmgfw.efi䥗䑎坏S
Boot0003* Fedora HD(1,GPT,88eebe97-5f67-41e8-8d0b-8bac881409b0,0x800,0x12c000)/\EFI\fedora\shimx64.efi
Boot2001* EFI USB Device 䍒
Boot3002* Internal Hard Disk or Solid State Disk

Head_on_a_Stick · 2024-12-14 13:35:37

Delete Boot0002 & Boot0003. And don't use `pacman -Sy $package` in an installed system: https://wiki.archlinux.org/title/System … nsupported

theonlyone · 2024-12-14 13:37:07

will it also delete my window boot manager? cause iam dual booting

Head_on_a_Stick · 2024-12-14 13:40:18

Are you using the firmware boot menu to launch Windows? If so then keep it but your firmware seems to "forget" the Arch systemd-boot entry and will only boot the fallback ($ESP/EFI/Boot/bootx64.efi) automatically if the NVRAM entries pointing to specific loaders are removed.

You could try using the Shim with Arch and fake Fedora's setup, perhaps your firmware is coded to "remember" such boot entries. https://wiki.archlinux.org/title/Unifie … _Boot#shim

EDIT: does changing the boot order work? Try that first. I think it will probably reset though.

EDIT2: how many EFI system partitions do you have?

Please share the output of `blkid`.

Last edited by Head_on_a_Stick (2024-12-14 13:42:36)

theonlyone · 2024-12-14 13:44:41

window boots automatically and is listed in the boot order, but its the arch manager that is not being listed anymore it was listed the first time i installed arch then i just selected arch as my first boot priority and it would boot into systemd boot while also giving me option to boot into window but now its just listed as efi harddrive and does not show up in boot order.

edit: but i can use the firmware boot menu to manually boot into the efi harddrive which would get me into arch (it is annoying to do that everytime)

Last edited by theonlyone (2024-12-14 13:49:01)

theonlyone · 2024-12-14 13:46:10

[user@arch ~]$ blkid
/dev/nvme0n1p3: BLOCK_SIZE="512" UUID="7E924DC1924D7EA1" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="3e17cbb0-ec61-4afd-ac7d-b8cf38523d6a"
/dev/nvme0n1p1: UUID="F24A-5239" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="Basic data partition" PARTUUID="f4df9c98-1a78-4bac-a442-84282ec783a6"
/dev/nvme0n1p4: BLOCK_SIZE="512" UUID="04DAEF2ADAEF16A8" TYPE="ntfs" PARTUUID="c3755184-932d-4602-9b11-a1fb23caa0a0"
/dev/sda4: UUID="a04b15e5-cccf-46c9-9f0e-f2cc386c1b56" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="home" PARTUUID="388f4804-ed0f-463f-bdd6-08cfa91db256"
/dev/sda2: UUID="aa1bd239-062f-46b4-befe-b7abea46ac86" TYPE="swap" PARTLABEL="swap" PARTUUID="77da56fc-7879-408b-a4c6-5a1f5429dd31"
/dev/sda3: UUID="37c1972b-34fc-4d2f-aa58-00af50ad9048" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="root" PARTUUID="22c0ffd8-9629-466e-bcd3-84e1d764ab8e"
/dev/sda1: UUID="3076-A185" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="boot" PARTUUID="591548fb-503f-4b3d-91d5-14698215a6d3"

Head_on_a_Stick · 2024-12-14 13:48:51

Try

efibootmgr -o 1,2

The Fedora entry should be removed, it's no longer valid.

If you had shared Windows' ESP (/dev/nvme0n1p1) with Arch then systemd-boot would have created a menu entry for it automatically and you wouldn't need the Windows firmware boot entry at all.

theonlyone · 2024-12-14 13:52:57

i remove the fedora entry im gonna try to reboot now.

sudo efibootmgr -b 0003 --delete-bootnum

theonlyone · 2024-12-14 13:57:19

still nothing the boot order doesnt recognize EFI HARDDRIVE as a boot manager, im still manually booting using firmware boot option

Head_on_a_Stick · 2024-12-14 14:01:48

You could try a simple fake Fedora boot entry with GRUB:

grub-install --target=x86_64-efi --efi-directory=/boot --bootloader-id=fedora

But you might need to use the Shim as well.

EDIT: perhaps also check /sys/firmware/efi/efivars/ for dump files: https://wiki.archlinux.org/title/Unifie … iable_data

Last edited by Head_on_a_Stick (2024-12-14 14:06:09)

theonlyone · 2024-12-14 14:04:14

Head_on_a_Stick wrote:

Try
efibootmgr -o 1,2
The Fedora entry should be removed, it's no longer valid.
If you had shared Windows' ESP (/dev/nvme0n1p1) with Arch then systemd-boot would have created a menu entry for it automatically and you wouldn't need the Windows firmware boot entry at all.

how can i share the windows esp? if thats easier?

theonlyone · 2024-12-14 14:07:03

Head_on_a_Stick wrote:

You could try a simple fake Fedora boot entry with GRUB:
grub-install --target=x86_64-efi --efi-directory=/boot --bootloader-id=fedora
But you might need to use the Shim as well.

the reason i moved away from grub was it wasn't signing the secureboot keys kept giving me an error ESP PATH not found even after manually directing path to esp and signing all keys grub still gave a secure boot violation error

Head_on_a_Stick · 2024-12-14 14:09:15

To share the Windows ESP mount it under /boot/ in the Arch system then re-install the kernel package(s) and re-run the bootloader installation command (eg, grub-install, bootctl install, etc) then modify /etc/fstab to reflect the new configuration.

theonlyone · 2024-12-14 14:11:50

Head_on_a_Stick wrote:

To share the Windows ESP mount it under /boot/ in the Arch system then re-install the kernel package(s) and re-run the bootloader installation command (eg, grub-install, bootctl install, etc) then modify /etc/fstab to reflect the new configuration.

i'll try that. thanks in advance

Head_on_a_Stick · 2024-12-14 14:19:34

Also copy over the configuration files from /dev/sda1. Forgot about those :-)

Arch Linux

#1 2024-12-14 13:16:01

Arch Boot Issue

#2 2024-12-14 13:29:10

Re: Arch Boot Issue

#3 2024-12-14 13:33:27

Re: Arch Boot Issue

#4 2024-12-14 13:35:37

Re: Arch Boot Issue

#5 2024-12-14 13:37:07

Re: Arch Boot Issue

#6 2024-12-14 13:40:18

Re: Arch Boot Issue

#7 2024-12-14 13:44:41

Re: Arch Boot Issue

#8 2024-12-14 13:46:10

Re: Arch Boot Issue

#9 2024-12-14 13:48:51

Re: Arch Boot Issue

#10 2024-12-14 13:52:57

Re: Arch Boot Issue

#11 2024-12-14 13:57:19

Re: Arch Boot Issue

#12 2024-12-14 14:01:48

Re: Arch Boot Issue

#13 2024-12-14 14:04:14

Re: Arch Boot Issue

#14 2024-12-14 14:07:03

Re: Arch Boot Issue

#15 2024-12-14 14:09:15

Re: Arch Boot Issue

#16 2024-12-14 14:11:50

Re: Arch Boot Issue

#17 2024-12-14 14:19:34

Re: Arch Boot Issue

Board footer