Description of problem: After an upgrade to Fedora 21, I get the following message every boot: [ 0.857565] systemd[1]: systemd-modules-load.service: main process exited, code=exited, status=1/FAILURE [ 0.858128] systemd[1]: Failed to start Load Kernel Modules. [ 0.858194] systemd[1]: Unit systemd-modules-load.service entered failed state. [ 0.858214] systemd[1]: systemd-modules-load.service failed. However, all of my kernel modules actually do load fine, and the system works normally. systemctl status systemd-modules-load.service: ● systemd-modules-load.service - Load Kernel Modules Loaded: loaded (/usr/lib/systemd/system/systemd-modules-load.service; static) Active: active (exited) since Sat 2014-12-13 00:28:11 CST; 14h ago Docs: man:systemd-modules-load.service(8) man:modules-load.d(5) Process: 460 ExecStart=/usr/lib/systemd/systemd-modules-load (code=exited, status=0/SUCCESS) Main PID: 460 (code=exited, status=0/SUCCESS) CGroup: /system.slice/systemd-modules-load.service journalctl -u systemd-modules-load.service shows nothing. This is repeatable on every reboot. I can't seem to find any detailed logs as to what went wrong - where can I look?
Hello, did you install VirtualBox? I started to have that issue after installing VirtualBox as the required kernel modules weren't installed, try installing these packages, according to your needs: # dnf install kmod-VirtualBox-3.17.7-300.fc21.x86_64.x86_64 kmod-VirtualBox.x86_64 VirtualBox-kmodsrc.x86_64
Hello, I got the same problem after upgrading from Fedora 20. Removing of VirtualBox did not change anything. However, rebuilding of the initramfs seems solve the issue: mkinitrd /boot/initramfs-3.17.4-301.fc21.x86_64.img 3.17.4-301.fc21.x86_64
I'm experiencing this as well, but on the 3.18.3-201.fc21 kernel. Rebuilding my initramfs did not fix the issue for me. And like bztdlinux said, the system journal doesn't give me any details. How can one go about debugging kernel module loading problems like this?
(In reply to Martín Cigorraga from comment #1) > Hello, did you install VirtualBox? > I started to have that issue after installing VirtualBox as the required > kernel modules weren't installed, try installing these packages, according > to your needs: > # dnf install kmod-VirtualBox-3.17.7-300.fc21.x86_64.x86_64 > kmod-VirtualBox.x86_64 VirtualBox-kmodsrc.x86_64 https://ask.fedoraproject.org/en/question/68083/is-something-serious-if-systemctl-status-systemd-modules-loadservice-says-its-failed/
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '21'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 21 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.