EndeaveourOS not booting anymore after 2nd Linux installation

General system Kernel, boot, graphics & hardware
1

Hi EndeavourOS community,

I have been using EndeavourOS since some month and was mostly happy.
Some issues (another story) made me trying out Mint and I regret it right after the installation.
The Mint installation somehow corrupted the boot process of EndeavourOS.
I could get the grub boot entry back by updating grub.
But when selecting it I get the error:

error: file `/boot/vmlinuz-linux' not found.
error: you need to load the kernel first.

I tried boot-repair from Mint, but this failed to solve the issue: https://paste.ubuntu.com/p/JMF87JkdZb/

Then I tried to solve it from a USB with the EndeavourOS, but got stuck as well.
I tried these steps:

sudo mount /dev/nvme0n1p1 /mnt/boot/efi
sudo mount --bind /dev /mnt/dev
sudo mount --bind /proc /mnt/proc
sudo mount --bind /sys /mnt/sys
sudo mount --bind /run /mnt/run
sudo chroot /mnt
grub-install /dev/nvme0n1

The last command gives a failure:

[root@EndeavourOS /]# grub-install /dev/nvme0n1
Installing for x86_64-efi platform.
EFI variables are not supported on this system.
EFI variables are not supported on this system.
grub-install: error: efibootmgr failed to register the boot entry: No such file or directory.

Can someone guide me to what I need to do, to get EndeavourOS running again?

2

You cant use chroot on arch based. It has to be arch-chroot booting off a live usb of EOS. Also Mint doesn’t play well with arch based distros as far as the boot loaders go. Therefore it is better to let EOS be in control of the boot process. Also not sure if you installed in UEFI or Bios both on Mint and EOS.

Edit:

https://discovery.endeavouros.com/system-rescue/arch-chroot/2022/12/

This is an example if you installed EOS with grub. The default EOS install is systemd-boot.

sudo mount /dev/nvme0n1p2 /mnt ( Root of installed endeavouros)
sudo mount /dev/nvme)n1p1 /boot/efi/ /mnt

sudo arch-chroot /mnt

Hopefully i have this right flying off the top of my head but I would defer to @pebcak since he is more knowledgable on the fly.

Edit: You could post lsblk -f from the live ISO

1 Like
3

Screenshot from 2024-07-23 06-26-14
Screenshot from 2024-07-23 06-26-14904×593 58.8 KB

:thinking:

You would need to mount your root/system partition first before mounting your ESP.
Then using sudo arch-chroot /mnt makes all of the following unnecessary:

sudo mount --bind /dev /mnt/dev
sudo mount --bind /proc /mnt/proc
sudo mount --bind /sys /mnt/sys
sudo mount --bind /run /mnt/run
sudo chroot /mnt

:arrow_right: https://wiki.archlinux.org/title/Chroot

At any rates, in order to being able to give more precise instructions, we would need some more additional info.

From your EnOS live session, post the output of the following commands.
Also, if using several disks, please indicate on which one your EnOS is installed.

sudo parted -l
efibootmgr
1 Like
4

Thank you for your feedback.
I decided to install EnOS on the partitions where I have tested Mint.
The older EnOS installation was not detected automatically, so I will try following the explanations from the links you gave above to reactivate it.