I recently updated my PC (EndeavorOS) after a month of being away and I ran a system upgrade which upgraded grub. I heard about the config changes earlier but i forgot to run the commands that regenerated an updated grub config - so now my PC keeps booting to UEFI. What do I need to do to fix my config so I can go back to booting my OS (I'm currently on a EndeavorOS live install environment to run commands).
#[SOLVED] GRUB issues
46 messages · Page 1 of 1 (latest)
mount all of your drives to /mnt and run grub-install
so root is mounted to /mnt/, boot is mounted to /mnt/boot (or wherever yours is normally)
my disk seems to be already mounted at /run/media/liveuser/81697fa1-0101-4adc-b6ca-3dcf26a228fc/
should i still move it over or to /mnt or just use it there
is your boot partition mounted?
no, only my root partition and other disk
ok, could you mount your boot partition relative to the root partition? for example, /run/media/liveuser/81697fa1-0101-4adc-b6ca-3dcf26a228fc/boot or /run/media/liveuser/81697fa1-0101-4adc-b6ca-3dcf26a228fc/boot/efi
both of those already exist already
yes i know. Which one is your boot partition usually mounted to?
whatever is default ig, i didnt set it up specifically
ok i am guessing it'll be /boot/efi. could you mount your boot partition to it? sudo mount <bootPart> /run/media/liveuser/81697fa1-0101-4adc-b6ca-3dcf26a228fc/boot/efi
just done that, is there supposed to be a nested EFI directory or should i have mounted to .../boot instead
is there anything in the .../boot folder?
ok this looks good. could you now run sudo arch-chroot /run/media/liveuser/81697fa1-0101-4adc-b6ca-3dcf26a228fc/
/boot/efi/EFI/boot looks a bit wrong, is it supposed to be like that
pasted the wrong screenshot
ok
once you do that command, go ahead and run grub-install
grub-install --target=x86_64-efi --efi-directory=esp --bootloader-id=GRUB sorry
.. grub-issue
Too few arguments for command addnote!
Usage: .addnote <name> <text>
are you not running on efi?
i think i should be, my pc isnt that old
hm was i supposed to use a different bootloader id than GRUB, theres a similar directory named endeavouros-1895 already there
with a grubx64.efi
shouldn't change anything. You shouldn't be gettiing that efi error
That’s what I was trying to link, I need to get used to qbot again
followed those instructions, i still get the same EFI variables not supported error
would this have something to do with me using ventoy to boot into the live environment, i dont think so
i have no idea why this is reporting as BIOS and not UEFI hmm
i just rebooted and now I see this:
this makes sense why it says bios lol
yep it was a ventoy issue, i got another drive and flashed the endeavor iso to it and it just worked
Please can you mark this as solved if it is solved by changing the title to start with [solved]