NFS Access/Mount

Have some feedback, questions, suggestions, or just fancy a chat? Pop it in here.
Quizzer
Posts: 16
Joined: Tue Jul 03, 2018 12:15 am

Re: NFS Access/Mount

Post by Quizzer » Wed Jul 04, 2018 7:02 pm

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

Image

I'll try fixing manually again.

Quizzer
Posts: 16
Joined: Tue Jul 03, 2018 12:15 am

Re: NFS Access/Mount

Post by Quizzer » Wed Jul 04, 2018 7:28 pm

No luck trying to run the command manually.

Code: Select all

[email protected]:~# mount -t nfs -o port=2049 192.168.0.11:/volume1/video /mnt/nfs
mount.nfs: mount point /mnt/nfs does not exist
[email protected]:~# sudo mkdir -p /mnt/nfs
[email protected]:~# mount -t nfs -o port=2049 192.168.0.11:/volume1/video /mnt/nfs
mount.nfs: Protocol not supported
[email protected]:~#

Quizzer
Posts: 16
Joined: Tue Jul 03, 2018 12:15 am

Re: NFS Access/Mount

Post by Quizzer » Wed Jul 04, 2018 9:27 pm

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:
Image
dietpi-drive_manager screen once mounted:
Image

User avatar
MichaIng
Legend
Posts: 542
Joined: Sat Nov 18, 2017 5:21 pm

Re: NFS Access/Mount

Post by MichaIng » Thu Jul 05, 2018 5: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

dunc
Posts: 1
Joined: Sat Jul 07, 2018 11:49 pm

Re: NFS Access/Mount

Post by dunc » Sun Jul 08, 2018 12:01 am

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

[email protected]:/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
[email protected]:/mnt#
Trying a test mount explicitly specifying nfs3 also fails:

Code: Select all

[email protected]:/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
[email protected]:/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
Posts: 16
Joined: Tue Jul 03, 2018 12:15 am

Re: NFS Access/Mount

Post by Quizzer » Tue Jul 10, 2018 2:11 pm

MichaIng wrote:
Thu Jul 05, 2018 5: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
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.

Post Reply