System unbootable after upgrade from 5.9 > 5.10

Support Kernel
1

i,

I’d been running 5.9.16-1 for the last 5 months no issue but saw that it was no longer supported so I updated my kernel to 5.10 LTS.

After installing the newer kernel and rebooted I got the following error on screen:

EFI stub: ERROR: Failed to open file initramfs-5.10-x86_64.img
EFI stub: ERROR: Failed to load initrd!
EFI stub: ERROR: efi_main() failed

Failed to execute Manjaro Linux 5.10(\Manjaro\vmlinuz-5.10-x86_64): Not found

Dropped into a chroot session and I can provide the following:

mhwd-kernel -li

The following kernels are installed in your system:
* linux510
* linux511
* linux54
* linux59

inxi -Fza 
System:    Kernel: 5.6.15-1-MANJARO x86_64 bits: 64 compiler: gcc v: 10.1.0 
           parameters: BOOT_IMAGE=/boot/vmlinuz-x86_64 lang=en_US keytable=us tz=UTC driver=free nouveau.modeset=1 
           i915.modeset=1 radeon.modeset=1 misobasedir=manjaro misolabel=MANJARO_ARCHITECT_2003 quiet systemd.show_status=1 
           Console: tty 1 Distro: Manjaro Linux base: Arch Linux 
Machine:   Type: Laptop System: Notebook product: PCX0DX v: N/A serial: N/A Chassis: type: 10 serial: N/A 
           Mobo: Notebook model: PCX0DX serial: N/A UEFI: INSYDE v: 1.07.07 date: 06/17/2020 
Battery:   ID-1: BAT0 charge: 70.3 Wh (100.0%) condition: 70.3/70.7 Wh (99.5%) volts: 12.8 min: 11.4 model: Notebook BAT 
           type: Li-ion serial: <filter> status: Full 
CPU:       Info: 8-Core model: Intel Core i7-10875H socket: U3E1 bits: 64 type: MT MCP arch: Comet Lake family: 6 
           model-id: A5 (165) stepping: 2 microcode: C8 cache: L2: 16 MiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 73625 
           Speed: 900 MHz min/max: 800/5100 MHz base/boost: 2178/8300 volts: 0.8 V ext-clock: 100 MHz Core speeds (MHz): 
           1: 900 2: 901 3: 900 4: 900 5: 901 6: 900 7: 901 8: 900 9: 900 10: 900 11: 901 12: 900 13: 900 14: 900 15: 901 
           16: 900 
           Vulnerabilities: Type: itlb_multihit status: KVM: Split huge pages 
           Type: l1tf status: Not affected 
           Type: mds status: Not affected 
           Type: meltdown status: Not affected 
           Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl and seccomp 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Enhanced IBRS, IBPB: conditional, RSB filling 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: Intel UHD Graphics vendor: CLEVO/KAPOK driver: i915 v: kernel bus-ID: 00:02.0 chip-ID: 8086:9bc4 
           class-ID: 0300 
           Device-2: NVIDIA TU106M [GeForce RTX 2060 Mobile] vendor: CLEVO/KAPOK driver: nouveau v: kernel bus-ID: 01:00.0 
           chip-ID: 10de:1f15 class-ID: 0300 
           Device-3: Acer BisonCam NB Pro type: USB driver: uvcvideo bus-ID: 1-8:2 chip-ID: 5986:9102 class-ID: 0e02 
           Display: server: X.org 1.20.11 driver: loaded: modesetting alternate: fbdev,intel,vesa tty: 240x67 
           Message: Advanced graphics data unavailable in console for root. 
Audio:     Device-1: Intel Comet Lake PCH cAVS vendor: CLEVO/KAPOK driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 
           chip-ID: 8086:06c8 class-ID: 0403 
           Device-2: NVIDIA TU106 High Definition Audio vendor: CLEVO/KAPOK driver: snd_hda_intel v: kernel bus-ID: 01:00.1 
           chip-ID: 10de:10f9 class-ID: 0403 
           Sound Server-1: ALSA v: k5.6.15-1-MANJARO running: yes 
           Sound Server-2: JACK v: 0.125.0 running: no 
           Sound Server-3: PulseAudio v: 14.2 running: no 
           Sound Server-4: PipeWire v: 0.3.26 running: no 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: CLEVO/KAPOK driver: r8169 v: kernel 
           port: 3000 bus-ID: 42:00.0 chip-ID: 10ec:8168 class-ID: 0200 
           IF: enp66s0 state: down mac: <filter> 
           Device-2: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel port: 3000 bus-ID: 44:00.0 chip-ID: 8086:2723 
           class-ID: 0280 
           IF: wlp68s0 state: down mac: <filter> 
Bluetooth: Device-1: Intel AX200 Bluetooth type: USB driver: btusb v: 0.8 bus-ID: 1-14:4 chip-ID: 8087:0029 class-ID: e001 
           Report: rfkill ID: hci0 rfk-id: 1 state: down bt-service: N/A rfk-block: hardware: no software: no 
           address: see --recommends 
Drives:    Local Storage: total: 5.51 TiB used: 996.62 GiB (17.7%) 
           ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Western Digital model: WDS100T2B0C-00PXH0 size: 931.51 GiB block-size: 
           physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 rotation: SSD serial: <filter> rev: 211070WD temp: 39.9 C 
           SMART: yes health: PASSED on: 52d 12h cycles: 253 read-units: 180,178 [92.2 GB] written-units: 1,549,517 [793 GB] 
           ID-2: /dev/nvme1n1 maj-min: 259:2 vendor: Samsung model: SSD 970 EVO 1TB size: 931.51 GiB block-size: 
           physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 rotation: SSD serial: <filter> rev: 2B2QEXE7 temp: 38.9 C 
           SMART: yes health: PASSED on: 78d 18h cycles: 185 read-units: 242,546 [124 GB] written-units: 2,433,114 [1.24 TB] 
           ID-3: /dev/sda maj-min: 8:0 type: USB vendor: Seagate model: BUP BK size: 3.64 TiB block-size: physical: 4096 B 
           logical: 512 B serial: <filter> rev: 0304 
           SMART Message: A mandatory SMART command failed. Various possible causes. 
           ID-4: /dev/sdb maj-min: 8:16 type: USB vendor: SanDisk model: Ultra size: 57.28 GiB block-size: physical: 512 B 
           logical: 512 B serial: <filter> rev: 1.00 
           SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure? 
Partition: ID-1: / raw-size: 100 GiB size: 97.93 GiB (97.93%) used: 30.19 GiB (30.8%) fs: ext4 block-size: 4096 B 
           dev: /dev/dm-6 maj-min: 254:6 mapped: vg02-lvol--root 
           ID-2: /boot raw-size: 767 MiB size: 765.5 MiB (99.80%) used: 593.6 MiB (77.5%) fs: vfat block-size: 512 B 
           dev: /dev/nvme1n1p1 maj-min: 259:3 
           ID-3: /home raw-size: 10 GiB size: 9.78 GiB (97.81%) used: 262.9 MiB (2.6%) fs: ext4 block-size: 4096 B 
           dev: /dev/dm-7 maj-min: 254:7 mapped: vg02-lvol--home 
Swap:      Alert: No swap data was found. 
Sensors:   System Temperatures: cpu: 66.0 C mobo: N/A gpu: nouveau temp: 44.0 C 
           Fan Speeds (RPM): N/A 
Info:      Processes: 311 Uptime: 2m wakeups: 1 Memory: 31.06 GiB used: 912.1 MiB (2.9%) Init: systemd v: 247 tool: systemctl 
           Compilers: gcc: 10.2.0 Packages: 1443 pacman: 1422 lib: 399 flatpak: 21 Shell: systemd (sudo) running-in: tty 1 
           inxi: 3.3.04
ls /boot/*

/boot/amd-ucode.img
/boot/initramfs-5.4-x86_64-fallback.img
/boot/initramfs-5.4-x86_64.img
/boot/initramfs-5.9-x86_64-fallback.img
/boot/initramfs-5.9-x86_64.img
/boot/intel-ucode.img
/boot/linux54-x86_64.kver
/boot/linux59-x86_64.kver
/boot/vmlinuz-5.4-x86_64
/boot/vmlinuz-5.9-x86_64

/boot/EFI:
BOOT
Linux
systemd

/boot/Manjaro:
amd-ucode.img
initramfs-5.10-x86_64-fallback.img
initramfs-5.10-x86_64.img
initramfs-5.11-x86_64-fallback.img
initramfs-5.11-x86_64.img
initramfs-5.4-x86_64-fallback.img
initramfs-5.4-x86_64.img
intel-ucode.img
linux510-x86_64.kver
linux511-x86_64.kver
linux54-x86_64.kver
vmlinuz-5.10-x86_64
vmlinuz-5.11-x86_64
vmlinuz-5.4-x86_64

/boot/loader:
entries
loader.conf
random-seed

/boot/memtest86+:
memtest.bin

parted -l

Model: WDC WDS100T2B0C-00PXH0 (nvme)
Disk /dev/nvme0n1: 1000GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:

Number Start End Size File system Name Flags
1 1049kB 1000GB 1000GB Linux LVM lvm

Model: Samsung SSD 970 EVO 1TB (nvme)
Disk /dev/nvme1n1: 1000GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:

Number Start End Size File system Name Flags
1 1049kB 805MB 804MB fat32 EFI system partition boot, esp
2 806MB 1000GB 999GB Linux LVM lvm

Any help on what I can do to resolve would be much appreciated.

TIA
Jade

2

Hello @Jade1 :wink:

Question: Why is it installed under:

and not under /boot ?

Which bootloader do you use? grub or systemd-boot?

Normally mhwd just triggers grub by a hook and not systemd-boot.

If it is systemd-boot, then have a look here: systemd-boot - ArchWiki

3

you have to remove version linux5.9 also modules from version 5.9

sudo mhwd-kernel -r linux59
ls /lib/modules
4

Thanks for your response megavolt. I based my installation on the instructions in Manjaro install fully encrypted

I use systemd-boot as the bootloader

5

I’m concerned that if I remove 5.9 then I won’t even be able to use the system at all. I’m not able to boot using 5.10 or 5.11 so 5.9 is the only fallback I have.

ls -l /lib/modules
total 32
drwxr-xr-x 4 root root 4096 May 12 22:18 5.10.34-1-MANJARO
drwxr-xr-x 4 root root 4096 May 12 22:26 5.11.18-1-MANJARO
drwxr-xr-x 4 root root 4096 May 10 11:37 5.4.116-1-MANJARO
drwxr-xr-x 4 root root 4096 Jan 8 11:27 5.9.16-1-MANJARO
drwxr-xr-x 2 root root 4096 May 12 22:18 extramodules-5.10-MANJARO
drwxr-xr-x 2 root root 4096 May 12 22:26 extramodules-5.11-MANJARO
drwxr-xr-x 2 root root 4096 May 10 11:37 extramodules-5.4-MANJARO
drwxr-xr-x 2 root root 4096 May 10 11:36 extramodules-5.9-MANJARO

6

Here’s what I have when I do

bootctl list

title: Manjaro Linux 5.9 (manjarolinux5.9.conf)
id: manjarolinux5.9.conf
source: /efi/loader/entries/manjarolinux5.9.conf
linux: /vmlinuz-5.9-x86_64
initrd: /amd-ucode.img
/intel-ucode.img
/Manjaro/amd-ucode.img
/Manjaro/intel-ucode.img
/initramfs-5.9-x86_64.img
options: root=UUID=c4cf79bc-b324-4058-83ba-bead81dc6c08 rw

    title: Manjaro Linux 5.10 (manjarolinux5.10-fallback.conf)
       id: manjarolinux5.10-fallback.conf
   source: /efi/loader/entries/manjarolinux5.10-fallback.conf
    linux: /Manjaro/vmlinuz-5.10-x86_64
   initrd: /amd-ucode.img
           /intel-ucode.img
           /Manjaro/amd-ucode.img
           /Manjaro/intel-ucode.img
           /initramfs-5.10-x86_64-fallback.img (No such file or directory)
  options: root=UUID=c4cf79bc-b324-4058-83ba-bead81dc6c08 rw

    title: Manjaro Linux 5.10 (manjarolinux5.10.conf)
       id: manjarolinux5.10.conf
   source: /efi/loader/entries/manjarolinux5.10.conf
    linux: /Manjaro/vmlinuz-5.10-x86_64
   initrd: /amd-ucode.img
           /intel-ucode.img
           /Manjaro/amd-ucode.img
           /Manjaro/intel-ucode.img
           /initramfs-5.10-x86_64.img (No such file or directory)
  options: root=UUID=c4cf79bc-b324-4058-83ba-bead81dc6c08 rw

    title: Manjaro Linux 5.11 (manjarolinux5.11-fallback.conf)
       id: manjarolinux5.11-fallback.conf
   source: /efi/loader/entries/manjarolinux5.11-fallback.conf
    linux: /Manjaro/vmlinuz-5.11-x86_64
   initrd: /amd-ucode.img
           /intel-ucode.img
           /Manjaro/amd-ucode.img
           /Manjaro/intel-ucode.img
           /initramfs-5.11-x86_64-fallback.img (No such file or directory)
  options: root=UUID=c4cf79bc-b324-4058-83ba-bead81dc6c08 rw

    title: Manjaro Linux 5.11 (manjarolinux5.11.conf) (default)
       id: manjarolinux5.11.conf
   source: /efi/loader/entries/manjarolinux5.11.conf
    linux: /Manjaro/vmlinuz-5.11-x86_64
   initrd: /amd-ucode.img
           /intel-ucode.img
           /Manjaro/amd-ucode.img
           /Manjaro/intel-ucode.img
           /initramfs-5.11-x86_64.img (No such file or directory)

I guess the fact that I’m seeing

/initramfs-5.10-x86_64.img (No such file or directory)

means I have to do a manual rebuild mkintcpio -P
?

7

you have version 5.4
can you please try to boot on this version
( press Esc on boot , choose in advanced section version kernel )

if ok , then

sudo mhwd-kernel -r linux59
sudo mkinitcpio -P

reboot and test 510 , 511 , 5.12

8

I see there is the Problem:

By default the presets are set to the path /boot, but your entries point to path /boot/Manjaro. So change the path at your entries and run bootctl update or the presets at /etc/mkinitcpio.d/ and run again mkinitcpio -P.

9

Thanks for your responses.

@stephane , I tried to boot into 5.4 was not able to do so.

@Megavolt, I did as you suggested, changed the path at my entries, ran bootctl update and then mkintcpio -P. After mkinitcpio had finished, I got:

==> ERROR: specified kernel image does not exist: /boot/vmlinuz-5.9-x86_64' ==> Building image from preset: /etc/mkinitcpio.d/linux59.preset: 'fallback' -> -k /boot/vmlinuz-5.9-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.9-x86_64-fallback.img -S autodetect ==> ERROR: specified kernel image does not exist: /boot/vmlinuz-5.9-x86_64’

…and I’m still unable to boot into anything other than 5.9

10

Well, you moved everything to /boot/Manjaro and didn’t change the preset /etc/mkinitcpio.d/linux59.preset ?

11

That means that the files are not in /boot, but at /boot/Manjaro:

12

Thanks all for your help. I’m not sure how I ended up with /boot/Manjaro for the 510 and 511 kernels and /boot for the 59 kernel??

I changed the preset (/etc/mkinitcpio.d/linux5xx.preset) for 510 and 511 to point to /boot/Manjaro then I did bootctl update, then I ran mkinitcpio -P.

I’m now booted into 510.

Thanks again!

13