# 'Vagrant up' hangs at "Mounting NFS shared folders..." **URL:** https://discourse.roots.io/t/vagrant-up-hangs-at-mounting-nfs-shared-folders/5133 **Category:** trellis **Created:** 2015-10-27T05:22:30Z **Posts:** 14 ## Post 1 by @Craig — 2015-10-27T05:22:30Z Yesterday I did ‘vagrant up’ on an old project after having not run a vagrant VM for a month or so. It hung at: Mounting NFS shared folders… After updating Virtualbox, Guest Additions, Vagrant, Vagrant plugins, and the ‘box’ the only way I could fix this was to modify the line below in the VagrantFile: from: > config.vm.synced\_folder local\_site\_path(site), nfs\_path(name), type: ‘nfs’ to: > config.vm.synced\_folder local\_site\_path(site), nfs\_path(name), type: ‘nfs’, nfs\_udp: false The only thing that I think had changed since I last ran a vagrant VM is OS (Ubuntu) updates. So without having investigated any further I am assuming that that is the cause for now. However it would be good to know if anyone else had seen this issue? And maybe they had even investigated the exact cause. Maybe this is even related to [VirtualBox performance in windows - #13 by Grant\_Derepas](https://discourse.roots.io/t/virtualbox-performance-in-windows/3932/13) however that thread is discussing Windows so it seems unlikely. EDIT: Just to clarify, my control machine (host) is Ubuntu 14.04 LTS --- ## Post 2 by @jom — 2015-10-27T18:10:27Z My host machine is windows 8.1 64bit and I started experiencing the same problem yesterday. I cloned each repo and only changed one line in the Vagrantfile as per this post : [Deploying from windows](https://discourse.roots.io/t/deploying-from-windows/4434/5) The vagrant-winnfsd also stays running sometimes after a vagrant halt. I’m not entirely sure what I did that fixed it. I destroyed the vagrant boxes, cleared them out using the virtualbox GUI, and rebooted. Then reinstalled and voila. --- ## Post 3 by @madonion — 2015-10-29T20:25:54Z I also have the same problem, same host (ubuntu 14.4) and I can confirm Craig’s solution works for me too. Thanks. --- ## Post 4 by @Craig — 2015-10-30T03:59:19Z Thanks for the info it makes me think that this is guest side as the VM was unchanged. Looking at your link my guess is you are using UDP as I think that is the default NFS protocol and I don’t think that you have specified otherwise? So I think that these two issues may be unrelated based on the fact that the host side seems to have Ubuntu host using TCP while (I think), the Windows host is using UDP?? --- ## Post 5 by @treb0r — 2015-10-30T15:10:21Z Have a look at the comments on [here](https://github.com/mitchellh/vagrant/issues/6423#issuecomment-150653307) --- ## Post 6 by @jom — 2015-10-30T20:36:59Z I have only changed that single line in the Vagrantfile, so your guess would be correct. All other settings are default. --- ## Post 7 by @richardwilis — 2015-11-05T09:30:25Z I can confirm a dist-upgrade to kernel 3.16.0-52 fixed it for me. --- ## Post 8 by @Craig — 2015-11-09T22:20:28Z Thanks for that, wish I found it myself it would have saved me a headache (obviously need to work on my Google skills :frowning: ) I forgot to post it originally however my output with VAGRANT\_LOG set to ‘info’ was similar I believe. --- ## Post 9 by @bwade231 — 2016-07-20T03:17:10Z Also anyone else that still has this issue, running the following worked for me: sudo ifconfig vboxnet1 down sudo ifconfig vboxnet1 up This essentially restarts the virtualbox network. --- ## Post 10 by @johnrlive — 2018-08-19T19:51:40Z If you are on a mac make sure your hard drive is not encrypted. $ sudo fdesetup status If enabled, it will read ‘FileVault is On’. To disable FileVault type in terminal. $ sudo fdesetup disable --- ## Post 11 by @thommeredith — 2018-10-16T00:11:23Z I am also getting this out of the blue, I just updated Mac OS to 10.13.6 not sure if this is the culprit. I did run the notes above but this did not change anything `$ sudo fdesetup status` `$ sudo fdesetup disable` --- ## Post 12 by @ben — 2018-10-16T00:31:45Z > [@thommeredith](#): > > I just updated Mac OS to 10.13.6 What’s your exact error? Did you encrypt your filesystem? See [NFS - Synced Folders | Vagrant | HashiCorp Developer](https://www.vagrantup.com/docs/synced-folders/nfs.html#other-notes) /via [https://roots.io/trellis/docs/local-development-setup/](https://roots.io/trellis/docs/local-development-setup/) --- ## Post 13 by @thommeredith — 2018-10-16T02:59:18Z I restarted my computer and all is well again. When in doubt, restart! --- ## Post 14 by @chancestrickland — 2019-07-11T15:00:54Z If you are on MacOS, make sure your terminal app has full disk access. See comment here: [https://github.com/hashicorp/vagrant/issues/10234#issuecomment-424305964](https://github.com/hashicorp/vagrant/issues/10234#issuecomment-424305964)