LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices



Reply
 
Search this Thread
Old 05-24-2013, 02:14 AM   #1
kikinovak
Senior Member
 
Registered: Jun 2011
Location: Montpezat (South France)
Distribution: Slackware, Slackware64
Posts: 1,959

Rep: Reputation: 975Reputation: 975Reputation: 975Reputation: 975Reputation: 975Reputation: 975Reputation: 975Reputation: 975
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.

Last edited by kikinovak; 05-24-2013 at 02:44 AM.
 
Old 05-24-2013, 03:03 AM   #2
Nikosis
Member
 
Registered: Dec 2005
Location: In front of the monitor
Distribution: Slackware
Posts: 312

Rep: Reputation: 59
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

Last edited by Nikosis; 05-24-2013 at 03:07 AM.
 
Old 05-24-2013, 04:06 AM   #3
kikinovak
Senior Member
 
Registered: Jun 2011
Location: Montpezat (South France)
Distribution: Slackware, Slackware64
Posts: 1,959

Original Poster
Rep: Reputation: 975Reputation: 975Reputation: 975Reputation: 975Reputation: 975Reputation: 975Reputation: 975Reputation: 975
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?

Last edited by kikinovak; 05-24-2013 at 04:12 AM.
 
Old 05-24-2013, 04:48 AM   #4
Nikosis
Member
 
Registered: Dec 2005
Location: In front of the monitor
Distribution: Slackware
Posts: 312

Rep: Reputation: 59
Quote:
Originally Posted by kikinovak View Post
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...

Last edited by Nikosis; 05-24-2013 at 05:09 AM.
 
Old 05-24-2013, 08:01 AM   #5
kikinovak
Senior Member
 
Registered: Jun 2011
Location: Montpezat (South France)
Distribution: Slackware, Slackware64
Posts: 1,959

Original Poster
Rep: Reputation: 975Reputation: 975Reputation: 975Reputation: 975Reputation: 975Reputation: 975Reputation: 975Reputation: 975
Quote:
Originally Posted by Nikosis View Post
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.
 
Old 05-24-2013, 09:08 AM   #6
phenixia2003
Member
 
Registered: May 2006
Location: France
Distribution: Slackware
Posts: 299

Rep: Reputation: 179Reputation: 179
Hello,


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


--
SeB
 
Old 05-24-2013, 11:48 AM   #7
tronayne
Senior Member
 
Registered: Oct 2003
Location: Northeastern Michigan, where Carhartt is a Designer Label
Distribution: Slackware 32- & 64-bit Stable
Posts: 3,121

Rep: Reputation: 819Reputation: 819Reputation: 819Reputation: 819Reputation: 819Reputation: 819Reputation: 819
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.
 
Old 05-25-2013, 04:07 AM   #8
ppr:kut
Slackware Contributor
 
Registered: Aug 2006
Location: Netherlands
Distribution: Slackware
Posts: 369

Rep: Reputation: 94
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)?
 
Old 05-25-2013, 04:15 AM   #9
kikinovak
Senior Member
 
Registered: Jun 2011
Location: Montpezat (South France)
Distribution: Slackware, Slackware64
Posts: 1,959

Original Poster
Rep: Reputation: 975Reputation: 975Reputation: 975Reputation: 975Reputation: 975Reputation: 975Reputation: 975Reputation: 975
Quote:
Originally Posted by ppr:kut View Post
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
 
Old 05-25-2013, 04:25 AM   #10
ppr:kut
Slackware Contributor
 
Registered: Aug 2006
Location: Netherlands
Distribution: Slackware
Posts: 369

Rep: Reputation: 94
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.
 
  


Reply

Tags
virtualbox


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Virtualbox update actinide Linux - Newbie 9 01-23-2013 12:20 PM
[SOLVED] VirtualBox Kernel Driver Missing after Update? lkraemer Slackware 5 12-26-2012 10:55 AM
Update Manager Glitch DigitalBeach Linux - Newbie 2 04-05-2011 05:50 PM
VirtualBox broken after kernel update in Arch Linux MTK358 Linux - Software 10 09-06-2010 08:51 PM
LXer: Update: VirtualBox 2.2.0 LXer Syndicated Linux News 0 04-13-2009 06:00 PM


All times are GMT -5. The time now is 08:42 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration