I’m trying to mount an fstab based NFS share using this guide. I’m using a Synology DS411j NAS (DSM version: 6.2.3-25426 Update 2) and an RPi 3B+ with OSMC 2020.06-1. The NFS share on the Synology NAS (192.168.0.105:/volume1/TestShare) works fine - at least it can be seen (and browsed) from another RPi 3B+ with Kodi 17.1 installed through RetroPie, so I don’t expect the NAS to be the problem(?). Sharing via SMB works fine for both RPi’s.
Thanks fzinken, appreciate it. I guess you refer to the (Synology) NAS? Sorry for dumb questions, I’m not very experienced in this kind of set-up. Weird thing, that I’m able to access the NFS share without problems from the other RPi 3B+ with Kodi 17.1(?)
So. What have you specified in DSM (on the Synology) for NFS permissions for your target folder? I am wondering whether you have only specified the address of the working pi and have not included the new one
First of all, thanks for taking your time to reply.
I basically followed the guide here by Synology.
In the “File Services” I have enabled NFS (although not NFS 4.0/4.1).
In the “Shared Folders” I have the following NFS Permissions for the specific folder: Hostname or IP: * Privilege: Read/Write Squash: Map all users to admin
And I have selected:
Allow connections from non-privileged ports (ports higher than 1024)
Allow users to access sub-folders
Hope it makes sense.
EDIT: So to answer your question, I guess that I allowed all addresses using the asterisk (*).
Hi @bmillham, the other RPi does not work either - I was mistaken.
Also, that second RPi (which I thought was working, but it didn’t) was not set up using mounts. Its NFS was configured in Kodi directly instead. Hope it makes sense, otherwise let me know.
osmc@osmc:/$ sudo showmount -e 192.168.1.52
Export list for 192.168.1.52:
This is showing all the NFS enabled folders on my Synology and which devices can connect.
If I do this:
osmc@osmc:/mnt$ sudo showmount -e 192.168.1.53
clnt_create: RPC: Port mapper failure - Unable to receive: errno 113 (No route to host)
and that happens because there is no device at that address.
However if I do this:
osmc@osmc:/mnt$ sudo showmount -e 192.168.1.204
clnt_create: RPC: Program not registered
This address exists but it is not running an NFS server.
This is a long way round of saying that in your case, you are talking to a valid NFS server but the error 111 does actually mean that it is the server refusing the connection.
So we need to look at your Synology.
First. Is the firewall off?
No idea if this will help, here is the NFS set-up for my Synology video share. I only use Kodi-mounted NFS, never had issues requiring kernel mount. The “Map all users to guest” for the Squash setting only works for me because I have configured the guest account to have access to the video share. But previously I used Map all users/root to admin and that worked too.