To revert, perform these again but set boot flag for /dev/sda2.
Oh, I must have misunderstood. No, I can’t get it to boot from UEFI mode at all. I get media fail, no boot device found from both the EN and Windows isos. If I use legacy, I could boot with either.
If I don’t use a USB and try to boot normally, using legacy, it now says missing operating system. This is after I used the live EN iso, used gparted, and then set the flag on sda1 to boot.
Before, I could boot into windows normally. Now, my only option is to boot legacy with EN live iso
Did you see my last post?
Yes, I set boot on sda2, restarted. It then booted back into windows—I’m learning lol, thanks.
You would need to re-install EnOS’ bootloader in order to be able to boot it up.
Have a look at the article linked to below and follow the instructions for the BIOS/Legacy system:
https://discovery.endeavouros.com/system-rescue/repair-a-non-booting-grub/2021/03/
If anything is unclear, post about it.
I should have posted these two guides way earlier…
Boot En Live ISO, follow 1st guide for chrooting and 2nd one (repair GRUB on BIOS systems only) for reinstalling bootloader. If you get stuck, feel free to reply back.
https://discovery.endeavouros.com/system-rescue/arch-chroot-for-bios-legacy-systems/2021/03/
https://discovery.endeavouros.com/system-rescue/repair-a-non-booting-grub/2021/03/
CSM does need to be disabled as some systems will install in dos mode with it enabled. Settings should be set to UEFI only and secure boot disabled. Proper creation of the live usb is also a factor. Some methods just don’t work properly in some instances.
OP has Windows installed in CSM / BIOS mode. CSM should remain enabled in order to dual boot with Windows.
Thanks. I just can’t get that BIOS to read from a USB in UEFI no matter what I try. I tried making iso bootable disks in balenca, ventoy, win2grub….
It’s a Dell Inspiron 5500 series, A6 bios if that makes a difference.
Any suggestions?
Thank you, these help.
The second tutorial, when I enter >sudo grub-mkconfig -o /boot/grub/grub.cfg
I get the error ‘failed to get the canonical path of ‘airootfs’
Did you arch-chroot correctly?
1. sudo mount /dev/sda1 /mnt
2. sudo arch-chroot /mnt
3. grub-install --target=i386-pc /dev/sda
4. grub-mkconfig -o /boot/grub/grub.cfg
5. exit
1 Like
Ah, I see what I did. I exited the terminal after part one, and didn’t go into chroot for part 2.
Grub shows up now, but only option is Windows 10. When I try to install EN via live iso I don’t have the alongside option. Just replace, erase, and manual.
On GRUB, hit “c” and type these:
linux /boot/vmlinuz-linux root=/dev/sda1
initrd /boot/initramfs-linux
boot
1 Like
I am not sure but isn’t “Install alongside” for when the whole disk is occupied with another system so the installer would need to shrink the size of the other system first and so on?
I might be mistaken though.
If you need to reinstall:
Choose replace partition and point the installer to /dev/sda1.
Choose the MBR of the disk, that is /dev/sda (no number here) as the location for the installation of the bootloader.
Almost there, I can feel it.
Error: file ‘/boot/initramfs-Linux’ not found.
In chroot:
pacman -Syu linux linux-headers
mkinitcpio -p linux
grub-mkconfig -o /boot/grub/grub.cfg
exit
Reboot.
This is weird. System is updating and I get a PGP key from David Runge? A bunch of errors that say package blah blah .pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)) delete y/n. If I say yes, I get the message signature from David Runge is marginal trust.
Install archlinux-keyring first.
Still in chroot:
pacman -Sy archlinux-keyring
Then:
pacman -Su linux linux-headers
mkinitcpio -p linux
grub-mkconfig -o /boot/grub/grub.cfg
exit
Reboot.
Grr!
All went well (lots and lots of updates) but grub-config-mkconfig -o /boot/grub/grub.cfg returns
/usr/bin/grub-probe: error: failed to get canonical path of ‘airootfs’
I tried in both chroot (sudo su) and using sudo commands in both root and as liveuser.
Man, what am I missing?
Don’t know.
This indicates that you are not in chroot if I am not mistaken.
Let’s do it from the square one again.
In the live session, open a terminal and do the following:
1. sudo mount /dev/sda1 /mnt
2. sudo arch-chroot /mnt
3. pacman -Sy archlinux-keyring
4. pacman -Su linux linux-headers
5. mkinitcpio -p linux
6. grub-install --target=i386-pc /dev/sda
7. grub-mkconfig -o /boot/grub/grub.cfg
8. exit
Reboot.
If this won’t work then there must be some more deeply laying issue on your install.
In lack of better suggestions (speaking for myself), I would personally re-install the system at this stage.