
I'll try fixing manually again.
Code: Select all
root@DietPi:~# mount -t nfs -o port=2049 192.168.0.11:/volume1/video /mnt/nfs
mount.nfs: mount point /mnt/nfs does not exist
root@DietPi:~# sudo mkdir -p /mnt/nfs
root@DietPi:~# mount -t nfs -o port=2049 192.168.0.11:/volume1/video /mnt/nfs
mount.nfs: Protocol not supported
root@DietPi:~#
Code: Select all
192.168.1.10:/mnt/user/music_test /mnt/nas/music_test nfs auto,nofail 0 0
Code: Select all
root@DietPi:/mnt# mount -v /mnt/nas/music_test
mount.nfs: timeout set for Sun Jul 8 10:58:35 2018
mount.nfs: trying text-based options 'vers=4.2,addr=192.168.1.10,clientaddr=192.168.1.9'
mount.nfs: mount(2): Invalid argument
mount.nfs: trying text-based options 'vers=4.1,addr=192.168.1.10,clientaddr=192.168.1.9'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'vers=4.0,addr=192.168.1.10,clientaddr=192.168.1.9'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'addr=192.168.1.10'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: trying 192.168.1.10 prog 100003 vers 3 prot TCP port 2049
mount.nfs: prog 100005, trying vers=3, prot=17
mount.nfs: trying 192.168.1.10 prog 100005 vers 3 prot UDP port 33776
mount.nfs: Protocol not supported
root@DietPi:/mnt#
Code: Select all
root@DietPi:/mnt# mount -t nfs -o vers=3 -v 192.168.1.10:/mnt/user/music_test /mnt/test/
mount.nfs: timeout set for Sun Jul 8 10:59:56 2018
mount.nfs: trying text-based options 'vers=3,addr=192.168.1.10'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: trying 192.168.1.10 prog 100003 vers 3 prot TCP port 2049
mount.nfs: prog 100005, trying vers=3, prot=17
mount.nfs: trying 192.168.1.10 prog 100005 vers 3 prot UDP port 33776
mount.nfs: Protocol not supported
root@DietPi:/mnt#
Hi MichaIng, I think you've captured it well on git.MichaIng wrote: ↑Thu Jul 05, 2018 6:19 pm @Quizzer
So finally it showed "protocol unsupported" messages when using mount -t nfs4 as well as with mount -t nfs?
And when enabling nfs4 support on NAS, both commands work?
I opened an issue about this on GitHub, feel free to join there as well, maybe we get this fixed for v6.11 hotfix update: https://github.com/Fourdee/DietPi/issues/1898