[pewpew1]

I cannot get my NFS share to work, with the Frodo version.
I have updated one of my ATVs to the newest IOS and newest Frodo version (offical release), but I get the following error (MNT3ERR_ACCES(13) Permission denied(13)")). See below for more debug information. The other ATV with is Eden (and an older IOS) has a working NFS share.
But for clarity I will explain how my setup is:
I have a synology and it is setup by following the wiki
NFS guide. I changed the ip white listing though, see below. The IP on the atv is 192.168.1.245 and validates against the white listing.

The error looks like I did not setup my config correctly, but the other ATV works, so the setup must be correct. On the ATV with Frodo, I can use SMB without problems, so my networks works.

I have searched the forum and people who had the "13" error had setup their nas incorrect, but I do not believe that it is my case.

I do not know much about NFS (and linux), but isn't there something about user id. Maybe the mobile user on the ATV has changed so it is not 501. Can I log on the ATV a try to manually mount to my nas the same way XBMC does (if so, how) and get a better debug message?

Code:

/volume1/multimedie     192.168.1.*(rw,async,no_wdelay,no_root_squash,insecure,anonuid=0,anongid=0)
/volume1/music  192.168.1.*(rw,async,no_wdelay,no_root_squash,insecure,anonuid=0,anongid=0)

Code:

09:11:16 T:98926592   DEBUG:   ParentPath = [sources://video/]
09:11:16 T:111017984   DEBUG: SECTION:LoadDLL(libnfs.1.dylib)
09:11:16 T:111017984   DEBUG: Loading: /var/stash/Applications/XBMC.frappliance/Frameworks/libnfs.1.dylib
09:11:16 T:111017984   DEBUG: NFS: Context for 192.168.1.101 not open - get a new context.
09:11:16 T:111017984   ERROR: NFS: Failed to mount nfs share:  (mount/mnt call failed with "RPC error: Mount failed with error MNT3ERR_ACCES(13) Permission denied(13)")
09:11:16 T:132272128   DEBUG: NFS: Context for 192.168.1.101/volume1/music not open - get a new context.
09:11:16 T:132272128   ERROR: NFS: Failed to mount nfs share: /volume1/music (mount/mnt call failed with "RPC error: Mount failed with error MNT3ERR_ACCES(13) Permission denied(13)")
09:11:16 T:132272128   DEBUG: NFS: Refreshing context for 192.168.1.101/volume1/music, old: 3644553, new: 3644626
09:11:16 T:132272128   DEBUG: NFS: Using cached context.
09:11:17 T:132272128   DEBUG: NFS: Context for 192.168.1.101/volume1/multimedie not open - get a new context.
09:11:17 T:132272128   ERROR: NFS: Failed to mount nfs share: /volume1/multimedie (mount/mnt call failed with "RPC error: Mount failed with error MNT3ERR_ACCES(13) Permission denied(13)")
09:11:17 T:132272128   DEBUG: NFS: Refreshing context for 192.168.1.101/volume1/multimedie, old: 3644740, new: 3644843
09:11:17 T:132272128   DEBUG: NFS: Using cached context.
09:11:38 T:98926592   DEBUG: SECTION:UnloadDelayed(DLL: special://xbmcbin/system                                                                                        /ImageLib-arm-osx.so)
09:11:38 T:98926592   DEBUG: Unloading: ImageLib-arm-osx.so
09:12:51 T:98926592  NOTICE: NFS is idle. Closing the remaining connections.

[Memphiz]

Yes its your nas setup. Try restarting the nfs service or the whole nas. Look like it doesn't accept the ip whitelist.

[Memphiz]

ohh and the way you have set it up all accesses are done with uid0 (root user). So you also have to verify that all subdirs and files in your exported folder are owned by root.

[pewpew1]

It works now, but it was not solved by restarting the nfs service.

I rebooted my nas and still got the problem ("old" Eden worked and the "new" Frodo did not).
So I though it can be network/WIFI related, because my "old" atv had a static IP, so I changed the IP settings on the "new" frodo (which had a "clean and new" IOS) from Automatic to static (same ip as in my first post, only diff. it is static set). And then the NFS share worked.

My old Synology nfs config (/etc/exports) file did not have the "*", but absolute ip adresses 192.168.1.103 and 192.168.1.104, so at first I thought maybe my synology did not "pick up" the newer config file. But I cannot see it is the case, because the static ip adresse on the new "frodo" is 192.168.1.245.

Well, in short, it works now. Maybe I will test my setup later (Router, NAS and ATVs).