file /boot/vmlinuz not found after update | I did update-grub | black screen

I performed pacman updates in a laptop . After restart, a black screen appears with the following message:

file /boot/vmlinuz-5.1-x86_64 not found
press any key to continue

pressing any key leads to the grub menu. I select Manjaro (only option) and the above message is displayed again.

So I booted from manjaro live USB and did:

manjaro-chroot -a
update-grub
exit
sudo reboot

I can now see a black screen with no message.
I would appreciate if you could help me
Many thanks.

Try this in a chroot:

mkinitcpio -P
update-grub

Before doing that check in chroot status of kernels:

mhwd-kernel -l

Depending on result I would recommend to install some kernels in addition, e.g. 5.4:

sudo mhwd-kernel -i linux54

@Wollie @drunkenmonkey Thank you for your input.

[manjaro@manjaro-gnome ~]$ manjaro-chroot  -a
==> Mounting (ManjaroLinux) [/dev/nvme0n1p2]
 --> mount: [/mnt]
 --> mount: [/mnt/boot/efi]
[manjaro-gnome /]# mhwd-kernel  -l
available kernels:
   * linux316
   * linux414
   * linux419
   * linux44
   * linux49
   * linux53
   * linux54
   * linux55
   * linux419-rt
   * linux54-rt

It seems I've got linux54 already.

mkinitcpio -P gives an error:

[manjaro-gnome /]# mkinitcpio -P 
==> ERROR: No presets found in /etc/mkinitcpio.d

mhwd-kernel -l - gives a list of available kernels
mhwd-kernel -li - gives a list of installed kernels

That's the problem, just do as Wollie said.

@Wollie @drunkenmonkey Thanks again.

It seems there is also linux54 installed:

[manjaro-gnome /]# mhwd-kernel  -li
Currently running: 5.2.11-1-MANJARO (linux52)
The following kernels are installed in your system:
   * linux54
   * linux54-rt

Nevertheless, I restarted and did:

[manjaro@manjaro-gnome ~]$ manjaro-chroot  -a
==> Mounting (ManjaroLinux) [/dev/nvme0n1p2]
 --> mount: [/mnt]
 --> mount: [/mnt/boot/efi]

[manjaro-gnome /]# mhwd-kernel  -li
Currently running: 5.2.11-1-MANJARO (linux52)
The following kernels are installed in your system:
   * linux54
   * linux54-rt

[manjaro-gnome /]# sudo mhwd-kernel -i linux54
:: Synchronizing package databases...
 core                  167.9 KiB   691 KiB/s 00:00 [######################] 100%
 extra                1970.7 KiB  3.68 MiB/s 00:01 [######################] 100%
 community               5.8 MiB  1257 KiB/s 00:05 [######################] 100%
 multilib              192.5 KiB   573 KiB/s 00:00 [######################] 100%
error: no targets specified (use -h for help)

update-grub and reboot yield the black screen (no grub menu)

Is there a reason you have installed the 5.4 realtime kernel? If not, I would remove it from within the chroot:

sudo mhwd-kernel -r linux54-rt

Afterwards, try to update again (still in chroot):

pacman-mirrors -f 5
pacman -Syyu

Then exit chroot and reboot.

@Wollie Thanks for your comment.

No, there is no particular reason...

Ok. I get this error:

[manjaro@manjaro-gnome ~]$ manjaro-chroot  -a
==> Mounting (ManjaroLinux) [/dev/nvme0n1p2]
 --> mount: [/mnt]
 --> mount: [/mnt/boot/efi]
[manjaro-gnome /]# sudo mhwd-kernel -r linux54-rt
checking dependencies...
error: failed to prepare transaction (could not satisfy dependencies)
:: removing linux54-rt breaks dependency 'linux54-rt' required by linux-rt-manjaro

[manjaro-gnome /]# mhwd-kernel  -li
Currently running: 5.2.11-1-MANJARO (linux52)
The following kernels are installed in your system:
   * linux54
   * linux54-rt

can you add in chroot

mhwd-kernel  -i linux419 
mhwd-kernel  -i linux414
exit

if all ok reboot or return error

@stephane Ok.

[manjaro-gnome ~]# mhwd-kernel  -i linux419
:: Synchronizing package databases...
 core                  167.9 KiB   360 KiB/s 00:00 [######################] 100%
 extra                1970.7 KiB  2.38 MiB/s 00:01 [######################] 100%
 community               5.8 MiB   980 KiB/s 00:06 [######################] 100%
 multilib              192.5 KiB   848 KiB/s 00:00 [######################] 100%
error: no targets specified (use -h for help)

[manjaro-gnome ~]# mhwd-kernel  -i linux414
:: Synchronizing package databases...
 core                  167.9 KiB   365 KiB/s 00:00 [######################] 100%
 extra                1970.7 KiB  2.95 MiB/s 00:01 [######################] 100%
 community               5.8 MiB  1826 KiB/s 00:03 [######################] 100%
 multilib              192.5 KiB  31.3 MiB/s 00:00 [######################] 100%
error: no targets specified (use -h for help)

[manjaro-gnome ~]# exit
exit
 --> umount: [/mnt/boot/efi]
 --> umount: [/mnt]

I reboot, and see the black screen again...

I access the chroot again and I cannot see the 414 or 419 installed:

[manjaro-gnome /]# mhwd-kernel  -li
Currently running: 5.2.11-1-MANJARO (linux52)
The following kernels are installed in your system:
   * linux54
   * linux54-rt

you reboot on Grub ( F12 or F8 or Esc )
you go to details options and you change kernels to boot

(please see update: mhwd-kernel -li does not yield 414 or 419 unfortunately)

Some live kernels seem to have difficulties with mhwd-kernel. I would think it's worth trying to install via pacman (within chroot):

pacman -S linux54 linux54-headers
mkinitcpio -P
exit

Grub menu does not even appear, just a black screen

Please check this


Several vital hooks has errors - including grub and mkinitcpio

@philm @oberon @Ste74


Please run this command - and post the output

grep -iRl 'Type = Path' /usr/share/libalpm/hooks

@Wollie

So:

[manjaro@manjaro-gnome ~]$ manjaro-chroot  -a
==> Mounting (ManjaroLinux) [/dev/nvme0n1p2]
 --> mount: [/mnt]
 --> mount: [/mnt/boot/efi]
[manjaro-gnome /]# pacman -S linux54 linux54-headers
warning: linux54-5.4.14-2 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...

Packages (2) linux54-5.4.14-2  linux54-headers-5.4.14-2

Total Download Size:     9.65 MiB
Total Installed Size:  186.86 MiB
Net Upgrade Size:       47.33 MiB

:: Proceed with installation? [Y/n] y
:: Retrieving packages...
 linux54-headers-...     9.7 MiB  1360 KiB/s 00:07 [######################] 100%
(2/2) checking keys in keyring                     [######################] 100%
(2/2) checking package integrity                   [######################] 100%
(2/2) loading package files                        [######################] 100%
(2/2) checking for file conflicts                  [######################] 100%
(2/2) checking available disk space                [######################] 100%
:: Running pre-transaction hooks...
(1/1) Save Linux kernel modules
:: Processing package changes...
(1/2) reinstalling linux54                         [######################] 100%
(2/2) installing linux54-headers                   [######################] 100%
:: Running post-transaction hooks...
(1/5) Arming ConditionNeedsUpdate...
(2/5) Updating module dependencies...
(3/5) Updating linux initcpios...
==> Building image from preset: /etc/mkinitcpio.d/linux54.preset: 'default'
  -> -k /boot/vmlinuz-5.4-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.4-x86_64.img
==> Starting build: 5.4.14-2-MANJARO
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [resume]
  -> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-5.4-x86_64.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux54.preset: 'fallback'
  -> -k /boot/vmlinuz-5.4-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.4-x86_64-fallback.img -S autodetect
==> Starting build: 5.4.14-2-MANJARO
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [resume]
  -> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-5.4-x86_64-fallback.img
==> Image generation successful
(4/5) Updating Grub-Bootmenu
Generating grub configuration file ...
Found theme: /usr/share/grub/themes/manjaro/theme.txt
Found linux image: /boot/vmlinuz-5.4-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-5.4-x86_64.img
Found initrd fallback image: /boot/initramfs-5.4-x86_64-fallback.img
Found linux image: /boot/vmlinuz-5.4-rt-x86_64
Found initrd image: /boot/intel-ucode.img
grub-probe: error: cannot find a GRUB drive for /dev/sda1.  Check your device.map.
grub-probe: error: cannot find a GRUB drive for /dev/sda1.  Check your device.map.
Found memtest86+ image: /boot/memtest86+/memtest.bin
/usr/bin/grub-probe: warning: unknown device type nvme0n1.
done
(5/5) Restore Linux kernel modules

==> Warning:
	 -> This computer hasn't been restarted for a while.
	 -> You are running an old kernel. In order to use a
	 -> new version of the kernel, please restart your
	 -> computer as soon as possible.
[manjaro-gnome /]# mhwd-kernel  -li
Currently running: 5.2.11-1-MANJARO (linux52)
The following kernels are installed in your system:
   * linux54
   * linux54-rt

Please note that before this last installation through pacman, mhwd-kernel -li also yielded linux54... As I can see from warning: linux54-5.4.14-2 is up to date -- reinstalling, this has been a reinstallation of the kernel

[manjaro-gnome /]# mkinitcpio -P
==> Building image from preset: /etc/mkinitcpio.d/linux54.preset: 'default'
  -> -k /boot/vmlinuz-5.4-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.4-x86_64.img
==> Starting build: 5.4.14-2-MANJARO
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [resume]
  -> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-5.4-x86_64.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux54.preset: 'fallback'
  -> -k /boot/vmlinuz-5.4-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.4-x86_64-fallback.img -S autodetect
==> Starting build: 5.4.14-2-MANJARO
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [resume]
  -> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-5.4-x86_64-fallback.img
==> Image generation successful
[manjaro-gnome /]# mhwd-kernel  -li
Currently running: 5.2.11-1-MANJARO (linux52)
The following kernels are installed in your system:
   * linux54
   * linux54-rt
[manjaro-gnome /]# exit
exit
 --> umount: [/mnt/boot/efi]
 --> umount: [/mnt]

I now reboot and can go to my local manjaro installation.

Now, I cannot see the Grub every time I reboot... but only by pressing Esc just after the optional BIOS entry and just before the Manjaro login.
before, though, the grub menu just prompted - should it be prompted as a default behaviour ?
Many thanks

@linux-aarhus Many thanks for your input and for the link.

david@david-pc ~]$ grep -iRl 'Type = Path' /usr/share/libalpm/hooks/
/usr/share/libalpm/hooks/xorg-mkfontscale.hook
/usr/share/libalpm/hooks/30-systemd-udev-reload.hook
/usr/share/libalpm/hooks/60-mkinitcpio-remove.hook
/usr/share/libalpm/hooks/99-grub.hook
/usr/share/libalpm/hooks/30-systemd-hwdb.hook
/usr/share/libalpm/hooks/30-systemd-binfmt.hook
/usr/share/libalpm/hooks/30-systemd-daemon-reload.hook
/usr/share/libalpm/hooks/30-systemd-catalog.hook
/usr/share/libalpm/hooks/20-systemd-sysusers.hook
/usr/share/libalpm/hooks/30-systemd-sysctl.hook
/usr/share/libalpm/hooks/30-systemd-update.hook
/usr/share/libalpm/hooks/90-mkinitcpio-install.hook
/usr/share/libalpm/hooks/30-systemd-tmpfiles.hook
/usr/share/libalpm/hooks/update-mime-database.hook

For future seekers - read the following topic

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.

Forum kindly sponsored by