Upgrade to 5.1.20 and shared folders stopped working
Posted: 26. Apr 2017, 02:30
Hi, I upgraded to virtualbox version 5.1.20 (as nvme requires 5.1.20) and shared folders stopped working. Please note that guest additions inside guest was upgraded fine and output shows so as well. I even tried with "vagrant plugin install vagrant-vbguest" but no change. I manually tried the mount command in the vm but got same error. I have also added the dmesg error below. Appreciate any pointers.
Thanks
========="vagrant up" output from host =============
default: SSH username: ubuntu
default: SSH auth method: password
==> default: Machine booted and ready!
[default] GuestAdditions 5.1.20 running --- OK.
==> default: Checking for guest additions in VM...
==> default: Mounting shared folders...
default: /vagrant => <host_folder_path>
Vagrant was unable to mount VirtualBox shared folders. This is usually
because the filesystem "vboxsf" is not available. This filesystem is
made available via the VirtualBox Guest Additions and kernel module.
Please verify that these guest additions are properly installed in the
guest. This is not a bug in Vagrant and is usually caused by a faulty
Vagrant box. For context, the command attempted was:
mount -t vboxsf -o uid=1000,gid=1000 vagrant /vagrant
The error output from the command was:
mount: wrong fs type, bad option, bad superblock on vagrant,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so.
========== "dmesg | tail" output from guest ============
[ 56.555981] 00:00:00.000155 main OS Product: Linux
[ 56.555997] 00:00:00.000175 main OS Release: 4.4.0-75-generic
[ 56.556012] 00:00:00.000191 main OS Version: #96-Ubuntu SMP Thu Apr 20 09:56:33 UTC 2017
[ 56.556032] 00:00:00.000206 main Executable: /opt/VBoxGuestAdditions-5.1.20/sbin/VBoxService
00:00:00.000206 main Process ID: 1193
00:00:00.000207 main Package type: LINUX_64BITS_GENERIC
[ 56.556529] 00:00:00.000701 main 5.1.20 r114628 started. Verbose level = 0
[ 59.753434] sf_read_super_aux err=-22
[ 64.779064] sf_read_super_aux err=-22
[ 69.807138] sf_read_super_aux err=-22
Thanks
========="vagrant up" output from host =============
default: SSH username: ubuntu
default: SSH auth method: password
==> default: Machine booted and ready!
[default] GuestAdditions 5.1.20 running --- OK.
==> default: Checking for guest additions in VM...
==> default: Mounting shared folders...
default: /vagrant => <host_folder_path>
Vagrant was unable to mount VirtualBox shared folders. This is usually
because the filesystem "vboxsf" is not available. This filesystem is
made available via the VirtualBox Guest Additions and kernel module.
Please verify that these guest additions are properly installed in the
guest. This is not a bug in Vagrant and is usually caused by a faulty
Vagrant box. For context, the command attempted was:
mount -t vboxsf -o uid=1000,gid=1000 vagrant /vagrant
The error output from the command was:
mount: wrong fs type, bad option, bad superblock on vagrant,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so.
========== "dmesg | tail" output from guest ============
[ 56.555981] 00:00:00.000155 main OS Product: Linux
[ 56.555997] 00:00:00.000175 main OS Release: 4.4.0-75-generic
[ 56.556012] 00:00:00.000191 main OS Version: #96-Ubuntu SMP Thu Apr 20 09:56:33 UTC 2017
[ 56.556032] 00:00:00.000206 main Executable: /opt/VBoxGuestAdditions-5.1.20/sbin/VBoxService
00:00:00.000206 main Process ID: 1193
00:00:00.000207 main Package type: LINUX_64BITS_GENERIC
[ 56.556529] 00:00:00.000701 main 5.1.20 r114628 started. Verbose level = 0
[ 59.753434] sf_read_super_aux err=-22
[ 64.779064] sf_read_super_aux err=-22
[ 69.807138] sf_read_super_aux err=-22