Errors mounting NFS Synology 923+

[whomhead]

Hey all,

Here's the error I'm receiving trying to mount my NAS folder in Moode. Just moving over to Moode from Volumio, this did work in Volumio.

20250111 175026 worker: Try (mount -t nfs -o soft,timeo=10,retrans=1,ro,nolock "volume1:/Plex Media" "/mnt/NAS/PlexMusic")

20250111 175026 worker: Err (mount.nfs: Failed to resolve server volume1: Name or service not known)

Thanks for the help!

Andy

[Tim Curtis]

Did you use SCAN on the "Remote NAS Source" screen to find the NAS share or did you enter it manually via the "EDIT Path manually" option?

ETA: Are you sure its an NFS export and not an SMB share?

[whomhead]

I have tried both entering it manually and via scanning, this is the error I got by scanning -

20250111 191943 worker: Try (mount -t nfs -o soft,timeo=10,retrans=1,ro,nolock "192.168.184.236:/volume1/Plex" "/mnt/NAS/PlexMusic")
20250111 191943 worker: Err (mount.nfs: access denied by server while mounting 192.168.184.236:/volume1/Plex)

Yes, I do have NFS configured properly (I believe) in my Synology NAS. As stated, this did work with Volumio, so I believe it's configured properly.

[TheOldPresbyope]

@whomhead 

From your first post

Code:

20250111 175026 worker: Try (mount -t nfs -o soft,timeo=10,retrans=1,ro,nolock "volume1:/Plex Media" "/mnt/NAS/PlexMusic")

This command is looking for a host named "volume1". That was doomed to fail.

As well, it says your music directory name is "Plex Music", which contains white space.

Now, in your post #3, we see the mount command used what was, I assume, the correct host IP, but the incorrect directory name "Plex".

Code:

20250111 191943 worker: Try (mount -t nfs -o soft,timeo=10,retrans=1,ro,nolock "192.168.184.236:/volume1/Plex" "/mnt/NAS/PlexMusic")

This suggests that the white space in the directory name is causing a problem in Tim's code.

As a counterexample, I run a (virtual) Synology host for test purposes. It exports both SMB and NFS shares and all of them are easily mounted in my moOde players. However, none of the sharenames contains white space.

Regards,
Kent

ETA - I've been a bit loose in directory names. The full directory path on your server is, of course, "/volume1/Plex Music" but I elided the "/volume1/" in my answer for clarity.

[whomhead]

OK...I was able to get this to work by creating a test folder on the NAS named "music". The path that finally worked was

xxx.xxx.xxx.xxx/volume1/music

Just a suggestion for the documentation for this software, it would be helpful to have a "connect NAS shares to MoOde for dummies" in the documentation. I was not aware that white space (spaces?) would cause any issues here. Had I known that I would have addressed it going into the setup process.

Now, to play around. Thanks for the help.

[Tim Curtis]

Prolly not a bad idea. If someone writes up a document I'll go ahead and edit/publish it in MD format.

[TheOldPresbyope]

@whomhead 

Guides are always welcome.

As an aside on your directory naming issue, this sort of thing recurs again and again in software written by human beings. The last bugs are uncovered by users (of which there are many) rather than devs (of which there are usually only a few).

The only illegal printable character in a a Linux/Unix file or directory name is the forward slash. (A space is considered a printable character). 

Unfortunately, many scripting languages and programming languages such as Python will split strings on spaces into separate tokens. You'll often see scripts, in particular, with an abundance of quotation marks to try to avoid this (and note that there is a semantic difference between a single quote mark (e.g., apostrophe) and a double quote mark in bash, for example).

You'll also see that many seasoned Linux coders use hyphens, underscores or some sort of CamelCase in place of spaces in names. So, for example, Plex_Music or PlexMusic, might be used. It shouldn't be necessary but better safe than sorry  

Enjoy the music!

Regards,
Kent