Homestead: mount.nfs: requested NFS version or transport protocol is not supported

Created on 27 Dec 2017  Â·  12Comments  Â·  Source: laravel/homestead

Versions

  • Vagrant: 2.0.1
  • Provider: Virtualbox 5.2.4 r119758
  • Homestead: 7.0.1

Host operating system

Antergos

Homestead.yaml

---
ip: "192.168.10.10"
memory: 2048
cpus: 1
provider: virtualbox

authorize: ~/.ssh/id_rsa.pub

keys:
    - ~/.ssh/id_rsa

folders:
    - map: ~/PhpstormProjects
      to: /home/vagrant/proj
      type: nfs

sites:
    - map: app.dev
      to: /home/vagrant/proj/app/public

databases:
    - app

# blackfire:
#     - id: foo
#       token: bar
#       client-id: foo
#       client-token: bar

# ports:
#     - send: 50000
#       to: 5000
#     - send: 7777
#       to: 777
#       protocol: udp

Vagrant destroy & up output

https://gist.github.com/Cysioland/c1a012c11175aab3c5984c826b540ce7

Expected behavior

Machine gets brought up with no issues

Actual behavior

NFS folders can't be mounted, message in title

Steps to reproduce

  1. Use fully updated Antergos or Arch
  2. vagrant up your Homestead machine with NFS shared folders
  3. Error happens

Most helpful comment

@Cysioland @domagoj03 Thanks, I was missing

[nfsd]
udp=y

from my /etc/nfs.conf

All 12 comments

Do you get the same error when mapping one project folder instead of the larger folder?

Sounds like this may be NFS on your host. Does non-nfs folder sharing work?

--

  • Joe Ferguson
    JoeFerguson.me
    MemphisPHP.org

On Dec 27, 2017, 06:16 -0600, Cysioland notifications@github.com, wrote:

Versions

• Vagrant: 2.0.1
• Provider: Virtualbox 5.2.4 r119758
• Homestead: 7.0.1

Host operating system
Antergos

Homestead.yaml

ip: "192.168.10.10"
memory: 2048
cpus: 1
provider: virtualbox

authorize: ~/.ssh/id_rsa.pub

keys:

  • ~/.ssh/id_rsa

folders:

  • map: ~/PhpstormProjects
    to: /home/vagrant/proj
    type: nfs

sites:

  • map: app.dev
    to: /home/vagrant/proj/app/public

databases:

  • app

blackfire:

- id: foo

token: bar

client-id: foo

client-token: bar

ports:

- send: 50000

to: 5000

- send: 7777

to: 777

protocol: udp

Vagrant destroy & up output
https://gist.github.com/Cysioland/c1a012c11175aab3c5984c826b540ce7
Expected behavior
Machine gets brought up with no issues
Actual behavior
NFS folders can't be mounted, message in title
Steps to reproduce

  1. Use fully updated Antergos or Arch
  2. vagrant up your Homestead machine with NFS shared folders
  3. Error happens

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Mapping a smaller folder with NFS still fails.

Non-NFS map works fine

Okay, issue was entirely host-wise, leaving this for other people: had to reboot to the newest kernel, then run depmod as root, then reboot again.

Another reason may be, that NFS over UDP is disabled on the host-side

Exactly the same issue on Manjaro 414. I suspected it's due to encryption of home folders but after reinstalling OS, the issue remains.

requested NFS version or transport protocol is not supported

Any luck solving this @Cysioland ?

@domagoj03 Managed to solve this problem? Facing the same issue with Antergos 4.14.15-1-ARCH.

@domagoj03 @Jesuqq Make sure that NFS over UDP is turned on, some updates like to turn that off. Also, make sure that NFS kernel modules are in, if they ain't, then reboot and run depmod as root, and reboot again.

@Cysioland @domagoj03 Thanks, I was missing

[nfsd]
udp=y

from my /etc/nfs.conf

Yeah, I've solved it, however I can't really remember what fixed it specifically. I was following several arch wiki articles - vagrant, nfs, etc.
I think that part of my fix was the installation of net-tools. I can't really remember the flow right now, but the solution is available in Arch wiki.

For reference: clearing the (machine) NFS entries in /etc/exports fixed this issue for me after upgrading to macOS Mojave and/or vagrant 2.1.5.

try to check the status of nfs service
➜ macOS ✗ cat /etc/exports
➜ macOS ✗ sudo nfsd enable
The nfsd service is already enabled.
➜ macOS ✗ sudo nfsd start
The nfsd service is already running.
➜ macOS ✗ nfsd status
nfsd service is enabled
nfsd is running (pid 98008, 8 threads)

Can confirm that there were double generated entries in my /etc/exports. After removing them, and restarting the nfs server, I was able to stand up Homestead.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

alexdover picture alexdover  Â·  4Comments

pqt picture pqt  Â·  3Comments

Modelizer picture Modelizer  Â·  5Comments

teleclimber picture teleclimber  Â·  3Comments

mtpultz picture mtpultz  Â·  4Comments