Hello,
I have 2 Volumio devices, one Asus Tinkerware and one RBPi 3B+. Both were connecting to my music on Synology NAS via NFS (vers=3). I attempted to play files from it on Volumio on both systems. My library showed the music files but clicking on play on any file didn’t result on any action, not even error messages on the UI. I decided to delete the libraries and sources. Now the NFS shares appear as mounted, but no files are scanned into the library.
I have been streaming mostly from Qobuz, such that I cannot tell when this behavior started.
Here the log after attempting a re-scan: http://logs.volumio.org/volumio/xDNN4IF.html
Mounting with CIFS works and lets me scan and play files (on the Tinkerware, haven’t tried it on RBPi yet). However I rather continue to use NFS. Are there any additional setting to be made on the NAS side (mapping, cross-mount, etc)? Any help is very much appreciated.
Thanks, I’m trying it out now but I get the same behaviour… appears successfully mounted, but no action at all when re-scanning - empty library, no “in progress” rotating icon.
That’s not the problem, volume1/Public has to be there, the Synology NAS provides that path in the NFS settings - anything else just doesn’t work, Volumio rejects it immediately.
Also, via ssh it looks properly mounted and on the right location - it shows the correct folders on the NAS:
You path should be readable by Volumio, without the use of sudo.
Hence Volumio can’t scan it.
Please check the correct path for you share.
Open windows explorer and type file:\\192.168.0.101 to see the share. If you don’t see the folder it means that your share is incorrect setup.
Again the internal path volume1 is not part of a share.
I can access the share via my windows explorer, no problem. volume1/Public is the path given by Synology:
I’ve tried it with the leading slash, without, with volume1, without… only volume1/Public/Music has been accepted by volumio, otherwise an error comes.
I think this is the key - I am checking in parallel over the CIFS connection on the Tinkerboard and that dir listing works without sudo. Now I’m just trying to figure out why it mounts root protected on NFS but not on CIFS
Solved. The problem was the NFS squash setting on the Synology NAS. It needs to be “map all users to admin”.
On Volumio’s side, options vers=3 or nfsvers=3 work well, so does the longer mount path.
Thanks anyhow for the help.
Hello David Chif,
I have the same problem: the folder is mounted correctly, but I don’t see any files. Can you explain what settings you made on your Synology?
Thank you, RVpascal.
Here are simple and correct Synology NAS settings for using NFS with Volumio, to avoid issues like music not scanning or playback failing. This is based on the reported solution in the thread you shared and best practices for Synology and Volumio integration.
Recommended NFS Settings on Synology NAS (for Volumio)
1. Enable NFS Service
Go to Control Panel > File Services > NFS tab.
Enable NFS service.
Click Apply.
2. Configure the Shared Folder
Go to Control Panel > Shared Folder.
Select your music folder (e.g., Music or Public) and click Edit.
Go to the Permissions tab.
Set read access for all users (or specific ones if you manage Volumio users).
Go to the NFS Permissions tab:
Click Create and set:
Hostname/IP: use * for all or specify Volumio IP.
Privilege: Read/Write
Squash: Map all users to admin ← critical
Security: sys
Leave others default unless you need specific options.
3. Determine the Export Path
The correct NFS export path is typically like:
/volume1/Public/Music
Double-check this under Control Panel > Shared Folder > NFS Permissions (there’s usually an “NFS path” field).
4. Volumio Mount Settings
In Volumio’s “Add New Drive” section:
Type: NFS
IP address: your Synology’s local IP (e.g., 192.168.0.101)
Path: /volume1/Public/Music (match exactly what Synology provides; Volumio will reject bad paths)
Options:
nfsvers=3
or
vers=3
You can leave user/pass fields empty for NFS.
5. Scan and Verify
Once mounted, go to Sources and hit Update Library.
If it doesn’t scan:
SSH into Volumio and run mount to confirm it’s actually mounted.
Check folder permissions (ls -la) — it must be readable by user volumio without needing sudo.
Common Pitfalls
Wrong squash setting: If not set to “map all users to admin,” Volumio may mount but see no files.
Incorrect path: The exported path must match Synology’s internal export, including volume1.
Permissions: Folder and file permissions must allow read (and optionally write) access without root.
