[SOLVED] Arch No Longer In UEFI Boot Priorities

atticarch · 2024-10-23 20:04:58

Might make typos because I'm writing this from a phone.

Battery in my device started swelling, so I removed it and reassembled it thereafter. Internals are fine and it boots up without issue. To the UEFI, that is: Linux needs to be manually booted via shell's startup.nsh, as it does not appear in the boot priorities.

In addition, Linux will no longer boot - not that I can tell, at least. I get to the internal menu where it asks me to choose between the fallback and main linux image. Regardless of what I pick, my monitor does not display anything - not even a "No Signal" message. Then again, my set-up has always been finicky due to its jerryrigged nature.

I don't believe I'm using grub, as I remember seeing systemd as a directory in the EFI folder. I'd really rather not reinstall arch, if possible.

Any help or pointers will be greatly appreciated.

Last edited by atticarch (2024-10-23 22:24:22)

kermit63 · 2024-10-23 20:37:56

That's expected behavior. The boot entry was erased when power to the nvram was cut off by the battery removal. You need to arch-chroot into your installation, mount the requisite partitions (root, efi, /boot if you have a separate boot partition), then recreate the boot entry, in the same way when you first installed the system.

You can look up the specifics in the arch wiki, depending on your preferred bootloader.

atticarch · 2024-10-23 20:52:40

kermit63 wrote:

That's expected behavior. The boot entry was erased when power to the nvram was cut off by the battery removal. You need to arch-chroot into your installation, mount the requisite partitions (root, efi, /boot if you have a separate boot partition), then recreate the boot entry, in the same way when you first installed the system.
You can look up the specifics in the arch wiki, depending on your preferred bootloader.

Thanks for the response. Would I be able to do that via UEFI's shell or would I need a bootable USB?

kermit63 · 2024-10-23 21:06:35

You need a bootable USB in order to chroot into the installation. Can't do that with UEFI shell.

atticarch · 2024-10-23 22:24:01

kermit63 wrote:

You need a bootable USB in order to chroot into the installation. Can't do that with UEFI shell.

Got it. Thanks again. I'll mark it solved.

Arch Linux

#1 2024-10-23 20:04:58

[SOLVED] Arch No Longer In UEFI Boot Priorities

#2 2024-10-23 20:37:56

Re: [SOLVED] Arch No Longer In UEFI Boot Priorities

#3 2024-10-23 20:52:40

Re: [SOLVED] Arch No Longer In UEFI Boot Priorities

#4 2024-10-23 21:06:35

Re: [SOLVED] Arch No Longer In UEFI Boot Priorities

#5 2024-10-23 22:24:01

Re: [SOLVED] Arch No Longer In UEFI Boot Priorities

Board footer