Install Kernel in chroot

Hello everyone.

I know, this topic sounds too basic to ask for help but i have trouble with it and don’t see my mistake.

What happened:
After the usual updates, the next reboot grub can’t find any kernel anymore.

What i want:
Booting with Live Manjaro USB stick and chroot into my broken installed one.
Then i want to install a working kernel to fix everything.

What i try and don’t work:

[manjaro@manjaro ~]$ sudo cryptsetup luksOpen /dev/nvme0n1p2 root
Enter passphrase for /dev/nvme0n1p2: 
[manjaro@manjaro ~]$ sudo mkdir /chroot
[manjaro@manjaro ~]$ sudo mount /dev/mapper/root /chroot
[manjaro@manjaro ~]$ sudo mount /dev/nvme0n1p1 /chroot/boot/efi
[manjaro@manjaro ~]$ lsblk
loop0         7:0    0 129.4M  1 loop  /run/miso/sfs/livefs
loop1         7:1    0 579.2M  1 loop  /run/miso/sfs/mhwdfs
loop2         7:2    0   1.5G  1 loop  /run/miso/sfs/desktopfs
loop3         7:3    0 694.1M  1 loop  /run/miso/sfs/rootfs
sda           8:0    0 931.5G  0 disk  
sdb           8:16   1  28.6G  0 disk  
├─sdb1        8:17   1   1.6G  0 part  
├─sdb2        8:18   1   3.9M  0 part  
└─sdb3        8:19   1  27.1G  0 part  
sdc           8:32   1   7.5G  0 disk  /run/miso/bootmnt
├─sdc1        8:33   1   2.9G  0 part  
└─sdc2        8:34   1     4M  0 part  
nvme0n1     259:0    0 238.5G  0 disk  
├─nvme0n1p1 259:1    0   300M  0 part  /chroot/boot/efi
└─nvme0n1p2 259:2    0 238.2G  0 part  
  └─root    254:0    0 238.2G  0 crypt /chroot
[manjaro@manjaro ~]$ manjaro-chroot -a
grub-probe: error: cannot find a GRUB drive for /dev/sdc1.  Check your
grub-probe: error: cannot find a GRUB drive for /dev/sdc1.  Check your
==> ERROR: No Linux partitions detected!
[manjaro@manjaro ~]$ manjaro-chroot /chroot
sh-5.1# ls
bin		    dev   lib	      opt	       run   tmp
boot		    etc   lib64       proc	       sbin  usr
crypto_keyfile.bin  file  lost+found  root	       srv   var
desktopfs-pkgs.txt  home  mnt	      rootfs-pkgs.txt  sys
sh-5.1# rm -f /var/lib/pacman/db.lck
sh-5.1# ping -c 4
PING (2a00:1450:4005:80b::2003)) 56 data bytes
64 bytes from (2a00:1450:4005:80b::2003): icmp_seq=1 ttl=115 time=22.2 ms
64 bytes from (2a00:1450:4005:80b::2003): icmp_seq=2 ttl=115 time=19.0 ms
64 bytes from (2a00:1450:4005:80b::2003): icmp_seq=3 ttl=115 time=17.5 ms
64 bytes from (2a00:1450:4005:80b::2003): icmp_seq=4 ttl=115 time=20.7 ms

--- ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3005ms
rtt min/avg/max/mdev = 17.468/19.837/22.203/1.776 ms
sh-5.1# pacstrap / base
sh: pacstrap: command not found
sh-5.1# pacman -Syyu
sh-5.1# mhwd-kernel -li
Currently running: 5.13.15-1-MANJARO (linux513)
The following kernels are installed in your system:
sh-5.1# uname -a
Linux manjaro 5.13.15-1-MANJARO #1 SMP PREEMPT Wed Sep 8 14:12:50 UTC 2021 x86_64 GNU/Linux
sh-5.1# mhwd-kernel -i linux510
Error: Please make sure if the given kernel(s) exist(s).
available kernels:
sh-5.1# pacman -Syu linux510
sh-5.1# pacman -Syu --debug linux510
sh-5.1# mkinitcpio -p linux
sh-5.1# update-grub
Generating grub configuration file ...
Found theme: /usr/share/grub/themes/manjaro/theme.txt
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot entries.
Adding boot menu entry for UEFI Firmware Settings ...
Found memtest86+ image: /boot/memtest86+/memtest.bin
sh-5.1# exit
[manjaro@manjaro ~]$ 

Maybe good to know:

  • Using full encryption with Luks + LVM
  • Using UEFI + Secure Boot

What i am doing wrong?
Why is pacman so silent?

Please help me out!

With best regards,

What’s the contents of /boot ?

What happens, while in the chroot, if you check for available kernels?

mhwd-kernel -l

While in the chroot, can you also apply the fixes explained by @philm in the updates announcement:

After doing the above, then try again to install a kernel inside the chroot. (Such as linux510 and/or linux514)

Welcome to the forum!

This. :point_up:

Manjaro does not support Secure Boot, and to be honest, Secure Boot is pointless anyway ─ its restrictions have already been bypassed. Do yourself a favor and disable that abomination.

UEFI in and of itself is okay and fully supported, but you don’t need to have Secure Boot enabled in order to be able to boot in native UEFI mode. :wink:


This has nothing to do with Secure Boot. What’s pointless is your proclamations irrelevant to the topic being discussed lol. Speaking of topic, the problem is apparently between the monitor and the chair:

See no LVM here. There should be something like mount /dev/root/%your_root_volume% /chroot or mount /dev/mapper/root-%your_root_volume% /chroot instead. Also I would have not trusted manjaro-chroot utility when dealing with complicated setups. Use a regular chroot, mount devices one by one as per Arch Wiki guidelines.

PS: sorry @Aragorn but the above SB BS is really out of place and you know that.