LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (http://www.linuxquestions.org/questions/slackware-14/)
-   -   VirtualBox glitch after kernel update to 3.2.45: VBoxCreateUSBNode.sh ? (http://www.linuxquestions.org/questions/slackware-14/virtualbox-glitch-after-kernel-update-to-3-2-45-vboxcreateusbnode-sh-4175463263/)

kikinovak 05-24-2013 01:14 AM

VirtualBox glitch after kernel update to 3.2.45: VBoxCreateUSBNode.sh ?
 
Hi,

I just updated my kernel from 3.2.29 to 3.2.45 on my main workhorse PC. I have VirtualBox installed on it. It's basically built from my own SlackBuilds, slightly modified from the ones found on SlackBuilds.org.

The update itself went fine. I switched to init 3, updated, rebuilt the initrd, edited LILO and ran it, rebooted, then rebuilt the Nvidia driver and the virtualbox-kernel package. I also took care of reinstalling the VirtualBox Extension Pack.

Now I have these strange error messages on boot time (quoting from memory, since it flies by rather fast):

Code:

udevd: failed to execute /usr/share/virtualbox/VBoxCreateUSBNode.sh: No such file or directory
VirtualBox seems to run fine, though.

Any idea where this error message comes from, and what I can do to get rid of it?

According to Google, other folks have the same problem, but they're running either Ubuntu or Debian, and the suggested solutions can't really apply.

Nikosis 05-24-2013 02:03 AM

Your udev rule is pointing to wrong directory, find the location of "VBoxCreateUSBNode.sh"- most likely it's in /opt and change link location in 10.vboxdrv.rules in /etc/udev/rules.d
Quote:

/opt/VirtualBox/VBoxCreateUSBNode.sh

kikinovak 05-24-2013 03:06 AM

OK, I just found the culprit, but in a completely unexpected place. But first, there's no VirtualBox related files either in /opt or /etc/udev/rules.d. What was more curious: upon investigation, the file /usr/share/virtualbox/VBoxCreateUSBNode.sh is there. So why can't it be found? The only possible explanation is that /usr is not mounted yet. Let's see.

I rebooted again and noticed that the error message occurs early in the boot process. In fact right after the modules from the Initrd are loaded.

On a hunch, I removed VirtualBox and all related modules and rebuilt my Initrd. Then I rebooted and reinstalled VirtualBox and rebooted again. And everything works fine now.

I must come to the conclusion that some VirtualBox modules get wrongly inserted into the Initrd and then create this mess at startup.

I hesitate to mark this as solved, since some details remain a mystery. Someone has a more in-depth explanation for what happened?

Nikosis 05-24-2013 03:48 AM

Quote:

Originally Posted by kikinovak (Post 4957870)
The only possible explanation is that /usr is not mounted yet.

It's possible if your /usr is on separate partition.

Quote:

But first, there's no VirtualBox related files either in /opt or /etc/udev/rules.d.
What's interesting, if there was no related files in /etc/udev/rules.d, what called the function...

kikinovak 05-24-2013 07:01 AM

Quote:

Originally Posted by Nikosis (Post 4957895)
It's possible if your /usr is on separate partition.


What's interesting, if there was no related files in /etc/udev/rules.d, what called the function...

Well, no. Only /home is on a different partition (and on a different machine). And there's strictly no custem udev rule. Go figure.

phenixia2003 05-24-2013 08:08 AM

Hello,


SlackBuild for Virtualbox OSE installs 10-virtualbox.rules in /lib/udev/rules.d/


--
SeB

tronayne 05-24-2013 10:48 AM

I don't use the SlackBuild for VirtualBox; I prefer to simply install the .run (which has always worked fine for me).
Code:

locate VBoxCreateUSBNode.sh
/opt/VirtualBox/VBoxCreateUSBNode.sh

is where it's at with the .run install.

I've upgraded to 3.2.45 (Slackware 14.0 64-bit) and VirtualBox works just fine -- what the heck, the latest Critical Updates from microjunk installed in Win7...

Hope this helps some.

ppr:kut 05-25-2013 03:07 AM

Quote:

Well, no. Only /home is on a different partition (and on a different machine). And there's strictly no custem udev rule. Go figure.
Hmm, all I can find on google points towards /usr not mounted in time as well. If that's not the case it's rather weird :/
Do you know in what stage the error appears (like, during the initrd stage or after)?

kikinovak 05-25-2013 03:15 AM

Quote:

Originally Posted by ppr:kut (Post 4958562)
Hmm, all I can find on google points towards /usr not mounted in time as well. If that's not the case it's rather weird :/
Do you know in what stage the error appears (like, during the initrd stage or after)?

During the initrd stage. Check my second post. Rebuilding the initrd without vbox* modules present solved the problem.

Cheers,

Niki

ppr:kut 05-25-2013 03:25 AM

Oops, heh. Missed that :)
I'll check the udev rules next time I do an update. It's quite likely mkinitrd picks up the rules file and triggers it on boot in the initrd. So maybe it needs to be moved somewhere else now.


All times are GMT -5. The time now is 07:38 AM.