For some time I've seen some red text flashing by during boot. Today I decided to look into it. The systemctl service systemd-modules-load.service
is failing with this text:
tomas@bonus-debian:~$ sudo systemctl status systemd-modules-load ● systemd-modules-load.service - Load Kernel Modules Loaded: loaded (/lib/systemd/system/systemd-modules-load.service; static; vendor preset: enabled) Active: failed (Result: exit-code) since ma. 2015-11-09 02:58:48 CET; 5min ago Docs: man:systemd-modules-load.service(8) man:modules-load.d(5) Process: 644 ExecStart=/lib/systemd/systemd-modules-load (code=exited, status=1/FAILURE) Main PID: 644 (code=exited, status=1/FAILURE) nov. 09 02:58:48 bonus-debian systemd[1]: Starting Load Kernel Modules... nov. 09 02:58:48 bonus-debian systemd-modules-load[644]: Failed to find module '-r usbhid' nov. 09 02:58:48 bonus-debian systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1/FAILURE nov. 09 02:58:48 bonus-debian systemd[1]: Failed to start Load Kernel Modules. nov. 09 02:58:48 bonus-debian systemd[1]: systemd-modules-load.service: Unit entered failed state. nov. 09 02:58:48 bonus-debian systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'.
I thought I'd start out by Googling the issue:
Ouch.
My system doesn't seem to mind that the driver failed to load, as I haven't noticed a degraded experience, but I'd still like to fix it.
Since Google got me nowhere, I'm stuck already. I have no idea where to start looking.
How do I figure out why systemctl service "systemd-modules-load" fails?
Best Answer
I too had this issue. I was able to solve it by following the instructions on the Arch Linux systemd wiki page. Here is a summary of what I did :
Lets find the systemd services which fail to start
Ok, we found a problem with systemd-modules-load service. We want to know more.
If the Process ID is not listed, just restart the failed service with
Now we have the process id (PID) to investigate this error in depth. Enter the following command with the current Process ID (here: 15630):
We see that some of the kernel module configs have wrong settings. Therefore we have a look at these settings in /etc/modules-load.d/
The Failed to find module 'blacklist usblp' error message might be related to a wrong setting inside of blacklist.conf. Lets deactivate it with inserting a trailing # before each option we found via step 3:
Now, try to start systemd-modules-load:
If it was successful, this should not prompt anything. If you see any error, go back to step 3 and use the new PID for solving the errors left.
If everything is ok, you can verify that the service was started successfully with: