You are not logged in.
I'm not sure if this topic is appropriate for the Newbie corner or not but:
I have an Intel i7 10710u NUC. I have three ssd's: Arch linux, macOS, and windows. They all boot UEFI and have their own EFI partitions, so they can boot independently of each other. The NUC has only one tray for an SSD, so when I want to boot to another OS, I unplug the current SSD and plug in the desired one to boot. I know this is stupid, please bear with me. I've been having no problems at all for the past month or so. Yesterday, I unplugged the Arch ssd and swapped to macOS, but when swapping back to Arch it would no longer boot. Specifically, the Arch SSD is no longer detected by the BIOS as bootable, but it is detected as a hardware device because it offers to flash the BIOS using the SSD as a source.
I have a rEFInd USB that does detect the Arch SSD as bootable, and boots off of it just fine.
I checked the boot flags on the Arch SSD and the EFI partition boot flag is still set.
I have no idea why this is happening. Right now the only way to boot to my Arch SSD is by booting to the rEFInd usb which can chainboot to the Arch EFI partition.
Any ideas on why this could be happening? Please let me know if there are any tests I can run to give any further information.
Thanks in advance.
Last edited by enricozb (2020-09-05 16:38:47)
Offline
I think I've solved it. For some reason the NVRAM boot entry for the archlinux boot was deleted, or overwritten. Not sure what could have caused this. On the Arch SSD I boot from /EFI/refind/refind_x64.efi on the ESP. So, I had to re-add that entry with
sudo efibootmgr -c -l \\EFI\\refind\\refind_x64.efi -L rEFIndAccording to the troubleshooting section of the EFISTUB arch wiki page, it looks like "Some motherboards may remove boot entries after a couple of boots.", so maybe this is what was causing it. I've removed extra entries that I don't use, and hopefully this won't happen again.
Last edited by enricozb (2020-09-05 16:43:44)
Offline