vboxdrv.service won't start
Posted: 8. Sep 2020, 03:40
Host: Mint 19.3, all latest updates applied
VirtualBox: 6.1.14
Hi all,
This was working but suddenly stopped. I am running a Lenovo ThinkCentre mini PC with UEFI SecureBoot turned off (very clearly gives this msg on reboot). I have uninstalled and re-installed VB multiple times. When I run dmesg I don't see anything useful including no 'PKCS not signed' type errors, I'm happy to post the whole thing here if you think it will help. Note from the last paste below it looks like some installation files are missing but surely my multiple uninstalls + re-installs would have solved that??
Thanks in advance,
Paul
VirtualBox: 6.1.14
Hi all,
This was working but suddenly stopped. I am running a Lenovo ThinkCentre mini PC with UEFI SecureBoot turned off (very clearly gives this msg on reboot). I have uninstalled and re-installed VB multiple times. When I run dmesg I don't see anything useful including no 'PKCS not signed' type errors, I'm happy to post the whole thing here if you think it will help. Note from the last paste below it looks like some installation files are missing but surely my multiple uninstalls + re-installs would have solved that??
Thanks in advance,
Paul
systemctl status vboxdrv.service
● vboxdrv.service - VirtualBox Linux kernel module
Loaded: loaded (/usr/lib/virtualbox/vboxdrv.sh; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Mon 2020-09-07 18:26:33 PDT; 19s ago
Process: 836 ExecStart=/usr/lib/virtualbox/vboxdrv.sh start (code=exited, status=1/FAILURE)
Sep 07 18:26:33 fun vboxdrv.sh[836]: kmodsign: /lib/modules/5.4.0-45-generic/misc/vboxnetflt.ko.~signed~: No such file or directory
Sep 07 18:26:33 fun vboxdrv.sh[836]: At main.c:271:
Sep 07 18:26:33 fun vboxdrv.sh[836]: - SSL error:02001002:system library:fopen:No such file or directory: ../crypto/bio/bss_file.c:72
Sep 07 18:26:33 fun vboxdrv.sh[836]: - SSL error:2006D080:BIO routines:BIO_new_file:no such file: ../crypto/bio/bss_file.c:79
Sep 07 18:26:33 fun vboxdrv.sh[836]: kmodsign: /lib/modules/5.4.0-45-generic/misc/vboxnetadp.ko.~signed~: No such file or directory
Sep 07 18:26:33 fun vboxdrv.sh[836]: vboxdrv.sh: failed: modprobe vboxdrv failed. Please use 'dmesg' to find out why.
Sep 07 18:26:33 fun vboxdrv.sh[7279]: failed: modprobe vboxdrv failed. Please use 'dmesg' to find out why.
Sep 07 18:26:33 fun systemd[1]: vboxdrv.service: Control process exited, code=exited status=1
Sep 07 18:26:33 fun systemd[1]: vboxdrv.service: Failed with result 'exit-code'.
Sep 07 18:26:33 fun systemd[1]: Failed to start VirtualBox Linux kernel module.
Note no misc dir here:root@fun:~# /sbin/vboxconfig
vboxdrv.sh: Stopping VirtualBox services.
depmod: WARNING: could not open /lib/modules/5.4.55/modules.order: No such file or directory
depmod: WARNING: could not open /lib/modules/5.4.55/modules.builtin: No such file or directory
vboxdrv.sh: Starting VirtualBox services.
vboxdrv.sh: Building VirtualBox kernel modules.
At main.c:271:
- SSL error:02001002:system library:fopen:No such file or directory: ../crypto/bio/bss_file.c:72
- SSL error:2006D080:BIO routines:BIO_new_file:no such file: ../crypto/bio/bss_file.c:79
kmodsign: /lib/modules/5.4.0-45-generic/misc/vboxdrv.ko.~signed~: No such file or directory
At main.c:271:
- SSL error:02001002:system library:fopen:No such file or directory: ../crypto/bio/bss_file.c:72
- SSL error:2006D080:BIO routines:BIO_new_file:no such file: ../crypto/bio/bss_file.c:79
kmodsign: /lib/modules/5.4.0-45-generic/misc/vboxnetflt.ko.~signed~: No such file or directory
At main.c:271:
- SSL error:02001002:system library:fopen:No such file or directory: ../crypto/bio/bss_file.c:72
- SSL error:2006D080:BIO routines:BIO_new_file:no such file: ../crypto/bio/bss_file.c:79
kmodsign: /lib/modules/5.4.0-45-generic/misc/vboxnetadp.ko.~signed~: No such file or directory
vboxdrv.sh: failed: modprobe vboxdrv failed. Please use 'dmesg' to find out why.
There were problems setting up VirtualBox. To re-start the set-up process, run
/sbin/vboxconfig
as root. If your system is using EFI Secure Boot you may need to sign the
kernel modules (vboxdrv, vboxnetflt, vboxnetadp, vboxpci) before you can load
them. Please see your Linux system's documentation for more information.
root@fun:~#
root@fun:~# ll /lib/modules/5.4.0-45-generic
total 5784
drwxr-xr-x 5 root root 4096 Sep 7 18:30 ./
drwxr-xr-x 8 root root 4096 Sep 7 17:06 ../
lrwxrwxrwx 1 root root 39 Aug 26 09:06 build -> /usr/src/linux-headers-5.4.0-45-generic/
drwxr-xr-x 2 root root 4096 Aug 26 09:06 initrd/
drwxr-xr-x 17 root root 4096 Sep 6 22:21 kernel/
-rw-r--r-- 1 root root 1387002 Sep 7 18:30 modules.alias
-rw-r--r-- 1 root root 1363627 Sep 7 18:30 modules.alias.bin
-rw-r--r-- 1 root root 8105 Aug 26 09:06 modules.builtin
-rw-r--r-- 1 root root 10257 Sep 7 18:30 modules.builtin.bin
-rw-r--r-- 1 root root 63335 Aug 26 09:06 modules.builtin.modinfo
-rw-r--r-- 1 root root 610398 Sep 7 18:30 modules.dep
-rw-r--r-- 1 root root 853048 Sep 7 18:30 modules.dep.bin
-rw-r--r-- 1 root root 330 Sep 7 18:30 modules.devname
-rw-r--r-- 1 root root 220055 Aug 26 09:06 modules.order
-rw-r--r-- 1 root root 828 Sep 7 18:30 modules.softdep
-rw-r--r-- 1 root root 613998 Sep 7 18:30 modules.symbols
-rw-r--r-- 1 root root 746671 Sep 7 18:30 modules.symbols.bin
drwxr-xr-x 3 root root 4096 Sep 6 22:21 vdso/
root@fun:~#