Unable to Access New Samba Shared Folders

[jrcampbell]

Hey guys. I've been using VB for a while now, and had utilized an Ubuntu guest to share folders from my Windows host to the guest machine, and share back changes and updates via a samba share. Unfortunately, since a recent update, when I add a new shared folder, it appears that the owner group is vboxsf, and when I mount it to my samba shared folder, it's inaccessible. Can anyone help me get through this? It's really frustrating when I'm trying to expand some of my work out, and can no longer do what I used VB to do.

Thanks.

[socratis]

Unfortunately, since a recent update

Update what? Host? Guest? VirtualBox? A combination?

when I add a new shared folder, it appears that the owner group is vboxsf

What's the owner in the previous ones? And are we still talking about a SaMBa (SMB) share, or a VirtualBox Shared Folder (VBoxSF)? Those are quite different concepts, please double-check.

and when I mount it to my samba shared folder, it's inaccessible

If it's an SMB share, that's between your Host and your Guest, and what might have changed during the update.

But if it's a VBoxSF, then 1) you have to update the Guest Additions (GAs) in your Guest, 2) you got to be a member of the 'vboxsf' group, as described in the User Manual.

We need to see a complete VBox.log, from a complete VM run, where the problem occurs:

• Start the VM from cold-boot (not from a paused or saved state) / Observe or recreate the problem / Shutdown the VM (force close it if you have to).
• With the VM completely shut down (not paused or saved), right-click on the VM in the VirtualBox Manager and select "Show Log".
• Save only the first "VBox.log", ZIP it and attach it to your response. See the "Upload attachment" tab below the reply form.

[jrcampbell]

I'll upload the log sometime tomorrow. However, it was a recent VirtualBox update that seems to have broken things.

Previously, when I would have a share that was auto-mounted to the VM, it would be owned by root and root group. Now, any new folders that are created are actually under the group vboxsf, instead of root. So, when I use rar2fs to mount to my samba share, it's still utilizing the vboxsf group, and this is breaking my shared folders. Previous folders that have been shared are not showing this issue, but any new shared folder is having this issue.

Guest Additions have been updated. I'm even recreating the issue with a new VM.