A Blog Of Random Coding Techniques & Experiments Robert Askam

Vagrant was unable to mount VirtualBox shared folders. This is usually because the filesystem "vboxsf" is not available Post Vagrant was unable to mount VirtualBox shared folders. This is usually because the filesystem "vboxsf" is not available 1 year ago

Issue

When I started Vagrant for the first time I received this error.
vagrant up
...
...
...
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 actimeo=1,nolock,uid=1000,gid=1000 home_vagrant_Code /home/vagrant/Code

The error output from the command was:

unknown mount option `actimeo=1'
valid options:
rw mount read write (default)
ro mount read only
uid = default file owner user id
gid = default file owner group id
ttl = time to live for dentry
iocharset = i/o charset (default utf8)
convertcp = convert share name from given charset to utf8
dmode = mode of all directories
fmode = mode of all regular files
umask = umask of directories and regular files
dmask = umask of directories
fmask = umask of regular files

Fix

Run
vagrant destroy --force
vagrant up
vagrant plugin update vagrant-vbguest
vagrant up