File /boot/vmlinuz-5.10-x86_64 not found

[stephane]

then can you
return

inxi -Fza
lsblk -fs
parted -l
cat /etc/fstab

[Avocari]

from the chrooted from live or in grub Shell?

[Wollie]

@Avocari

[core]
Server = http://ftp.hosteurope.de/mirror/ftp.archlinux.org/core/os/$arch

How could this happen? You most likely screwed your system with this setting. Manjaro is not Arch, mixing repos from different distros is a pretty safe way to irrevocable corrupt your filesystem. Even if you get your current issues fixed there might be hidden deficiencies. Better safe your data and reinstall.

[stephane]

from live

lsblk -fs

and in chroot

inxi -Fza
parted -l
cat /etc/fstab

[Avocari]

@Wollie

How could this happen?

I am totally not sure how this ended up here, as far as I am aware, I did not add it in on purpose in the last year.

[Wollie]

It’s not getting there from alone, please be honest.

[Avocari]

I am honest, as far as I can remember I never touched said file. But I know what you mean

[Avocari]

@stephane

from live

    ~  lsblk -fs                                                        ✔ 
NAME FSTYPE FSVER LABEL UUID                                 FSAVAIL FSUSE% MOUNTPOINT
sda1 vfat   FAT32       1ABC-8020                                           
└─sda
                                                                            
sda2 crypto 1           xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx                  
└─sda
                                                                            
sda3 crypto 1           xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx                
└─sda

[Wollie]

It’s not a problem to make a huge mistake (we all do from time to time ) but you should not hide it when you are looking for help. This would not be fair to the people trying to fix your issues.

Anyway, using a Arch core repo is most likely toxic. I would not say impossible to fix but risky as you never know if you covered all deficiencies. Better safe your valuable data and reinstall. Take it as lesson.

[Avocari]

I understand you, and I did not try to hide it. As soon as @stephane told me to look at the file, I saw the line and pointed it out so I think I tried to be as helpful as possible

[stephane]

are you using sda2 & sda 3 as raid 1 disk

[Avocari]

According to the infos I got in grub, sda3 seems to be labeld as a swap partition
Do you need anything special from inxi -Fza?

[stephane]

line boot kernel , and info about partition installed

[Avocari]

[manjaro-gnome /]# inxi -Fza
12System:
  12Kernel 5.9.16-1-MANJARO x86_64 12bits 64 12compiler gcc 12v 10.2.0
    12parameters BOOT_IMAGE=/boot/vmlinuz-x86_64 lang=en_US keytable=de tz=UTC misobasedir=manjaro
    misolabel=MANJARO_GNOME_2021 quiet systemd.show_status=1 driver=free nouveau.modeset=1
    i915.modeset=1 radeon.modeset=1
  12Desktop GNOME 41.2 12tk GTK 3.24.30 12wm gnome-shell 12dm N/A 12Distro Manjaro Linux 12base Arch Linux

12Partition:
  12ID-1 / 12raw-size 878.98 GiB 12size 864.19 GiB (98.32%) 12used 313.17 GiB (36.2%) 12fs ext4
    12block-size 4096 B 12dev /dev/dm-0 12maj-min 254:0 12mapped sda2
  12ID-2 /boot 12raw-size 300 MiB 12size 299.4 MiB (99.80%) 12used 73.6 MiB (24.6%) 12fs vfat
    12block-size 512 B 12dev /dev/sda1 12maj-min 8:1

[manjaro-gnome /]# parted -l
Model: ATA CT960BX500SSD1 (scsi)
Disk /dev/sda: 960GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End    Size    File system  Name  Flags
 1      2097kB  317MB  315MB   fat32              boot, esp
 2      317MB   944GB  944GB
 3      944GB   960GB  16.1GB

[manjaro-gnome /]# cat /etc/fstab 
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
#
# <file system>             <mount point>  <type>  <options>  <dump>  <pass>
UUID=1ABC-8020                            /boot/efi      vfat    umask=0077 0 2
/dev/mapper/luks-9e5cb524-9427-4a0a-b016-a428e44cdd8b /              ext4    defaults,noatime,discard 0 1
/dev/mapper/luks-399a5a8e-b6e2-4897-8a1c-ef88c1dd101c swap           swap    defaults,noatime,discard 0 2
tmpfs                                     /tmp           tmpfs   defaults,noatime,mode=1777 0 0

[stephane]

have applied this on chroot mount ?

Grub rescue: unknown filesystem

see this topic if you need to chroot for grub restore sudo su cryptsetup luksOpen /dev/sdaX crypto ( here volume mapper encrypted ) cryptsetup luksOpen /dev/sdaY swap ( case out encrypted ) mount /dev/mapper/crypto /mnt mount /dev/sda1 /mnt/boot/efi ( if you need Efi ) mount -t proc proc /mnt/proc mount -t sysfs sys /mnt/sys mount -o bind /dev /mnt/dev mount -t devpts pts /mnt/dev/pts/ chroot /mnt grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=manjaro --rech…

[Avocari]

mount boot to /mnt/boot/efi? As I see in mine I should be in folder efi right?

[Avocari]

Following at the end:

grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=manjaro --recheck --verbose
..............
grub-install: info: executing efibootmgr --version </dev/null >/dev/null.
grub-install: info: executing modprobe -q efivars.
EFI variables are not supported on this system.
grub-install: info: executing efibootmgr -c -d /dev/sda -p 1 -w -L manjaro -l \EFI\manjaro\grubx64.efi.
EFI variables are not supported on this system.
grub-install: error: efibootmgr failed to register the boot entry: No such file or directory.

[Avocari]

Looks like no efi then?

[stephane]

only if you need to re install grub and re create entry EFI

inxi -Mxa will tells you UEFI or something else

[Avocari]

inxi -Mxa gives me only info about my machine and there stands 12UEFI

I do not need to reinstall grub as far as I am aware.

I am still at the errors:

error: file '/boot/vmlinuz-5.10-x86_64' not found
error: you need to load the kernel first

But grub itself appears