Failed to start Load Kernel Modules

shadowphoton · 2017-06-01 10:43:26

After the last update I've made I have "Failed to start Load Kernel Modules" error on my boot screen.
When I check

systemctl status systemd-modules-load.service

as it was suggested during the boot, I get:

Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.

When I boot my system with LTS kernel I do get the same warning, but the systemd-modules-load.service is active.
I'm not sure how to resolve this issue.
Any suggestions?

judd1 · 2017-06-01 11:25:34

https://bbs.archlinux.org/viewtopic.php?id=226643

shadowphoton · 2017-06-01 12:57:50

I didn't have the virtualbox-guest-modules-arch package people were suggesting to be removed (at end of the topic). So, I couldn't use that as a solution.

I've tried out your suggestion -> to delete the /usr/lib/modules-load.d/virtualbox-host-modules-arch.conf file.
It did stop "Failed to start Load Kernel Modules" error and journal warning. However, now when I type

systemctl status systemd-modules-load.service

I get

systemd-modules-load.service - Load Kernel Modules                                       
   Loaded: loaded (/usr/lib/systemd/system/systemd-modules-load.service; static; vendor preset: disabled)
   Active: inactive (dead)                   
Condition: start condition failed at Thu 2017-06-01 14:29:24 CEST; 7min ago                
           ├─ ConditionDirectoryNotEmpty=|/lib/modules-load.d was not met                  
           ├─ ConditionDirectoryNotEmpty=|/usr/lib/modules-load.d was not met              
           ├─ ConditionDirectoryNotEmpty=|/usr/local/lib/modules-load.d was not met        
           ├─ ConditionDirectoryNotEmpty=|/etc/modules-load.d was not met                  
           ├─ ConditionDirectoryNotEmpty=|/run/modules-load.d was not met                  
           ├─ ConditionKernelCommandLine=|modules-load was not met                         
           └─ ConditionKernelCommandLine=|rd.modules-load was not met                      
     Docs: man:systemd-modules-load.service(8)                                             
           man:modules-load.d(5)

Not sure if that's how it's supposed to be?

seth · 2017-06-01 13:28:47

compare

uname -a

and

pacman -Q linux

If they don't match, you're booting an old kernel because something went wrong with an update - usually you forgot to mount the /boot partition.
In this case just ensure a mounted /boot and re-install the linux package.

loqs · 2017-06-01 13:47:34

If that is the issue the virtualbox-host-modules-arch package would also need to be reinstalled to restore its functionality.

shadowphoton · 2017-06-01 13:53:23

seth wrote:

If they don't match, you're booting an old kernel because something went wrong with an update - usually you forgot to mount the /boot partition.
In this case just ensure a mounted /boot and re-install the linux package.

That's not an issue here.
I'm using Grub menu to chose wich kernel do I boot my system with. Linux or linux-lts.

loqs wrote:

If that is the issue the virtualbox-host-modules-arch package would also need to be reinstalled to restore its functionality.

Where you referring to seth's comment or my "systemctl echo"?

loqs · 2017-06-01 14:02:22

shadowphoton wrote:

Where you referring to seth's comment or my "systemctl echo"?

To seth's comments. I believe you are mistaken hat it can not be a kernel version mismatch did you try the commands provided to verify?
If the versions match please post the output from the journal of systemd-modules-load.service from the boot when it was failing.

$ journalctl -b -1 --unit=systemd-modules-load.service

Change the value passed to -b to -2 etc until you find the correct boot.
Systemd#Filtering_output
Is the system using virtualbox? If yes as a host or guest?

shadowphoton · 2017-06-01 14:26:22

For a long time now, I use Grub to select what kernel I'll use to boot my system with, so I'm not sure what type of mismatch are you refering to?
If I boot with linux kernel, uname -a will give me the same version as pacman -Q linux
If I boot with linux-lts kernel, uname -a will give me the same version as pacman -Q linux-lts

As for the journal output, this is what I got for LTS kernel

june 01 14:28:50 arch systemd[1]: Stopped Load Kernel Modules.

And this is the output for a regular linux kernel

june 01 12:06:20 arch systemd[1]: Starting Load Kernel Modules...
june 01 12:06:20 arch systemd-modules-load[1355]: Failed to insert 'vboxdrv': No such file or directory
june 01 12:06:20 arch systemd-modules-load[1355]: Failed to insert 'vboxpci': No such file or directory
june 01 12:06:20 arch systemd-modules-load[1355]: Failed to insert 'vboxnetadp': No such file or directory
june 01 12:06:20 arch systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1/FAILURE
june 01 12:06:20 arch systemd[1]: Failed to start Load Kernel Modules.
june 01 12:06:20 arch systemd[1]: systemd-modules-load.service: Unit entered failed state.
june 01 12:06:20 arch systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'.

Latest boot session has no entries.
System is not using virtualbox.

loqs · 2017-06-01 14:31:32

shadowphoton wrote:

System is not using virtualbox.

So why is virtualbox-host-modules-arch installed on the system?

shadowphoton · 2017-06-01 14:33:12

For my testing.

edit:
Btw. I don't have virtualbox-host-modules-arch installed, I have virtualbox-host-dkms...

Last edited by shadowphoton (2017-06-01 14:41:46)

loqs · 2017-06-01 14:44:32

So the error is expected as you installed a package providing modules that can not be loaded? See also smart questions.

seth · 2017-06-01 14:45:32

a) this makes no sense at all
b) check your pacman log, the dkms build probably only ran for the linux-lts kernel

---
about the mismatch: if you earch this forum you'll find quite some threads about the installed and booted kernel get out of sync because vmllinuz didn't go to the proper location during an upgrade.
it's a actually very common issue.

loqs · 2017-06-01 14:54:09

https://bugs.archlinux.org/task/54252 but that is i686 only.

shadowphoton · 2017-06-01 15:32:33

loqs wrote:

https://bugs.archlinux.org/task/54252 but that is i686 only.

I am still on i686... Thanks for the link, I didn't see it, nor as one posting in "Newbie Corner" did I connect it with the issue I'm having.
So, I guess I have to wait for that bug to be resolved?

loqs wrote:

See also smart questions.

Thanks again for your effort, I do appreciate it.
Although, you didn't have to invest your time in being condescending toward someone posting in "Newbie Corner" with that "smart questions" remark... Most people are aware of Code of conduct and "How to ask questions the smart way", but not everyone knows everything about anything.

seth wrote:

a) this makes no sense at all
b) check your pacman log, the dkms build probably only ran for the linux-lts kernel
---
about the mismatch: if you earch this forum you'll find quite some threads about the installed and booted kernel get out of sync because vmllinuz didn't go to the proper location during an upgrade.
it's a actually very common issue.

I don't have the mismatch, but I'll be aware of it, knowing that it could happen.
I've searched the pacman log and dkms is using linux 4.11 and not the lts. But I guess the bug that loqs pointed out is the issue here.

Last edited by shadowphoton (2017-06-01 15:36:31)

loqs · 2017-06-01 15:43:50

As per phasing-out-i686-support you might want to consider swapping distributions if you can not change architecture to x86_86. Packages are still produced for i686 but I would not expect them to be tested.
If the bug is resolved upstream in a new release it should be fixed when arch updates to that new release. If it is not pursued upstream this may be its outcome 54087#comment157808.
Edit:
You can verify if it is this issue by trying to manually load one of the modules and then check dmesg for errors.

Last edited by loqs (2017-06-01 15:45:06)

shadowphoton · 2017-06-01 15:55:06

loqs wrote:

As per phasing-out-i686-support you might want to consider swapping distributions if you can not change architecture to x86_86. Packages are still produced for i686 but I would not expect them to be tested.
If the bug is resolved upstream in a new release it should be fixed when arch updates to that new release. If it is not pursued upstream this may be its outcome 54087#comment157808.
Edit:
You can verify if it is this issue by trying to manually load one of the modules and then check dmesg for errors.

Yes, I am aware of i686 phasing out, and I do have hardware that supports x86_64.
I plan to migrate as soon as possible. Nonetheless, thanks for the warning.
And again, thank you very much for your effort, you've been extremly helpful.

newbie1962 · 2017-06-01 18:27:51

Post the answer of this command:

ls -l /etc/modules-load.d/

shadowphoton · 2017-06-01 23:21:45

newbie1962 wrote:

Post the answer of this command:
ls -l /etc/modules-load.d/

The folder is empty because if I leave virtualbox-host-dkms.conf somehow it manages to conflict with my boot process and it "fails to start Load Kernel Modules".

Arch Linux

#1 2017-06-01 10:43:26

Failed to start Load Kernel Modules

#2 2017-06-01 11:25:34

Re: Failed to start Load Kernel Modules

#3 2017-06-01 12:57:50

Re: Failed to start Load Kernel Modules

#4 2017-06-01 13:28:47

Re: Failed to start Load Kernel Modules

#5 2017-06-01 13:47:34

Re: Failed to start Load Kernel Modules

#6 2017-06-01 13:53:23

Re: Failed to start Load Kernel Modules

#7 2017-06-01 14:02:22

Re: Failed to start Load Kernel Modules

#8 2017-06-01 14:26:22

Re: Failed to start Load Kernel Modules

#9 2017-06-01 14:31:32

Re: Failed to start Load Kernel Modules

#10 2017-06-01 14:33:12

Re: Failed to start Load Kernel Modules

#11 2017-06-01 14:44:32

Re: Failed to start Load Kernel Modules

#12 2017-06-01 14:45:32

Re: Failed to start Load Kernel Modules

#13 2017-06-01 14:54:09

Re: Failed to start Load Kernel Modules

#14 2017-06-01 15:32:33

Re: Failed to start Load Kernel Modules

#15 2017-06-01 15:43:50

Re: Failed to start Load Kernel Modules

#16 2017-06-01 15:55:06

Re: Failed to start Load Kernel Modules

#17 2017-06-01 18:27:51

Re: Failed to start Load Kernel Modules

#18 2017-06-01 23:21:45

Re: Failed to start Load Kernel Modules

Board footer