Synology NFS network drive no longer connecting

Help and Support
1

Two days ago, a new release of Volumio was automatically installed on my Primo. Yesterday, Primo / Volumio was no longer able to make an NFS connection to my Synology network drive. Has anyone esle experienced this? solutions? Thanks,'Fran

2

Is any one else seeing this?

3

Sorry can’t comment for the Primo, however no issues with the PrimoV2, Rivo and Motivo. They all got updated yesterday. Only difference is that I am using a NAS from QNAP.
You might want to share a log, it might give us some insight. If not you can open a support ticket with Volumio. As Primo owner you’re entitled to premium support.

4

Thanks Wheaten. Here is the link to the log file … http://logs.volumio.org/volumio/3v9ziSk.html

It took a while with help from Davide in Volumio support to get this connection working in February 2024. Since then, it has been working (save for the occasional reboot/rescan). Nothing has changed on my end.

Problems seem to coincide with the installation of the latest Volumio release. I tried to play a song. Volumio could not find. I rebooted, rescanned . . . now my music count is at zero.

I can access the drive by other means.

I have sent a couple of emails to Volumio support with no answer. Any help would be greatly appreciated.
Thanks,
Fran

5

I see in your logs: ‘volume2/FranMusicNetworkFolder’ with ‘Cannot mount NAS Synology_NFS_Music at system boot, trial number 4, retrying in 5 seconds’.

Additionally, there are numerous errors on top.

Please test the following NFS mount options, one at a time:

  • nfsvers=3
  • nfsvers=4
  • nfsvers=4.1

If one of these options succeeds, note it down and perform a factory reset to remove all residual configurations.

6

Thanks Wheaton. Where do I specify the NFS mount options? Is that within the Volumio configurations (e.g. “options” in the network drive configuration)? I tried entering * nfsvers=3 in the options field but got an error saving (it flashed so quickly I could not read). When I went back to look, it was not there.

I also tried going into the Synology NFS configuration. It was set at “maximum NFS protocol NFSv3”. I changed to NFSv4 then rebooted Primo . . . that did not fix. I changed to NFSv4.1 then rebooted Primo . . . that did not work.

Here is the new log http://logs.volumio.org/volumio/UPtpjIV.html

Thanks,
Fran

7
  • Please perform a factory reset
  • Execute the initial setup
  • Mount the network drive and experiment again with the nfsvers options. (it’s indeed in the options field of the network mount)

@ded, @Marco_Melziade
please take a look.

8

OK. I did the factory reset. I tried all three of those settings on the Source–>AdvancedOptions–>Options. The first setting, I was allowed to save but it still did not mount. The second and third settings, I was not allowed to save. I got the message …
image

Here is the latest log http://logs.volumio.org/volumio/uf8peL4.html

Any ideas?

9

Wheaten,
Thank you very much for your help. I did get it to work.

Apparently, the IP address for Primo (the one I had granted NFS permissions) had changed (not sure why). I went into the Synology UI under NFS permissions for the shared folder. I was then able to specify the “option” in the Volumio Sources UI to nfsvers=3 and successfully saved. The music DB creation started right after that.

Thanks again for your help,
Fran

1 Like
10

Sorry just visited the forum…
Wasn’t aware you protected access via IP, Glad you got it resolved!

11

Just a hint.

NFSv4 requires a unique Domain ID definition. This option you will find in the „advanced settings“.