Ah, thanks I wouldn’t have gotten that. Just making sure before I go messing something up, this is all inside the arch-chroot, right?
If you are still able to boot using systemd-boot you can can do it from there which is probably easier, but if not from a chroot.
Don’t do this if you are dual-booting Windows.
I keep forgotting about Windows ![]()
Then it’s better to just remove the endeavouros files, so that the Windows efi files don’t get deleted.
/boot/efi/EFI/endeavouros
Does the Windows installer also automatically place the Windows efi files on the first disk it can find?
doing this now and I’m a little confused. You’re making them immediately removing efi. Sure enough it says it can’t make /boot/efi since it already exists.
You didn’t see @dalto’s reply I forgot about Windows!! delete /boot/efi/EFI/endeavouros instead.
Don’t worry, I saw that. I’m still on line two since it says that directory already exists.
Then you can just skip that line to and go on with the rest, what’s actually in that directory when you look with ls before you mount it?
ls /boot/efi
mount /dev/nvme0n1p1 /boot/efi
rm -rf /boot/efi/EFI/endeavouros
efibootmgr -B -b 0003
grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=EndeavourOS
grub-mkconfig -o /boot/grub/grub.cfg
reboot
Tried it and restarted. Same result, unfortunately. ![]()
You did this /boot/efi/EFI/endeavouros right instead of what I mentioned before and what does /boot/efi/EFI look like now? Was there anything in /boot/efi before you mounted it?
I’m not sure what was there before, but interestingly I just looked and there’s nothing there now. /boot/efi is empty
Did you mean it is empty when mounted or unmounted and you didn’t run rm -rf /boot/efi I hope?
just arch-chrooting in then cding it shows as empty. Also no, I ran it for endeavour specifically and that went properly.
What does /boot/efi/EFI look like now, can you share the output of ls /boot/efi/EFI when /boot/efi is mounted?
Just mounted it (sounds obvious now) and it has
BOOT EndeavourOS Linux systemd
Is your EndeavourOS install actually still a fresh install with no personal data placed yet or other programs than the ones places by the installation?
All of my personal stuff that I very much cannot afford to lose ![]()
Might be a good idea to chroot into your system, connect a usb hard drive and back a backup of all of your files to that usb hard drive just in case?
I’m not keen on buying another 2tb but it’s starting to look like a sensible option.
I’m thinking at this point I call it a day and try load my timeshift (not sure that’ll work here given last time I tried, though, and worried it’d make things worse)