NFS Access/Mount

[Quizzer]

Found the new options. But defaults to nsf4. So gives this error:



I'll try fixing manually again.

[Quizzer]

No luck trying to run the command manually.

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:~#

[Quizzer]

Ok fixed it. Enabled NFSv4 support on my Synology (not sure what the repercussions are). All existing NFS access remains fine though and now the new dietpi-drive_manager wizard successfully mounts as expected. Can browse to /mnt/nfs/ and see my shares.

Installed Emby and all appears to be well.

Post wizard success message:

dietpi-drive_manager screen once mounted:

[MichaIng]

@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

[dunc]

Hi guys, I'm seeing a similar issue since updating from 6.9 to 6.11

I have some NFSv3 shares on another server that mounted fine on 6.9 and earlier, and now fail to mount since updating from 6.9 to 6.11.

The original fstab entry was:

Code: Select all

192.168.1.10:/mnt/user/music_test    /mnt/nas/music_test nfs               auto,nofail          0 0

Trying to mount that mount point manually:

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#

Trying a test mount explicitly specifying nfs3 also fails:

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#

The server in this case is an unRAID based on Slackware, which only supports NFSv3, so I can't enable v4 per @Quizzer's fix.

[Quizzer]

@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

Hi MichaIng, I think you've captured it well on git.

- The new dietpi-drive_manager woks fine with NFSv4.
- The new dietpi-drive_manager fails with older versions of NFS as experienced by myself and @dunc.

If you need me to test anything else let me know.