mount.nfs: Protocol not supported

[Jerry Steele]

Hello,

I'm new to this wonderful firmware, I was previously able to mount NFS shares from my nasbox on the new firmware, but now this is not working for some reason.

When I try to manually mount an NFS share which is available on the box, I get:

# mount -t nfs nasbox:/mnt/md127 /mnt -vv
mount.nfs: timeout set for Fri Apr 24 23:32:31 2015
mount.nfs: trying text-based options 'vers=4.2,addr=192.168.1.12,clientaddr=192.168.1.14'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'vers=4.1,addr=192.168.1.12,clientaddr=192.168.1.14'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'vers=4.0,addr=192.168.1.12,clientaddr=192.168.1.14'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'addr=192.168.1.12'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: trying 192.168.1.12 prog 100003 vers 3 prot TCP port 2049
mount.nfs: prog 100005, trying vers=3, prot=17
mount.nfs: trying 192.168.1.12 prog 100005 vers 3 prot UDP port 51981
mount.nfs: mount(2): Protocol not supported
mount.nfs: Protocol not supported

The export looks like this:

# cat /etc/exports
/mnt/md127 192.168.1.0/24(rw,sync)

From Googling this, it looks like it might be something to do with the server attempting to offer v4, and not being able to, but I can't see anywhere to set that in the Alt-F environment.

The system log has this, but I don't know if that's a red herring:

Apr 24 23:10:15 dns325 daemon.notice rpc.mountd[1349]: Version 1.2.9 starting
Apr 24 23:10:15 dns325 daemon.notice rpc.statd[1356]: Version 1.2.9 starting
Apr 24 23:10:15 dns325 daemon.warn rpc.statd[1356]: Flags:
Apr 24 23:10:15 dns325 daemon.err rpc.nfsd[1362]: Setting version failed: errno 22 (Invalid argument)
Apr 24 23:10:15 dns325 daemon.notice sm-notify[1375]: Version 1.2.9 starting

Can anyone help? It's very frustrating, as it was working before (!)

EDIT: almost forgot to mention, hardware is DNS-320, firmware is: Alt-F 0.1RC4.1 with kernel 3.10.32

[João Cardoso]

On Friday, April 24, 2015 at 11:40:32 PM UTC+1, Jerry Steele wrote:

Hello,

I'm new to this wonderful firmware, I was previously able to mount NFS shares from my nasbox on the new firmware, but now this is not working for some reason.

When I try to manually mount an NFS share which is available on the box, I get:

# mount -t nfs nasbox:/mnt/md127 /mnt -vv
mount.nfs: timeout set for Fri Apr 24 23:32:31 2015
mount.nfs: trying text-based options 'vers=4.2,addr=192.168.1.12,clientaddr=192.168.1.14'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'vers=4.1,addr=192.168.1.12,clientaddr=192.168.1.14'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'vers=4.0,addr=192.168.1.12,clientaddr=192.168.1.14'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'addr=192.168.1.12'
mount.nfs: prog 100003, trying vers=3, prot=6

mount.nfs: trying 192.168.1.12 prog 100003 vers 3 prot TCP port 2049
mount.nfs: prog 100005, trying vers=3, prot=17

this should work. Alt-F uses NFS-v3:

silver:~ # mount -t nfs -vv dns-320l:/mnt/md1 /tmp

mount.nfs: timeout set for Sat Apr 25 15:25:51 2015

mount.nfs: trying text-based options 'vers=4,addr=192.168.1.83,clientaddr=192.168.1.1'

mount.nfs: mount(2): Protocol not supported

mount.nfs: trying text-based options 'addr=192.168.1.83'

mount.nfs: prog 100003, trying vers=3, prot=6

mount.nfs: trying 192.168.1.83 prog 100003 vers 3 prot TCP port 2049

mount.nfs: prog 100005, trying vers=3, prot=17

mount.nfs: trying 192.168.1.83 prog 100005 vers 3 prot UDP port 47449

Is the box nfs server (and all its components) started? Portmap? 'rcnfs start|stop|status|enable|disable|...' does all that is needed.

[Jerry Steele]

Thanks for your response,

In the end, a reboot of the client machines fixed this. I guess it must have been one of the rpc* services on them not started or working properly (I'm still finding my way round systemd's way of doing things). The error could be more descriptive, but that's the fault of NFS itself, not the firmware..

--
You received this message because you are subscribed to a topic in the Google Groups "Alt-F" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/alt-f/nEX-0UJWgcY/unsubscribe.
To unsubscribe from this group and all its topics, send an email to alt-f+un...@googlegroups.com.
Visit this group at http://groups.google.com/group/alt-f.
For more options, visit https://groups.google.com/d/optout.

--

---

Jerry Steele
Telephone: +44 (0)7920 237105
http://www.ticktockhouse.co.uk