vboxsf module loads but mount gives "No such device" error

[loukingjr]

@pmenso57,

You may have an issue that was first noticed yesterday. Look in /sbin for mount.vboxsf and see where the symlink points to.
Then see if the file exists there ( /usr/lib/VBoxGuestAdditions ) or does the file exist at ( /usr/lib/x86_64-linux-gnu/VBoxGuestAdditions )

I looked at that yesterday but now looking at mount.vboxsf in one of my guests it says the link is broken but my shared folder still mounts. It is set to auto-mount.

[Perryg]

@pmenso57,

You may have an issue that was first noticed yesterday. Look in /sbin for mount.vboxsf and see where the symlink points to.
Then see if the file exists there ( /usr/lib/VBoxGuestAdditions ) or does the file exist at ( /usr/lib/x86_64-linux-gnu/VBoxGuestAdditions )

I looked at that yesterday but now looking at mount.vboxsf in one of my guests it says the link is broken but my shared folder still mounts. It is set to auto-mount.

Auto-mount uses a different device ( IIRC ) which mounts the share as an external media much like a CD. These are stored in /media/ by default.

Now this one ( auto-mount ) can cause issues, so if you are having problems with shared folders that might be the reason.

[loukingjr]

I'm not having any shared folder issues but mount.vboxsf is in ( /usr/lib/x86_64-linux-gnu/VBoxGuestAdditions )

speaking of auto-mount, I know people recommend not using it because of possible issues but in 5 years I've not had any in hundreds of guests with the exception of one Linux distro, which I forget, where auto-mount wouldn't work and I had to mount it in rc.local.

[pmenso57]

@pmenso57,

You may have an issue that was first noticed yesterday. Look in /sbin for mount.vboxsf and see where the symlink points to.
Then see if the file exists there ( /usr/lib/VBoxGuestAdditions ) or does the file exist at ( /usr/lib/x86_64-linux-gnu/VBoxGuestAdditions )

I will try tomorrow night, have to reinstall new version etc..

[loukingjr]

I guess this all begs the question should one correct the link to point to where mount.vboxsf actually is, or move the VBoxGuestAdditions folder to /usr/lib, or just wait for a new release?

[Perryg]

My fix would be to correct the symlink. That way whenever the fix comes out it will not need to be fixed yet again.

[loukingjr]

thanks Perry. I guess in my case it really doesn't matter since I use auto-mounting shared folders. I was more or less asking for those that don't. It's a good thing I only installed 4.3.10 in 5 Linux guests out of 49 . I take it there is no issue with Windows guests?

[Kernel-Panic]

Same issue here on linux hosts.. Upgraded my mythbuntu box and lost backend storage. Looked up mount.vboxsf and it's not there! Break out the Grecian formulan and roll back again.

[Kernel-Panic]

The clone that I didn't upgrade guest additions on of the same guest mounts fine, so the problem is in the additions.iso.

[Kernel-Panic]

The mounts from the host worked but not the /etc/fstab mounts from the guest. And the guest works when I roll back guest additions to 3.2.8.

I use fstab on the guest to specify mythtv uid/gid during mounting, if I dont mythbackend doesnt work.