I have a Unifi based network running UDM Pro and Unifi Pro switches, ethernet wired network, latest builds. Roon ROCK device connected directly to Unifi switch
I have my music library on a Synology NAS, I can see the network location properly in the storage options of Roon, everything worked fine for years. However, a few days ago I noticed that when I place new music content in the watched folders they do not appear in my library until I force a rescan, this is not how Roon worked for me in the past.
Both the Synology folders and the Roon ROCK device are on the same network. I rebooted both the Roon ROCK and Synology NAS devices (DS423+) and the behavior did not change.
In Unifi, I have ensured that all traffic is allowed on my VLAN where the Synology and Rock device sit.
Have you tried to do a “Force rescan” as described in:
How long did you wait? Roon has a scheduled rescan interval (check the options of your watched folder) for network shares – but network shares only.
Note: Often NAS devices fail to properly announce changes to Roon. Inotify is known for having a default max_user_watches value of only 8192 entities. So depending on library content, structure and additional files in it, you may start running into issues with libraries around 7k tracks. Synology does not provide users with a means to change that value in their OS/GUI. Here is an article that tells you how you can increase the value if needed:
PS: Realtime watching for network shares is a feature of SMB3 so make sure that the maximum allowed protocol version is at least 3.0.
Thanks for reaching out to us about this issue. As a first step, please give @BlackJack’s suggestion a try and let us know how it goes. We’re here to help if you need any further assistance!
A force rescan (or restart of the Roon ROCK device) updates the missing content. I did test with a new Synology NAS with a share that contains only 1 album with 13 tracks, and the same thing is happening there, the content is not updated until the force re-scan is initiated so I am sure something is not right here.
So it seems that nothing is wrong with Roon Server and that Roon Server can access the remote share quite well. Waiting until the scheduled rescan happens should work too for you.
Realtime watching though depends entirely on the host (of the files) OS and its capability to monitor files / folders and communicate changes to interested parties. For shares it additionally requires that SMB 3 is negotiated as transport protocol. Hardly any of this is under the control of Roon Labs’ software.
What you can do is lookup the Storage page in Roon to check if Roon Server thinks it is real-time watching the folder (please post a screenshot of the page here).
Maybe Roon Labs can see something, looking into the logs from your Roon Server.
If not, and as monitoring should happen on the NAS in the first place, you should pronanly contact Synology support too.
The only thing I recently modified in my setup is the NFS version, I recently moved it up to NFS 4.1 but I don’t think NFS settings impact the Inotify services since Roon uses SMB and my music library is not an NFS share:
As far as the Roon storage settings, here is a screenshot where you can see both Synology NAS units (DS423 and DS423B) configured and reporting as “watching in real time”
So it looks like Roon negotiated successfully for receiving filesystem change notification. You need to troubleshoot your NASes to find out why they don’t send those notifications as you expect. The most likely reason is still an insufficient max_user_watches value on your NAS.
Note: Real-time watching isn’t a feature of Roon. It is a feature of the involved OSes (and SMB for shares) that Roon can utilize – if it works. It is “nice-to-have” but not required for Roon.
Impatient users can force a rescan, others can simply wait for the scheduled rescan to happen.
The thing is, both Synology NAS drives are doing this, one has my main library (6700+ albums) and the second Synology NAS has only 2 albums, both with the same behavior.
I would like to troubleshoot Inotify traffic/events on both the Roon ROCK as well as the Synology NAS… I can’t SSH into my Roon ROCK device so that options is a closed door for me.
There is nothing you can do on ROCK neither should there be a reason to – SMB works (and inotify for your shares concerns the NAS not ROCK). Synology support should be able to help you with the NAS side (inotify and SMB server troubleshooting).
Unlikely as SMB works. Should you block traffic though, you can try and disable the blocking software.
Note: Roon requires all devices to be in the same network, so there are no blocks to be expected.
I’ve read through the recent activity on this thread, and I agree with @BlackJack — reaching out to Synology support could be a helpful next step. If they’re able to confirm that there are no issues on the NAS side, we’ll be happy to escalate this to our developers for a deeper investigation. We just want to be certain the issue isn’t external before moving forward.
I will reach out to Synology on this, not exactly sure what is it that I have to ask them to lol for? Is there any brief technical explanation about what Roon Server expects to recieve to be able to properly refresh the changes?
I don’t intend to beat a dead horse here, while I wait for Synology tech support to get back to me, I created an SMB file share on Ubuntu Desktop 24.10 and added this share as a storage location in Roon (also showing as “watching in real time”
When I added a couple of albums to that share, nothing happened. The content does not reflect in realtime, I have to force the scan to see content changes. This means the issue is now repeating on both Synology NAS devices as well as my Ubuntu client machines.
Can someone from support check the health of the Inotify and SMB services on my Roon ROCK NUC?