Boot failing with LTS kernel

General system Kernel, boot, graphics & hardware
5

I did run dracut-rebluid, but no change to the issue. But there are some good news although I don’t understand everything, this beyond my knowledge :

I forgot to mention I am using rEFInd to boot. My desktop is configured to dual-boot between Debian and EndeavourOS. On Debian, I have installed rEFInd a long time ago (thus only installed from Debian). Then I installed EndeavourOS some days ago, and I was able to boot EOS using rEFInd boot manager, so far so good (booting directly from the EOS boot loader, and not using GRUB).

Until this morning : as I said, I updated the EOS (pacman -Syu), and after a reboot, I got the system stuck with the “failed to mount /sysroot“ error.

After some more testing, here is what I observe :

  • If I select the /boot/efi/EFI/endeavouros/grubx64.efi option, I can boot EOS selecting LTS kernel. Note this is from the system EFI partition.
  • If I select the /boot/vmlinuz-linux-lts option, then I get the system stuck with “Failed to mount /sysroot“ error. Note this is from the system disk where EOS is installed.
  • I can boot from both Debian similar choices (Grub or Debian boot loader).

If I am correct, the 2nd option is to boot directly from the boot loader on the ext4 system partition (when the first one is the grub boot manager from FAT32 EFI partition).

Here is the content of the boot dir :

$ sudo ls -al /boot
total 217340
drwxr-xr-x  4 root root     4096 27 oct.  14:41 .
drwxr-xr-x 22 root root     4096 25 oct.  17:41 ..
-rw-r–r--  1 root root   184320 22 oct.  01:12 amd-ucode.img
drwxr-x—  3 root root     4096  1 janv.  1970 efi
drwxr-xr-x  6 root root     4096 14 oct.  16:32 grub
-rw-------  1 root root 62639144 27 oct.  14:41 initramfs-linux-fallback.img
-rw-------  1 root root 32729064 27 oct.  14:41 initramfs-linux.img
-rw-------  1 root root 62453688 27 oct.  14:40 initramfs-linux-lts-fallback.img
-rw-------  1 root root 34070862 27 oct.  14:40 initramfs-linux-lts.img
-rw-r–r--  1 root root 16523455 25 oct.  17:41 vmlinuz-linux
-rw-r–r--  1 root root 13918720 27 oct.  10:22 vmlinuz-linux-lts

Does that mean the vmlinuz-linux-lts file is wrong or corrupted somewhere ? timestamp is probably time of the system update this morning.

Here is where I am…