Shared Folder not working in Mint 19

[pez4040]

I had some shared folders defined on my Mint 18.3 system. They were working fine. I just upgraded to Mint 19 and I am not able to access any files in the directories. Both of these were defined in virtualbox. I have added myself to the vboxsf group. I've logged off of my id and then logged back on. I've restarted my system but still not able to see the files. I've looked around many different pages and tried various things but nothing is working. Here is some info ... Any ideas ??

jeff@jeff-VirtualBox /media $ id jeff
uid=1000(jeff) gid=1000(jeff) groups=1000(jeff),4(adm),24(cdrom),27(sudo),30(dip),46(plugdev),113(lpadmin),130(sambashare),999(vboxsf)
jeff@jeff-VirtualBox /media $ pwd
/media
jeff@jeff-VirtualBox /media $ ll
total 20
drwxr-xr-x 5 root root 4096 Jun 13 08:33 ./
drwxr-xr-x 23 root root 4096 Jul 10 10:26 ../
drwxr-x---+ 3 root root 4096 Jul 10 15:43 jeff/
drwxrwx--- 2 root vboxsf 4096 Jun 13 08:33 sf_Docs/
drwxrwx--- 2 root vboxsf 4096 Jun 12 20:46 sf_Pics/
jeff@jeff-VirtualBox /media $ tail -3 /etc/group
sambashare130:jeff
vboxsf999:jeff
lxc-dnsmasq131:
jeff@jeff-VirtualBox /media $

[Seadreamer]

The shared folders have to be defined in VB on both Mint 18.3 and 19.

[pez4040]

The folders are defined in the virtual box machine. There was only one machine defined. I was running Mint 18.3 and upgraded in place to Mint 19. The directories are there, but there are no files shown. Everything seems to be done as described in various posts but I am unable to see any files on the Linux guest. I seem to be missing something but I am not sure what.
Jeff

[Seadreamer]

Sorry, I misread your first post. Do you mean vboxusers group, and did you install guest additions for whatever operating system you are using? I assume you have reinstalled VB on 19. Do you have a separate /home partition?

[rockadile]

I just upgraded my guest OS from Mint 18.3 to Mint 19 and I am having the same problem. My user is in the vboxsf group. The folders are set to automount and did just fine in previous Mint versions. The actual folders exist under the /media directory but they are empty. I am, however, able to mount them manually by running the following command:

Code: Select all

sudo mount -t vboxsf <MY-FOLDER-NAME> /media/sf_<MY-FOLDER-NAME>/

But I would prefer not to. Reinstalling the Guest Additions did not help. Adding additional shared folders does nothing, either.

[Seadreamer]

I don't know how to fix your problems. I will tell you how I set up my system, it may give you some insight.

I have a separate home partition and keep my virtual machine on a separate USB hard drive. I point VB to the USB hard drive. VirtualBox is installed in /.

I installed Mint 19 as a fresh install alongside Mint 18.3.

I installed VirtuaBox from a DEB file I downloaded from https://www.virtualbox.org/wiki/Downloads Along with the extension pack from the same page.

My user group is vboxuser.

I installed the latest guest additions to my guest OS which is Windows 7.

I have used the same shared folder since 2014 and it is not the first one I set up.

I know I have kind of a weird system but I hope any of this helps.

[ajgringo619]

I had some shared folders defined on my Mint 18.3 system. They were working fine. I just upgraded to Mint 19 and I am not able to access any files in the directories. Both of these were defined in virtualbox. I have added myself to the vboxsf group. I've logged off of my id and then logged back on. I've restarted my system but still not able to see the files. I've looked around many different pages and tried various things but nothing is working. Here is some info ... Any ideas ??

When you upgraded to 19 did you also upgrade VB? I've had your situation happen to me when the host/guests had different software levels.

[rockadile]

When you upgraded to 19 did you also upgrade VB? I've had your situation happen to me when the host/guests had different software levels.

Nope. Just a "simple" mint upgrade.

[ajgringo619]

When you upgraded to 19 did you also upgrade VB? I've had your situation happen to me when the host/guests had different software levels.

Nope. Just a "simple" mint upgrade.

Try reinstalling the Guest Additions on the VM.

[rockadile]

Try reinstalling the Guest Additions on the VM.

I tried...no dice. Does anyone know where/how VirtualBox handles the mounting? I’ve seen mention of adding it to /etc/profile but I’d rather put it where VirtualBox does if possible.

[ajgringo619]

Try reinstalling the Guest Additions on the VM.

I tried...no dice. Does anyone know where/how VirtualBox handles the mounting? I’ve seen mention of adding it to /etc/profile but I’d rather put it where VirtualBox does if possible.

Since your mount command worked you could always add it to /etc/fstab.

[smurphos]

Are you a member of vboxusers on the host following the upgrade?

What does dpkg -l | grep virtualbox return run from the host?

[MintForTom]

Dear All,

I want to confirm the existing issue. Also on my system which was running very well with version 18.3 I cannot see the shared folders.
They are available in /media/sf... bot not mounted.
I'm using the newest release of the VB and also the newest release of the guest additions.
I reinstalled the guest additions. After the reinstallation the folders are temporary shown. After a reboot the folders are gone again.
dpkg -l | grep virtualbox shows the following lines:
rc virtualbox-guest-utils 5.0.40-dfsg-0ubuntu1.16.04.1 amd64 x86 virtualization solution - non-X11 guest utilities
rc virtualbox-guest-x11 5.0.40-dfsg-0ubuntu1.16.04.1 amd64 x86 virtualization solution - X11 guest utilities

Here the dmesg log. Maybe here is the hint to find a solution:
dmesg

[ 0.004000] ACPI: 2 ACPI AML tables successfully acquired and loaded
[ 0.295438] pci 0000:00:00.0: Limiting direct PCI/PCI transfers
[ 5.402152] vboxguest: loading out-of-tree module taints kernel.
[ 5.402301] vboxguest: module verification failed: signature and/or required key missing - tainting kernel
[ 5.422117] vboxguest: misc device minor 55, IRQ 20, I/O port d020, MMIO at 00000000f0400000 (size 0x400000)
[ 5.422119] vboxguest: Successfully loaded version 5.2.16 (interface 0x00010004)
[ 5.576006] fbcon: vboxdrmfb (fb0) is primary device
[ 5.597487] vboxvideo 0000:00:02.0: fb0: vboxdrmfb frame buffer device
[ 5.624742] [drm] Initialized vboxvideo 1.0.0 20130823 for 0000:00:02.0 on minor 0
[ 6.971932] vboxsf: Successfully loaded version 5.2.16 (interface 0x00010004)
[ 378.293882] sf_read_super_aux err=-71
[ 378.294063] sf_read_super_aux err=-71
[ 408.847335] sf_read_super_aux err=-71
[ 408.847457] sf_read_super_aux err=-71
[ 1867.447211] sf_read_super_aux err=-71
[ 1867.447394] sf_read_super_aux err=-71
[ 2121.071107] 00:00:00.010492 automount vbsvcAutoMountWorker: Shared folder 'Share' was mounted to '/media/sf_Share'

The lines starting with 1867.447211 are created after a reinstallation of the VB.

Thanks for any help.

[smurphos]

I'm using the newest release of the VB and also the newest release of the guest additions.

Can you clarify - Host OS version, Host Vbox version, Guest OS version.

Where did you run dpkg -l | grep virtualbox? In the guest or the host?

[MintForTom]

Sorry for the incomplete information:
Host: Windows10 (Virtualbox Version 5.2.16 r123759 (Qt5.6.2), Guest: Mint 19
I called dpkg -l | grep virtualbox in the VB.

Finally I want to have the data of the virtual machine running Mint 19 in my host (Win10).

[Seadreamer]

I'm sorry, I just assumed you were running VB on Linux with some other OS as guest. Your question may be better answered in a Windows forum. In any case, good luck with it.

[rockadile]

Not sure how this would be a Windows issue since the simple act of upgrading Linux Mint caused this functionality to stop working.

[Seadreamer]

I don't know but I expect that almost all the responses you have gotten has been from people who use Linux as host and Windows as guest. I don't even know how to install VB in Windows much less how to make it work like you need it to. There are some really smart people on this forum and I am sure one of them can answer your question if they know what all the parameters are. As I said, good luck with it.

[smurphos]

dpkg -l | grep virtualbox shows the following lines:
rc virtualbox-guest-utils 5.0.40-dfsg-0ubuntu1.16.04.1 amd64 x86 virtualization solution - non-X11 guest utilities
rc virtualbox-guest-x11 5.0.40-dfsg-0ubuntu1.16.04.1 amd64 x86 virtualization solution - X11 guest utilities

Sorry for the incomplete information:
Host: Windows10 (Virtualbox Version 5.2.16 r123759 (Qt5.6.2), Guest: Mint 19
I called dpkg -l | grep virtualbox in the VB.

Thanks. Those packages are the mint 18.3 packaged guest utils for a version 5.0.40 host and shouldn't be on the syste,/

In the guest run the following in the terminal...

apt purge virtualbox*
apt install build-essentials

Then open VBox's devices menu from within the guest and chose the option 'Insert Guest Additions CD Image''. Follow the prompts to run the installer.

Finally in the guest run

sudo adduser $USER vboxsf

and reboot the guest.

That will hopefully do the trick.

[rockadile]

dpkg -l | grep virtualbox shows the following lines:
rc virtualbox-guest-utils 5.0.40-dfsg-0ubuntu1.16.04.1 amd64 x86 virtualization solution - non-X11 guest utilities
rc virtualbox-guest-x11 5.0.40-dfsg-0ubuntu1.16.04.1 amd64 x86 virtualization solution - X11 guest utilities

Sorry for the incomplete information:
Host: Windows10 (Virtualbox Version 5.2.16 r123759 (Qt5.6.2), Guest: Mint 19
I called dpkg -l | grep virtualbox in the VB.

Thanks. Those packages are the mint 18.3 packaged guest utils for a version 5.0.40 host and shouldn't be on the syste,/

In the guest run the following in the terminal...

apt purge virtualbox*
apt install build-essentials

Then open VBox's devices menu from within the guest and chose the option 'Insert Guest Additions CD Image''. Follow the prompts to run the installer.

Finally in the guest run

sudo adduser $USER vboxsf

and reboot the guest.

That will hopefully do the trick.

Where does build-essentials come from? Apt can't find it.