The output of mhwd-kernel -li gives
Currently running: 6.5.5-1-MANJARO (linux65)
The following kernels are installed in your system:
* linux510
* linux515
* linux61
From what I understand I was using the linux61 kernel beforehand and it lists it as being installed. However the interrupted update somehow messed with this and I need to reinstall it?
I ran mhwd-kernel -i linux61. The output is as follows:
:: Synchronizing package databases...
core 145.2 KiB 60.2 KiB/s 00:02 [#######################################] 100%
extra 8.6 MiB 1340 KiB/s 00:07 [#######################################] 100%
community 29.0 B 119 B/s 00:00 [#######################################] 100%
multilib 145.3 KiB 137 KiB/s 00:01 [#######################################] 100%
error: no targets specified (use -h for help)
Wait with the reallocation, but you can do it in live env after we know everything is working and you have tried booting.
I think one of those is the usb kernel, If this is yours:
And not cfinnberg:s then 6.5 and 6.1
Otherwise you have to look in /boot to be sure, then install all.
Itās better to reinstall all and then remove because otherwise there will be unwanted leftovers.
Clarification, ONLY the kernels you have in /boot
Iām a little confused. What you are suggesting I do? I know that I installed the linux510, linux515, and linux61 kernels at some point. I think the linux65 kernel is from the live USB.
That is why I asked if that was his or your output.
ls /boot
ls /boot
efi grub intel-ucode.img linux510-x86_64.kver linux515-x86_64.kver linux61-x86_64.kver memtest86+
There you go, your memory was correct. install 5.10, 5,15 & 6.10
I get error: no targets specified (use -h for help) when running mhwd-kernel -i linux61
Try installing grub first. ie jump to next step then try the kernels
grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=manjaro --recheck
Installing for x86_64-efi platform.
Installation finished. No error reported.
grub-mkconfig -o /boot/grub/grub.cfg
Generating grub configuration file ...
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.
ERROR: mkdir /var/lock/dmraid
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.
Adding boot menu entry for UEFI Firmware Settings ...
Root filesystem isn't btrfs
If you think an error has occurred, please file a bug report at "https://github.com/Antynea/grub-btrfs"
Found memtest86+ image: /boot/memtest86+/memtest.bin
/usr/bin/grub-probe: warning: unknown device type nvme0n1.
done
mhwd-kernel -i linux61
:: Synchronizing package databases...
core 145.2 KiB 56.8 KiB/s 00:03 [#######################################] 100%
extra 8.6 MiB 1890 KiB/s 00:05 [#######################################] 100%
community 29.0 B 122 B/s 00:00 [#######################################] 100%
multilib 145.3 KiB 335 KiB/s 00:00 [#######################################] 100%
error: no targets specified (use -h for help)
Ok, even though that looks confusing, I think we are good.
Tells us the kernels are allready installed, so lets not touch them before updating the system instead.
you can check /boot/efi if you are curious.
Now cross your fingers and run pacman-mirrors -f && pacman -Syu
This was a big mistake as this means you followed a guide for EndeavourOS! How could you believe this would work? 
The EndeavorOS article was linked in this Arch forum as a solution for one particular user (post #11 I think).
Yes, but Manjaro is not Arch and not EndeavourOS!
If you read the advice carefully you should have seen that there is an EndeavourOS specific syntax involved.
Especially the boot process is something very individual arranged for each Linux OS. You should never mix.
I guess that is where my ignorance got me into this mess.
Wait, hold on, I typed to fast before, your kernels does NOT get detected by grubā¦
We probably need to install them, but you could try to run update-grub one more time.
Otherwise try to update, mhwd will complain otherwise, this is a bit touch and go for me now.
If the update goes through, and mhwd still complains, we can then use pacman to install the kernels.
Donāt worry, just learn the lesson.
You are missing the kernel files. Again as an example, this is the content of my /boot/ directory:
-rw-r--r-- 1 root root 81920 29.10. 16:04 amd-ucode.img
drwxr-xr-x 6 root root 4096 7.11. 22:23 grub/
-rwxr-xr-x 1 root root 79210257 7.10. 10:46 initramfs-6.1-x86_64-fallback.img*
-rwxr-xr-x 1 root root 41201213 7.10. 10:45 initramfs-6.1-x86_64.img*
-rwxr-xr-x 1 root root 84849328 7.10. 10:47 initramfs-6.5-x86_64-fallback.img*
-rwxr-xr-x 1 root root 42121264 7.10. 10:46 initramfs-6.5-x86_64.img*
-rwxr-xr-x 1 root root 42121264 7.10. 11:33 initramfs-linux.img*
-rw-r--r-- 1 root root 21 25.10. 13:46 linux61-x86_64.kver
-rw-r--r-- 1 root root 20 25.10. 13:44 linux65-x86_64.kver
-rw-r--r-- 1 root root 20 30.10. 07:00 linux66-x86_64.kver
-rwxr-xr-x 1 root root 11515808 7.10. 10:44 vmlinuz-6.1-x86_64*
-rwxr-xr-x 1 root root 12828320 7.10. 10:44 vmlinuz-6.5-x86_64*
-rwxr-xr-x 1 root root 12828320 7.10. 11:33 vmlinuz-linux*
I think that mhwd-kernel does not have a āforceā option to reinstall the kernels, so youāll have to uninstall and install them again. Or youāll have to install them with pacman.
After installing the kernels, run update-grub again.
I think mhwd-kernel will ask if it should ignore the system not updated or not, but itās never a good thing, if an update can be done first, isnāt that better you think?
We can then use pacman to install kernels if mhwd still refuses.