Manjaro is failing to update due to a missing file or folder

[anon88624618]

If you’re currently booted with 5.10 kernel I would not recommend deleting any files belonging to linux510 but boot into a different kernel first (if you’ve got one installed, that is).

[DAC324]

Indeed, that might be the reason why he cannot overwrite these files - but some doubts remain. Usually, I also install any updates received for the currently running kernel, without having such problems.
It would be interesting to know what happened after

sudo rm /boot/linux510-x86_64.kver
sudo rm /usr/lib/modules/extramodules-5.10-MANJARO/version

In case of these two files, no impact on the system is expected when deleting them as these are simple text files containing the current kernel version only:
cat /usr/lib/modules/extramodules-5.10-MANJARO/version

5.10.23-1-MANJARO

cat /boot/linux510-x86_64.kver

5.10.23-1-MANJARO x64

So, just remove them and check with

ls -la /boot/linux510-x86_64.kver
ls -la /usr/lib/modules/extramodules-5.10-MANJARO/version

if the files are still there.

[gnoblin_44]

Sup fellas, the update went well from there but there is only one problem:

==> Starting build: 5.9.16-1-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]
==> ERROR: module not found: `usbhid'
  -> Running build hook: [keymap]
loadkeys: Unable to open file: au: No such file or directory
  -> Running build hook: [resume]
  -> Running build hook: [filesystems]
==> WARNING: No modules were added to the image. This is probably not what you want.
==> Creating gzip-compressed initcpio image: /boot/initramfs-5.9-x86_64.img
==> WARNING: errors were encountered during the build. The image may not be complete.
==> 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
==> Starting build: 5.9.16-1-MANJARO
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [keyboard]
==> ERROR: module not found: `usbhid'
  -> Running build hook: [keymap]
loadkeys: Unable to open file: au: No such file or directory
  -> Running build hook: [resume]
  -> Running build hook: [filesystems]
==> WARNING: No modules were added to the image. This is probably not what you want.
==> Creating gzip-compressed initcpio image: /boot/initramfs-5.9-x86_64-fallback.img
==> WARNING: errors were encountered during the build. The image may not be complete.
error: command failed to execute correctly

Will I have to make a file for kernel 5.9 aswell?
Also, I have been using kernel 5.4 since the beginning of this post

[anon88624618]

Linux59 is marked EOL (End Of Life), so I would just remove it…

[gnoblin_44]

Why was it given EOL? And how do I remove it?

[anon88624618]

Please read this:
https://wiki.manjaro.org/index.php/Manjaro_Kernels
https://www.kernel.org/category/faq.html

[gnoblin_44]

It says that the virtual box host modules are required for virtual box when I try to delete kernel 5.9

[omano]

Remove virtualbox to simplify things for now, do your stuff, then reinstall virtualbox.

[anon88624618]

If you’re not running Manjaro in a virtual machine, you should be able to manage your kernels via mhwd (mhwd-kernel) and/or its GUI in Manjaro’s settings.