You are not logged in.
Pages: 1
Ok, here is where I am at...
I have a desktop with 2 HDs. The primary HD had Windows 8.1 on it set to EFI boot with an EFI partition on it. The secondary HD had Arch Linux on it, set to EFI boot with it's own EFI partition and Gummiboot. I used the BIOS to let me select which HD I would boot off of, and all was well.
I did an upgrade to Windows 10, told it to "Keep Nothing" and install only on the primary drive. Well...
Windows 10 did the upgrade, removed the EFI partition off the primary drive, and decided to use the secondary partition's EFI partition for it's own boot.
So, now I have only one EFI partition.
How do I get Arch to boot again?
Offline
Re-install gummiboot (now called systemd-boot).
Now that the ESP is shared you should even get a menu entry for Windows in gummiboot.
Jin, Jîyan, Azadî
Offline
So, I just need to reinstall systemd-boot? I don't need to get the kernel back on the EFI partition?
I just don't want Windows 10 to deactivate. I don't understand why it even exists any more. The new Windows 10 model is that you're the revenue stream.
Offline
I don't need to get the kernel back on the EFI partition?
That depends -- is the kernel image (& initramfs) still on the ESP?
All your Arch files should still be there unless Windows re-formatted the partition.
If they're all gone then yes, you will have to re-install the kernel as well (make sure /boot is mounted correctly before doing this).
Jin, Jîyan, Azadî
Offline
I guess I need to boot off a Arch ISO and see what's going on.
According the Arch wiki, Windows 8.x and newer will always set itself as the default boot every time you boot into Windows. Need to make sure this doesn't mean systemd-boot is going to need to get reinstalled every time I boot Windows. Cause that would be really annoying.
Offline
According the Arch wiki, Windows 8.x and newer will always set itself as the default boot every time you boot into Windows. Need to make sure this doesn't mean systemd-boot is going to need to get reinstalled every time I boot Windows. Cause that would be really annoying.
I had Windows 10 (preview version) booting alongside Debian & Arch and it never did that.
Even if that does happen to you, to restore the boot order just use:
# efibootmgr -o xxxx,yyyy,zzzz
Replace "xxxx,yyyy,zzzz" with the actual Bootnumbers of the respective systems (run `efibootmgr` with no arguments to list all NVRAM entries with their Bootnumbers) -- see efibootmgr(8)
This can be done from the live environment.
Jin, Jîyan, Azadî
Offline
Pages: 1