Won't boot - "Failed to start Load Kernel Modules"
2 Attachment(s)
The computer won't boot, with the error message "Failed to start Load Kernel Modules". When running journalctl -xb I see messages about 'failed to load find module vboxdrv, vboxnetflt, vboxnetadp, vboxpci. I recently upgraded my Fedora 24 system, and I'm wondering if this could be because the VirtualBox is not yet caught up? What's the easiest fix for this - should I remove VirtualBox, and if so, what parts? Dkms, or just those modules that were listed? I tried booting with older kernels, but this did not work either.
Thanks!!! |
VirtualBox modules are not needed to boot. Something else is wrong.
|
boot up, and when it gets stuck (i suppose) can you press Ctrl+Alt+F2?
Does that bring you to a text console login? if yes, login, enter the following commands and post the output here: Code:
lspci -k so if the grep returns nothing, try Code:
sudo find / -name Xorg.0.log -exec grep -C4 EE {} \; |
Looking at your screenshot ... wondering if systemd stopped loading modules after vbox modules were not found.
|
1 Attachment(s)
Hey, I really appreciate this quick help.
I'm sorry to post screenshots, but all I have now is my phone, and typing the output would take forever and certainly allow mistakes to enter. Attached is a pic of the output of the commands lspci -k, uname -a, and sudo grep -C4 EE /var/log/Xorg.0.log. As for the Vbox issues, I think I've read something that there can be issues when you upgrade the kernel but the vbox and associated files are not upgraded and in sync. But I don't know if, as suggested, this just impacts vbox alone loading. |
nothing pops out from the code i requested, however the first 3 lines of that scrot might merit closer inspection.
|
I've read that if one of the modules can't be loaded, that can cause the whole system to entered a failed stated. Aside from losing VirtualBox, is there any risk of right now of doing a dnf remove VirtualBox and also dkms?
|
Quote:
|
Removed VirtualBox and Dkms and still getting warning "Failed to find module:
Vboxdrv Vboxnetflt Vboxnetadp Vboxpci" What can I do to exclude the system from attempting to load these? How exactly do I go about that? I've tried /etc/modprobe*/blacklist and blacklist vboxdrv etc, but that doesn't seem to work. Thanks. |
I'm cautiously optimistic that excluding these modules - once I know how to do so - will solve the problem.....
|
Sorry, I'm foreigner on systemd land. But I'm sure if you use your favorite search engine with keywords "systemd module loading" you will get your answer.
|
Sitting at home with food poisoning today (bleh), I've spent hours and hours searching, but have found nothing to solve the issue, unfortunately. Actually, the searching is the only way I learned about blacklisting....
|
Well, took me 30 seconds to get this one: https://wiki.gentoo.org/wiki/Systemd...module_loading Does it help?
|
Thanks for looking, I do appreciate it. The modules are not specified anywhere in my system, aside from the blacklist file I created, and the webpage doesn't provide any guidance on the blacklisting, at least from what I saw.
|
I just read on a forum that
Quote:
Is there any negatives or concerns you can think of about rebuilding initramfs? Thanks! |
All times are GMT -5. The time now is 06:52 AM. |