Arch Linux

heidegger

Member

Registered: 2013-04-24

Posts: 100

[SOLVED] DKMS Error During Pacman Update - Virtualbox-host-dkms, LTS

I received an error during my weekly pacman update.
I have not yet attempted to reboot.
I've never seen this one before, and I'm not sure if it's safe to reboot or if I need to try and fix this now as the kernel may be unbootable.
The LTS kernel was updated as was virtualbox-host-dkms, among many other packages.
The error is indicating that several zst files "exactly matches what is already found in kernel 6.6.12-1-lts."

Here's a sample output attempting to reinstall virtualbox-host-dkms after the update:
(This output appears identical without the additional info related to the other packages.)

[kafka@kafka ~]$ sudo pacman -S virtualbox-host-dkms
warning: virtualbox-host-dkms-7.0.14-2 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...

Packages (1) virtualbox-host-dkms-7.0.14-2

Total Installed Size:  11.07 MiB
Net Upgrade Size:       0.00 MiB

:: Proceed with installation? [Y/n] y
(1/1) checking keys in keyring                                                                                        [#######################################################################] 100%
(1/1) checking package integrity                                                                                      [#######################################################################] 100%
(1/1) loading package files                                                                                           [#######################################################################] 100%
(1/1) checking for file conflicts                                                                                     [#######################################################################] 100%
(1/1) checking available disk space                                                                                   [#######################################################################] 100%
:: Running pre-transaction hooks...
(1/1) Remove upgraded DKMS modules
==> dkms remove --no-depmod vboxhost/7.0.14_OSE -k 6.6.12-1-lts
==> dkms remove --no-depmod vboxhost/7.0.14_OSE -k 6.6.14-1-lts
==> dkms remove --no-depmod vboxhost/7.0.14_OSE -k 6.7.1-arch1-1
==> dkms remove vboxhost/7.0.14_OSE
:: Processing package changes...
(1/1) reinstalling virtualbox-host-dkms                                                                               [#######################################################################] 100%
ldconfig: file /usr/lib32/libLLVM.so is truncated

ldconfig: file /usr/lib32/libLLVM-16.so is truncated

ldconfig: file /usr/lib32/libLLVM-16.0.6.so is truncated

ldconfig: File /usr/lib/libzita-resampler.so.1.11.2 is empty, not checked.
ldconfig: File /usr/lib/libzita-resampler.so is empty, not checked.
ldconfig: File /usr/lib/libzita-resampler.so.1 is empty, not checked.
:: Running post-transaction hooks...
(1/3) Arming ConditionNeedsUpdate...
(2/3) Install DKMS modules
==> dkms install --no-depmod vboxhost/7.0.14_OSE -k 6.6.14-1-lts
==> dkms install --no-depmod vboxhost/7.0.14_OSE -k 6.6.12-1-lts
Module version 7.0.14 for vboxdrv.ko.zst
exactly matches what is already found in kernel 6.6.12-1-lts.
DKMS will not replace this module.
You may override by specifying --force.
Module version 7.0.14 for vboxnetflt.ko.zst
exactly matches what is already found in kernel 6.6.12-1-lts.
DKMS will not replace this module.
You may override by specifying --force.
Module version 7.0.14 for vboxnetadp.ko.zst
exactly matches what is already found in kernel 6.6.12-1-lts.
DKMS will not replace this module.
You may override by specifying --force.
Error! Installation aborted.
==> WARNING: `dkms install --no-depmod vboxhost/7.0.14_OSE -k 6.6.12-1-lts' exited 6
==> dkms install --no-depmod vboxhost/7.0.14_OSE -k 6.7.1-arch1-1
==> depmod 6.6.14-1-lts
==> depmod 6.7.1-arch1-1
(3/3) Updating linux initcpios...
==> Building image from preset: /etc/mkinitcpio.d/linux-lts.preset: 'default'
==> Using default configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-linux-lts -g /boot/initramfs-linux-lts.img --microcode /boot/intel-ucode.img
==> Starting build: '6.6.14-1-lts'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [kms]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
  -> Running build hook: [block]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-linux-lts.img'
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux-lts.preset: 'fallback'
==> Using default configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-linux-lts -g /boot/initramfs-linux-lts-fallback.img -S autodetect --microcode /boot/intel-ucode.img
==> Starting build: '6.6.14-1-lts'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [kms]
==> WARNING: Possibly missing firmware for module: 'ast'
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: 'qed'
==> WARNING: Possibly missing firmware for module: 'bfa'
==> WARNING: Possibly missing firmware for module: 'qla2xxx'
==> WARNING: Possibly missing firmware for module: 'qla1280'
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-linux-lts-fallback.img'
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
==> Using default configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-linux -g /boot/initramfs-linux.img --microcode /boot/intel-ucode.img
==> Starting build: '6.7.1-arch1-1'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [kms]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
  -> Running build hook: [block]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-linux.img'
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
==> Using default configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-linux -g /boot/initramfs-linux-fallback.img -S autodetect --microcode /boot/intel-ucode.img
==> Starting build: '6.7.1-arch1-1'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [kms]
==> WARNING: Possibly missing firmware for module: 'ast'
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: 'qed'
==> WARNING: Possibly missing firmware for module: 'bfa'
==> WARNING: Possibly missing firmware for module: 'qla2xxx'
==> WARNING: Possibly missing firmware for module: 'qla1280'
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-linux-fallback.img'
==> Image generation successful

Thank you,

And on a side note, if you can share how to correct those ldconfig notifications I would be very appreciative.

Last edited by heidegger (2024-01-27 20:41:26)

Scimmia

Fellow

Registered: 2012-09-01

Posts: 13,725

Re: [SOLVED] DKMS Error During Pacman Update - Virtualbox-host-dkms, LTS

You have filesystem problems. There's a left over dir in /usr/lib/modules/ for an old kernel that no longer exists; it was supposed to be removed on update, but for some reason it wasn't. It's likely related to those other errors about truncated and empty libraries, it means that things weren't correctly written to disk, usually from a power failure or something, but could be hardware issues, etc.

I don't see anything that would indicate a problem with booting up, but I would suggest reinstalling all packages that were part of the previous update that failed. Or just reinstall all packages, command for that is in the wiki, pacman tips and tricks, IIRC. You'll also want to delete that old dir for the old kernel.

Last edited by Scimmia (2024-01-27 16:26:10)

heidegger

Member

Registered: 2013-04-24

Posts: 100

Re: [SOLVED] DKMS Error During Pacman Update - Virtualbox-host-dkms, LTS

Thank you Scimmia.

Yes, the ldconfig errors started from a hardware failure during an update.
That was quite a while back, but these ldconfig errors persisted.
I may have reinstalled all packages back when the drive was replaced to get back up and running, but I don't believe the removal process was re-ran and left these files.
Since replacing the drive several months back, everything appeared to be going smooth, aside from the ldconfig notes.
Should I consider tracking down orphaned files and removing them manually?

Edit: I will re-install all packages again for certainty.

Last edited by heidegger (2024-01-27 16:42:55)

Scimmia

Fellow

Registered: 2012-09-01

Posts: 13,725

Re: [SOLVED] DKMS Error During Pacman Update - Virtualbox-host-dkms, LTS

OK, if those aren't related, are you using something like kernel-modules-hook that keeps the modules around after you update the kernel? That would explain the old dir being there as well, it requires a separate cleanup service.

As for the possibility of old files around, yes, I would be running lostfiles to see what's where.

heidegger

Member

Registered: 2013-04-24

Posts: 100

Re: [SOLVED] DKMS Error During Pacman Update - Virtualbox-host-dkms, LTS

I do have kernel-modules-hook installed and the cleanup service is enabled.
There may have been a period where it was installed without the cleanup service, but not recently.
Edit: cleanup was enabled when kernel-modules-hook was installed.

Last edited by heidegger (2024-01-27 17:26:25)

Scimmia

Fellow

Registered: 2012-09-01

Posts: 13,725

Re: [SOLVED] DKMS Error During Pacman Update - Virtualbox-host-dkms, LTS

Thinking about it, that hook would probably mean that dkms will always try to build for the kernel you're running, since that dir is still there, so this is probably normal in this case?

heidegger

Member

Registered: 2013-04-24

Posts: 100

Re: [SOLVED] DKMS Error During Pacman Update - Virtualbox-host-dkms, LTS

Interesting.
I know that when updating the kernel and using the AUR nVidia DKMS package, it is necessary to reboot to the new kernel before updating the DKMS package.
So in this situation, I should reboot, then reinstall the the virtualbox-host-dkms package manually for it to be applied to the new kernel.
I haven't come across a situation like this from the mainline repositories myself, only with AUR packages.

Also, thanks for pointing me to lostfiles!

Last edited by heidegger (2024-01-27 17:37:19)

heidegger

Member

Registered: 2013-04-24

Posts: 100

Re: [SOLVED] DKMS Error During Pacman Update - Virtualbox-host-dkms, LTS

After restarting and loading the new kernel, I reinstalled the virtualbox-host-dkms package manually and everything is working correctly.
Since the new kernel was loaded, there were no errors during the installation.

It seems pretty obvious now but the errors during DKMS install threw up some big red flags.