GRUB Not Loading After Reset During Update

[YugiBearx]

Hello,
After interrupting an update by resetting my system, GRUB stopped loading. Upon boot, I receive the following error message:

ERROR: /boot/vmlinuz-6.6-x86_64 not found. You need to load the kernel first.

Now, GRUB only shows the UEFI Firmware Settings and Memory Test options. I’ve run update-grub to regenerate the GRUB configuration, but it hasn’t resolved the issue. Additionally, I’ve tried reinstalling GRUB, but os-prober is not detecting my Manjaro or Windows 11 partitions (I’m dual-booting), even though lsblk shows them.

I’ve run the following commands to reinstall GRUB:

sudo pacman -S grub efibootmgr os-prober
sudo grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=Manjaro --recheck
sudo grub-mkconfig -o /boot/grub/grub.cfg

Any help would be appreciated. Thank you!

[Aragorn]

[HowTo] Recovering from an interrupted update/upgrade

Difficulty: ★★☆☆☆ So you couldn’t wait until the update process had completed and you went for the reset/power button, didn’t you? And now you’re getting the message that you don’t have a kernel installed. Well, you’re not the only one — we’re seeing it happen all the time. So, here’s how to fix it, you impatient n00b. If you don’t happen to have a recent Manjaro installer USB/DVD/CD handy, direct your browser to this wonderful page, download t…

[YugiBearx]

This is what I followed to recover from an interrupted update, but now the problem is that GRUB no longer lists my operating systems. When I run update-grub, it shows the following output:

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
/usr/bin/grub-probe: warning: unknown device type nvme0n1.
Found memtest86+ EFI image: /boot/memtest86+/memtest.efi
/usr/bin/grub-probe: warning: unknown device type nvme0n1.

Despite running update-grub, my OSes (Manjaro and Windows) still do not appear in GRUB.

[Aragorn]

Are you sure your kernels have been installed and the initramfs have been recreated?

What is the output of…

ls -l /boot

…?

On account of Windows, if it isn’t found, then chances are that it was installed in legacy BIOS mode, rather than in UEFI mode. You cannot mix the two on a single drive — either they must both boot in native UEFI mode or both in legacy BIOS mode.

[YugiBearx]

Here is the output of ls -l /boot:

total 9480
drwxr-xr-x 4 root root    4096 Dec 31  1969 efi
drwxr-xr-x 6 root root    4096 May  5 13:21 grub
-rw-r--r-- 1 root root 9683968 Feb 11 13:09 intel-ucode.img
-rw-r--r-- 1 root root      22 Apr 10 15:19 linux54-x86_64.kver
-rw-r--r-- 1 root root      21 Apr 26 01:36 linux66-x86_64.kver
drwxr-xr-x 2 root root    4096 Feb  4 10:46 memtest86+

[Aragorn]

@YugiBearx

total 9480
drwxr-xr-x 4 root root    4096 Dec 31  1969 efi
drwxr-xr-x 6 root root    4096 May  5 13:21 grub
-rw-r--r-- 1 root root 9683968 Feb 11 13:09 intel-ucode.img
-rw-r--r-- 1 root root      22 Apr 10 15:19 linux54-x86_64.kver
-rw-r--r-- 1 root root      21 Apr 26 01:36 linux66-x86_64.kver
drwxr-xr-x 2 root root    4096 Feb  4 10:46 memtest86+

Just as I suspected already.

-rw-r--r-- 1 root root      22 Apr 10 15:19 linux54-x86_64.kver
-rw-r--r-- 1 root root      21 Apr 26 01:36 linux66-x86_64.kver

Delete these two files and reinstall the kernels from within the chroot…

pacman -S linux54 linux66
mkinitcpio -P && update-grub

[YugiBearx]

How would I delete these two files?

[Aragorn]

rm -f /boot/linux54-x86_64.kver /bootlinux66-x86_64.kver

The existence of those two files prevents pacman from installing the kernels.

[YugiBearx]

I will try booting into GRUB and see how it goes.

[YugiBearx]

Thanks for helping, will try being a little patient next time there’s an update