top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

RedHat: Failed to start Load Kernel Modules?

0 votes
635 views

I get FAILED TO START LOAD KERNEL MODULES during the boot.

Everytime Kernel is updated VirtualBox modules fail I have to reboot into the new Kernel, run the following commands and then it starts working.

$ sudo akmods --force
$ sudo dracut -v -f
$ sudo grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg

Then everything starts working again and the boot error goes away. My question is how can I automate this task.

posted Jun 18, 2018 by anonymous

Share this question
Facebook Share Button Twitter Share Button LinkedIn Share Button

1 Answer

0 votes

You are using the VirtualBox packages from rpmfusion, yes?

I don't, but I seem to recall they operate differently than the packages from Oracle. The Oracle packages don't rely on akmod and don't put the modules in the initramfs. The vbox modules are checked for existence when vboxdrv.service is run and if they don't exist for the running kernel they are built at that time.

Assuming akmods is being used to build the modules when the kernel is updated there should be some sort of log file in /var/cache/akmods just like there is for nvidia. Have you checked?

Also, have you considered asking about this on the rpmfusion user's list since it is their package?

answer Jun 18, 2018 by anonymous
Similar Questions
0 votes
RedHat: NFS v4 Performance degradation

I recently migrated approximately 100 rhel 6 machines from NFS3 to NFS4 (server is rhel 6.6, clients are a mix from 6.3 to 6.6). Things went pretty smooth until several hours into the new configuration, then things started
running very slowly. Restarting the nfs server process clears the issue which seems to indicate the server is the problem.

The file system itself can do some very high io throughput, on the order of 1GB/sec sustained and the "th" values in /proc/net/rpc/nfsd never increase which indicates i/o's are completing on time with no thread starvation. The server itself is set for 384 threads. During the previous NFS3 config the thread count was much higher and had no problems.

I suspect file locking as the primary application in use ( an in house app) uses a lot of little startup scripts which call other scripts to set up the environment etc. Under normal circumstances this startup takes about 6 seconds. Over time that duration increases up to 30 and even 70 seconds in some cases.

I've scoured every reference to nfs4 performance degradation I could find but nothing seems to call out what we are experiencing. A few retrans exist in nfsstat but nothing that stands out. Generally, everything "look" OK but
clearly is not.

Oh, and this is all being run over 10G Ethernet. If memory serves, I believe the kernel is 2.6.2-504.8.1 on the server.

Any ideas about what else to check would be greatly appreciated.

+1 vote
File system re-sizing with cloud-init on centos or redhat.

Has any one used resizefs module with cloud-init on centos/redhat before? How to call it with #cloud-config user data, do I need to give it any parameters? I googled cloud-init, but it is pretty difficult to find a manual/book on this, and mostly they are Ubuntu based.

If possible, I'd like to use a same image/AMI to boot up instances(VMs) with different disk size setup, and let cloud-init to take care of increasing partition size, and file system re-sizing. Is it possible for centos/redhat?

0 votes
centos 6' repositories against redhat 6 upstream

Wonder how's the relationship between the centos 6's main OS/ repository and redhat 6's repositories. Let's say, Redhat 6 seperate RPMs into a series of repos like:

redhat-6-server ##(base redhat 6 OS/)
redhat-6-server-optional
redhat-6-server-supplementary
redhat-6-server-rhev-agent
rhel-6-server-cf-tools
...

Does centos 6 merge all the redhat 6 repos into one big repository? or still leave out some minor/functional ones? If the second is true, then it will be great if we can find the repo mapping link between Redhat 6 and centos 6.

0 votes
Apache on RedHat

I am setting up Apache on Redhat and have the following errors:

Starting httpd: httpd: Syntax error on line 59 of /etc/httpd/conf/httpd.conf: Cannot load
/etc/httpd/modules/mod_perl.so into server: /etc/httpd/modules/mod_perl.so: cannot open shared object file: No such file or directory
[FAILED]

I have the following 3 lines in the httpd.conf file

ServerRoot "/etc/httpd" - This was already their
LoadModule perl_module modules/mod_perl.so
PerlSwitches -w -T
PerlConfigRequire /var/www/html/bugzilla/mod_perl.pl

I am not sure what else I need to do fix this error.

+1 vote
Can not start VirtualBox on Fedora19

I am getting the error message below on a Fredora 19 system when attempt to start VirualBox Any help will be greatly appreciated :

Kernel driver not installed (rc=-1908) The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there is a permission problem with /dev/vboxdrv. Please reinstall the kernel module by executing '/etc/init.d/vboxdrv setup' as root.

...