You are not logged in.

Pages: 1

#1 2018-04-06 16:14:03

DonTrash
Member
Registered: 2018-04-06
Posts: 9

[SOLVED] Failed to start Load Kernel Modules after upgrade

Hey everyone
after upgrading my system (sudo pacman -Syu) I got a "Failed to start Load Kernel Modules" while booting.
I fixed this by using following command with live Arch on usb: pacman -U /var/cache/pacman/pkg/linux-4.15.14-1-x86_64.pkg.tar.xz

output of systemctl status systemd-modules-load.service: 

* systemd-modules-load.service - Load Kernel Modules
   Loaded: loaded (/usr/lib/systemd/system/systemd-modules-load.service; static; vendor preset: disabled)
   Active: failed (Result: exit-code) since Fri 2018-04-06 17:38:43 CEST; 12min ago
     Docs: man:systemd-modules-load.service(8)
           man:modules-load.d(5)
  Process: 283 ExecStart=/usr/lib/systemd/systemd-modules-load (code=exited, status=1/FAILURE)
 Main PID: 283 (code=exited, status=1/FAILURE)

Apr 06 17:38:43 ArchLinux systemd[1]: Starting Load Kernel Modules...
Apr 06 17:38:43 ArchLinux systemd-modules-load[283]: Failed to find module 'vboxguest'
Apr 06 17:38:43 ArchLinux systemd-modules-load[283]: Failed to find module 'vboxsf'
Apr 06 17:38:43 ArchLinux systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1/FAILURE
Apr 06 17:38:43 ArchLinux systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'.
Apr 06 17:38:43 ArchLinux systemd[1]: Failed to start Load Kernel Modules.

output of journalctl -u systemd-modules-load.service

-- Reboot --
Apr 06 17:38:43 ArchLinux systemd-modules-load[202]: Inserted module 'crypto_user'
Apr 06 17:38:43 ArchLinux systemd-modules-load[202]: Failed to find module 'vboxguest'
Apr 06 17:38:43 ArchLinux systemd-modules-load[202]: Failed to find module 'vboxsf'
Apr 06 17:38:43 ArchLinux systemd-modules-load[202]: Inserted module 'vboxvideo'
Apr 06 17:38:43 ArchLinux systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1/FAILURE
Apr 06 17:38:43 ArchLinux systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'.
Apr 06 17:38:43 ArchLinux systemd[1]: Failed to start Load Kernel Modules.
Apr 06 17:38:43 ArchLinux systemd[1]: Starting Load Kernel Modules...
Apr 06 17:38:43 ArchLinux systemd-modules-load[283]: Failed to find module 'vboxguest'
Apr 06 17:38:43 ArchLinux systemd-modules-load[283]: Failed to find module 'vboxsf'
Apr 06 17:38:43 ArchLinux systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1/FAILURE
Apr 06 17:38:43 ArchLinux systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'.
Apr 06 17:38:43 ArchLinux systemd[1]: Failed to start Load Kernel Modules.

Is there anything I could do to upgrade and fix this problem?

Last edited by DonTrash (2018-04-06 17:42:01)

Offline

#2 2018-04-06 16:22:30

Scimmia
Fellow
Registered: 2012-09-01
Posts: 11,560

Re: [SOLVED] Failed to start Load Kernel Modules after upgrade

So you're running inside of VirtualBox? What kernel did you upgrade to and what virtualbox module package are you running?

Offline

#3 2018-04-06 16:37:24

DonTrash
Member
Registered: 2018-04-06
Posts: 9

Re: [SOLVED] Failed to start Load Kernel Modules after upgrade

no I'm not running Arch in VBox. Its single booted on my ThinkPad Yoga 460. As bootloader I'm using systemd.

thats the pacman.log file if that helps:

[2018-04-06 16:47] [PACMAN] Running 'pacman -Syu'
[2018-04-06 16:47] [PACMAN] synchronizing package lists
[2018-04-06 16:47] [PACMAN] starting full system upgrade
[2018-04-06 16:48] [ALPM] running '70-dkms-remove.hook'...
[2018-04-06 16:48] [ALPM-SCRIPTLET] ==> dkms remove vboxguest/5.2.8_OSE -k 4.15.14-1-ARCH
[2018-04-06 16:48] [ALPM] transaction started
[2018-04-06 16:48] [ALPM] upgraded alsa-plugins (1.1.5-1 -> 1.1.6-1)
[2018-04-06 16:48] [ALPM] upgraded archlinux-keyring (20180322-1 -> 20180404-1)
[2018-04-06 16:48] [ALPM-SCRIPTLET] ==> Appending keys from archlinux.gpg...
[2018-04-06 16:48] [ALPM-SCRIPTLET] ==> Locally signing trusted keys in keyring...
[2018-04-06 16:48] [ALPM-SCRIPTLET]   -> Locally signing key DDB867B92AA789C165EEFA799B729B06A680C281...
[2018-04-06 16:48] [ALPM-SCRIPTLET]   -> Locally signing key 684148BB25B49E986A4944C55184252D824B18E8...
[2018-04-06 16:48] [ALPM-SCRIPTLET]   -> Locally signing key 91FFE0700E80619CEB73235CA88E23E377514E00...
[2018-04-06 16:48] [ALPM-SCRIPTLET]   -> Locally signing key AB19265E5D7D20687D303246BA1DFB64FFF979E7...
[2018-04-06 16:48] [ALPM-SCRIPTLET]   -> Locally signing key 0E8B644079F599DFC1DDC3973348882F6AC6A4C2...
[2018-04-06 16:48] [ALPM-SCRIPTLET] ==> Importing owner trust values...
[2018-04-06 16:48] [ALPM-SCRIPTLET] ==> Disabling revoked keys in keyring...
[2018-04-06 16:48] [ALPM-SCRIPTLET]   -> Disabling key 7FA647CD89891DEDC060287BB9113D1ED21E1A55...
[2018-04-06 16:48] [ALPM-SCRIPTLET]   -> Disabling key D4DE5ABDE2A7287644EAC7E36D1A9E70E19DAA50...
[2018-04-06 16:48] [ALPM-SCRIPTLET]   -> Disabling key 40440DC037C05620984379A6761FAD69BA06C6A9...
[2018-04-06 16:48] [ALPM-SCRIPTLET]   -> Disabling key B1F2C889CB2CCB2ADA36D963097D629E437520BD...
[2018-04-06 16:48] [ALPM-SCRIPTLET]   -> Disabling key BC1FBE4D2826A0B51E47ED62E2539214C6C11350...
[2018-04-06 16:48] [ALPM-SCRIPTLET]   -> Disabling key 63F395DE2D6398BBE458F281F2DBB4931985A992...
[2018-04-06 16:48] [ALPM-SCRIPTLET]   -> Disabling key 8F76BEEA0289F9E1D3E229C05F946DED983D4366...
[2018-04-06 16:48] [ALPM-SCRIPTLET]   -> Disabling key 4FCF887689C41B09506BE8D5F3E1D5C5D30DB0AD...
[2018-04-06 16:48] [ALPM-SCRIPTLET]   -> Disabling key 81D7F8241DB38BC759C80FCE3A726C6170E80477...
[2018-04-06 16:48] [ALPM-SCRIPTLET]   -> Disabling key 5E7585ADFF106BFFBBA319DC654B877A0864983E...
[2018-04-06 16:48] [ALPM-SCRIPTLET]   -> Disabling key E7210A59715F6940CF9A4E36A001876699AD6E84...
[2018-04-06 16:48] [ALPM-SCRIPTLET]   -> Disabling key F5A361A3A13554B85E57DDDAAF7EF7873CFD4BB6...
[2018-04-06 16:48] [ALPM-SCRIPTLET]   -> Disabling key 8CF934E339CAD8ABF342E822E711306E3C4F88BC...
[2018-04-06 16:48] [ALPM-SCRIPTLET]   -> Disabling key 5696C003B0854206450C8E5BE613C09CB4440678...
[2018-04-06 16:48] [ALPM-SCRIPTLET]   -> Disabling key 9515D8A8EAB88E49BB65EDBCE6B456CAF15447D5...
[2018-04-06 16:48] [ALPM-SCRIPTLET]   -> Disabling key 4A8B17E20B88ACA61860009B5CED81B7C2E5C0D2...
[2018-04-06 16:48] [ALPM-SCRIPTLET]   -> Disabling key 0B20CA1931F5DA3A70D0F8D2EA6836E1AB441196...
[2018-04-06 16:48] [ALPM-SCRIPTLET]   -> Disabling key 34C5D94FE7E7913E86DC427E7FB1A3800C84C0A5...
[2018-04-06 16:48] [ALPM-SCRIPTLET]   -> Disabling key 39F880E50E49A4D11341E8F939E4F17F295AFBF4...
[2018-04-06 16:48] [ALPM-SCRIPTLET]   -> Disabling key 66BD74A036D522F51DD70A3C7F2A16726521E06D...
[2018-04-06 16:48] [ALPM-SCRIPTLET]   -> Disabling key DBE7D3DD8C81D58D0A13D0E76BC26A17B9B7018A...
[2018-04-06 16:48] [ALPM-SCRIPTLET]   -> Disabling key 07DFD3A0BC213FA12EDC217559B3122E2FA915EC...
[2018-04-06 16:48] [ALPM-SCRIPTLET]   -> Disabling key 44D4A033AC140143927397D47EFD567D4C7EA887...
[2018-04-06 16:48] [ALPM-SCRIPTLET]   -> Disabling key 27FFC4769E19F096D41D9265A04F9397CDFD6BB0...
[2018-04-06 16:48] [ALPM-SCRIPTLET]   -> Disabling key 8840BD07FC24CB7CE394A07CCF7037A4F27FB7DA...
[2018-04-06 16:48] [ALPM-SCRIPTLET] ==> Updating trust database...
[2018-04-06 16:48] [ALPM-SCRIPTLET] gpg: marginals needed: 3  completes needed: 1  trust model: pgp
[2018-04-06 16:48] [ALPM-SCRIPTLET] gpg: depth: 0  valid:   1  signed:   5  trust: 0-, 0q, 0n, 0m, 0f, 1u
[2018-04-06 16:48] [ALPM-SCRIPTLET] gpg: depth: 1  valid:   5  signed:  74  trust: 0-, 0q, 0n, 5m, 0f, 0u
[2018-04-06 16:48] [ALPM-SCRIPTLET] gpg: depth: 2  valid:  74  signed:   8  trust: 74-, 0q, 0n, 0m, 0f, 0u
[2018-04-06 16:48] [ALPM-SCRIPTLET] gpg: next trustdb check due at 2018-06-25
[2018-04-06 16:48] [ALPM] upgraded fuse-common (3.2.1-1 -> 3.2.2-2)
[2018-04-06 16:48] [ALPM] installed perl-timedate (2.30-4)
[2018-04-06 16:48] [ALPM] installed perl-mailtools (2.20-1)
[2018-04-06 16:48] [ALPM] upgraded git (2.16.3-1 -> 2.17.0-1)
[2018-04-06 16:48] [ALPM] upgraded glib2 (2.56.0+7+g66948ae23-1 -> 2.56.0+16+gecabc6e21-1)
[2018-04-06 16:48] [ALPM] upgraded libusb (1.0.21-2 -> 1.0.22-1)
[2018-04-06 16:48] [ALPM] upgraded iproute2 (4.15.0-1 -> 4.16.0-1)
[2018-04-06 16:48] [ALPM] upgraded libsecret (0.18.5+14+g9980655-1 -> 0.18.6-1)
[2018-04-06 16:48] [ALPM] upgraded mkinitcpio-busybox (1.28.2-1 -> 1.28.3-1)
[2018-04-06 16:48] [ALPM] upgraded linux (4.15.14-1 -> 4.15.15-1)
[2018-04-06 16:48] [ALPM] upgraded linux-headers (4.15.14-1 -> 4.15.15-1)
[2018-04-06 16:48] [ALPM] upgraded lsof (4.90-2 -> 4.91-1)
[2018-04-06 16:48] [ALPM] upgraded mesa (17.3.7-1 -> 18.0.0-2)
[2018-04-06 16:48] [ALPM] upgraded neon (0.30.2-2 -> 0.30.2-3)
[2018-04-06 16:48] [ALPM] upgraded noto-fonts (20171025-2 -> 20180322-1)
[2018-04-06 16:48] [ALPM] upgraded thunar (1.6.14-1 -> 1.6.15-1)
[2018-04-06 16:48] [ALPM] upgraded zstd (1.3.3-1 -> 1.3.4-1)
[2018-04-06 16:48] [ALPM] transaction completed
[2018-04-06 16:48] [ALPM] running '60-linux.hook'...
[2018-04-06 16:48] [ALPM] running '70-dkms-install.hook'...
[2018-04-06 16:48] [ALPM-SCRIPTLET] ==> dkms install vboxguest/5.2.8_OSE -k 4.15.15-1-ARCH
[2018-04-06 16:49] [ALPM] running '90-linux.hook'...
[2018-04-06 16:49] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
[2018-04-06 16:49] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
[2018-04-06 16:49] [ALPM-SCRIPTLET] ==> Starting build: 4.15.15-1-ARCH
[2018-04-06 16:49] [ALPM-SCRIPTLET]   -> Running build hook: [base]
[2018-04-06 16:49] [ALPM-SCRIPTLET]   -> Running build hook: [udev]
[2018-04-06 16:49] [ALPM-SCRIPTLET]   -> Running build hook: [autodetect]
[2018-04-06 16:49] [ALPM-SCRIPTLET]   -> Running build hook: [modconf]
[2018-04-06 16:49] [ALPM-SCRIPTLET]   -> Running build hook: [block]
[2018-04-06 16:49] [ALPM-SCRIPTLET]   -> Running build hook: [filesystems]
[2018-04-06 16:49] [ALPM-SCRIPTLET]   -> Running build hook: [keyboard]
[2018-04-06 16:49] [ALPM-SCRIPTLET]   -> Running build hook: [fsck]
[2018-04-06 16:49] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2018-04-06 16:49] [ALPM-SCRIPTLET] ==> Creating gzip-compressed initcpio image: /boot/initramfs-linux.img
[2018-04-06 16:49] [ALPM-SCRIPTLET] ==> Image generation successful
[2018-04-06 16:49] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
[2018-04-06 16:49] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
[2018-04-06 16:49] [ALPM-SCRIPTLET] ==> Starting build: 4.15.15-1-ARCH
[2018-04-06 16:49] [ALPM-SCRIPTLET]   -> Running build hook: [base]
[2018-04-06 16:49] [ALPM-SCRIPTLET]   -> Running build hook: [udev]
[2018-04-06 16:49] [ALPM-SCRIPTLET]   -> Running build hook: [modconf]
[2018-04-06 16:49] [ALPM-SCRIPTLET]   -> Running build hook: [block]
[2018-04-06 16:49] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: wd719x
[2018-04-06 16:49] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: aic94xx
[2018-04-06 16:49] [ALPM-SCRIPTLET]   -> Running build hook: [filesystems]
[2018-04-06 16:49] [ALPM-SCRIPTLET]   -> Running build hook: [keyboard]
[2018-04-06 16:49] [ALPM-SCRIPTLET]   -> Running build hook: [fsck]
[2018-04-06 16:49] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2018-04-06 16:49] [ALPM-SCRIPTLET] ==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-fallback.img
[2018-04-06 16:49] [ALPM-SCRIPTLET] ==> Image generation successful
[2018-04-06 16:49] [ALPM] running 'detect-old-perl-modules.hook'...
[2018-04-06 16:49] [ALPM] running 'fontconfig.hook'...
[2018-04-06 16:49] [ALPM] running 'gtk-update-icon-cache.hook'...
[2018-04-06 16:49] [ALPM] running 'systemd-daemon-reload.hook'...
[2018-04-06 16:49] [ALPM] running 'systemd-sysusers.hook'...
[2018-04-06 16:49] [ALPM] running 'systemd-udev-reload.hook'...
[2018-04-06 16:49] [ALPM] running 'systemd-update.hook'...
[2018-04-06 16:49] [ALPM] running 'update-desktop-database.hook'...
[2018-04-06 16:49] [ALPM] running 'xorg-mkfontdir.hook'...

Offline

#4 2018-04-06 16:41:52

loqs
Member
Registered: 2014-03-06
Posts: 17,372

Re: [SOLVED] Failed to start Load Kernel Modules after upgrade

If you are not running the system inside virtualbox why did you install virtualbox-guest-dkms?

Offline

#5 2018-04-06 16:42:57

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 19,791

Re: [SOLVED] Failed to start Load Kernel Modules after upgrade

Okay, but why do you think you need modules that are only appropriate if you are running as an guest under Virtualbox?
Why did you configure it in that way?

Edit: too slow

Last edited by ewaller (2018-04-06 16:43:27)

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

Offline

#6 2018-04-06 16:43:30

Scimmia
Fellow
Registered: 2012-09-01
Posts: 11,560

Re: [SOLVED] Failed to start Load Kernel Modules after upgrade

If you're not running in VirtualBox, why do you have the VirtualBox guest modules installed?

from your log:

dkms install vboxguest/5.2.8_OSE -k 4.15.15-1-ARCH

Edit: WAY too slow

Last edited by Scimmia (2018-04-06 16:44:06)

Offline

#7 2018-04-06 16:44:15

Slithery
Administrator
From: Norfolk, UK
Registered: 2013-12-01
Posts: 5,776

Re: [SOLVED] Failed to start Load Kernel Modules after upgrade

DonTrash wrote:

no I'm not running Arch in VBox.

Then why do you have the VirtualBox guest modules installed and configured in modules-load.d?

How did you install Arch?

Edit - WAY, WAAY too slow smile

Last edited by Slithery (2018-04-06 16:44:52)

No, it didn't "fix" anything. It just shifted the brokeness one space to the right. - jasonwryan
Closing -- for deletion; Banning -- for muppetry. - jasonwryan

aur - dotfiles

Offline

#8 2018-04-06 16:50:24

DonTrash
Member
Registered: 2018-04-06
Posts: 9

Re: [SOLVED] Failed to start Load Kernel Modules after upgrade

Oh yikes I Have no Idea how that happend...
I followed straight the Guide. Must happend after the Installation.

Offline

#9 2018-04-06 17:00:06

DonTrash
Member
Registered: 2018-04-06
Posts: 9

Re: [SOLVED] Failed to start Load Kernel Modules after upgrade

How can I fix this?

Offline

#10 2018-04-06 17:00:34

Scimmia
Fellow
Registered: 2012-09-01
Posts: 11,560

Re: [SOLVED] Failed to start Load Kernel Modules after upgrade

By doing the opposite of whatever you did to install it.

Offline

#11 2018-04-06 17:01:40

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 19,791

Re: [SOLVED] Failed to start Load Kernel Modules after upgrade

Start with pacman -Rs vboxguest

Then, reboot, and lets see if there are any residual effects.

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

Offline

#12 2018-04-06 17:06:16

DonTrash
Member
Registered: 2018-04-06
Posts: 9

Re: [SOLVED] Failed to start Load Kernel Modules after upgrade

No, same problem...

Offline

#13 2018-04-06 17:07:36

Scimmia
Fellow
Registered: 2012-09-01
Posts: 11,560

Re: [SOLVED] Failed to start Load Kernel Modules after upgrade

because there's no package named vboxguest, uninstall the actual package that you installed.

Offline

#14 2018-04-06 17:12:04

DonTrash
Member
Registered: 2018-04-06
Posts: 9

Re: [SOLVED] Failed to start Load Kernel Modules after upgrade

I removed virtualbox-guest-dkms thats what you mean right?

Offline

#15 2018-04-06 17:16:47

Scimmia
Fellow
Registered: 2012-09-01
Posts: 11,560

Re: [SOLVED] Failed to start Load Kernel Modules after upgrade

Yes, and there's no way you still have the same errors after removing that.

Offline

#16 2018-04-06 17:41:07

DonTrash
Member
Registered: 2018-04-06
Posts: 9

Re: [SOLVED] Failed to start Load Kernel Modules after upgrade

Now it works. I reinstalled linux and linux-headers.
Thanks to you guys!

Offline

#17 2018-04-06 18:14:20

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 19,791

Re: [SOLVED] Failed to start Load Kernel Modules after upgrade

My bad... Sorry.

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

Offline

Pages: 1

Board footer

Powered by FluxBB