Several; all on wired network. I’m typing this on a Dell laptop (also wired)
Number of Tracks in Library
18,000+
Description of Issue
I have always been one of the smug ones who have felt nothing but scorn towards all those on here whingeing about all the problems they seem to have with Roon.
Until now. Since my Synology DS920+ updated the other day to:
I can’t get access to my music:
Should I abandon the NAS for music storage and connect an externat HDD to the NUC running ROCK? I’d rather not as it would mess up my backup regime. Plus I have no idea how to point to it as a network share as the NUC (presumably) isn’t running Windows.
Hi
Sorry for the trouble
I can only say mine works. m1 mini core and DS720+
But sometimes I find all the network paths hard to figure in roon (the NAS and two hhds on an iMac for backup)
Yes. I guess you already did that, Maybe try to restart the router? Also now when I did log in to get the screenshot I noticed there is a SMB update. maybe it will be a fix (if you did not already did that)
Generally, the more universal syntax for SMB connections is smb://{ip_address_or_servername}/path_to_music, and this should require username/password credentials if done right.
What are the permissions of the folder on the NAS? The user you specify in the “Add Network Share” dialog box will need to have read access to the folder.
Also, you need to make sure that the SMB service is installed, running, and configured on your 920+
I thought smb:// was only for Macs. Everything I’ve read says it’s \ for Windows; which is what worked previously.
As far as I can see the SMB service is up and running.
The \Public folder on the NAS doesn’t require a username and password. I will try the admin user and password tomorrow, but am pretty sure it still won’t work. Surely if it was a password error, Roon would come up with a more specific error message.
The really annoying thing is that I had just taken out a lifetime subscription after two years of trouble-free use. I’m not sure there’s any way I could get my money back?
Well, smb:// is for every platform, whereas \ only works with Windows. But the key thing is, you are connecting from ROCK to a Linux-based NAS, so Windows really isn’t involved at all in the network connection.
I don’t know how you are configuring shared folder access on your NAS with no credentialing. That is actually more difficult with Synology DSM than it’s worth.
Check the permissions on your “Public” folder in Control Panel > Shared Folder. Use a username and password that at least allows “Read” access (and preferably ONLY “Read” access) to that folder. And use File Station to ensure that those permissions have also cascaded down to your “MusicRoon” folder.
FWIW, one of the great things you can do with DSM is put your music all in a top-level share called “music” and get dual access to your music using Synology Audio Station and DS Audio (as well as having Roon ingest it). Food for thought!
Try all of @DDPS suggestions and let us know if it resolves the issue. There’s something simple going on here that should be easy to resolve. I’m on the same update as you with no issues.
Also, how is the DS IP address allocated? Hopefully over DHCP with an address reservation in your router so that its IP address doesn’t change?
Another bit of advice - setup a user account with the necessary admin privileges to manage your DS and disable the admin account in the Control Panel settings.
Synology recommends this approach as an additional layer of security. Anyone maliciously trying to access it from outside your network doesn’t even have a username to go on.
This is an astute question because the issue could be that your ROCK isn’t finding your NAS in the first place. I’ve had issues with name resolution on my network in the past. I’ll take Graeme’s recommendation a step further and suggest that you:
Stabilize your Synology’s IP address by using the approach he recommended
Use an IP address-based path in Roon
If the IP address of your Synology is, for example, 192.168.1.2, you can use the path \\192.168.1.2\Public or \\192.168.1.2\Music or whatever. This is what I do. It eliminates name resolution as a possible source of issues.
The recommendations from @DDPS and @Graeme_Finlayson are really good - both of them provided expert-level best practices. These are smart things to do - they’re exactly what I do.
In case there happens to be an issue with your SMB settings, here are screenshots of mine - they are from File Services > SMB > Advanced Settings. I’m not completely sure these represent current best practices but they are working.
Update: It still isn’t working, but in trying to resolve it I have discovered that my external backups and synchs to OneDrive from the NAS are no longer working either since the DSM update. The fact that I noticed that I couldn’t play music yet failed to spot messages advising of failed backups say a lot about my priorities…
So it’s presumably some kind of firewall issue. There has been a Windows update around the same time (2023-04 Cumulative Update Preview for Windows 11 Version 22H2 for x64-based Systems (KB5025305)); maybe that is to blame?
Following this - Roon ROCK cannot connect to my NAS - I would say that I’d recommend you set up your shared folder to use a username and password. Please let us know if you have tried that and get back to us with the results!
Thanks, tried that without success.
I’ve basically abandoned the NAS for now. I’ve got a 2TB SSD installed in the ROCK, and it works great. Backing up manually to a portable drive, but would still be nice to schedule backups to the NAS.
Are you syncing your NAS with OneDrive using Synology Cloud Sync? I do exactly that and the latest Synology update did not break it for me. I’m on Cloud Sync 2.6.1-2286 - released 2022-09-22. Synology’s online release notes describe version 2.6.1-2507, released 2023-04-25. That version isn’t showing up as an update option for me yet. If you are using CloudSync and you aren’t on one of these versions, I suggest updating if an update is available in Package Center.
That said, it’s hard to imagine that a OneDrive syncing issue is related to the Roon/SMB issue you’re experiencing. I also don’t understand how a Windows update would be relevant here at all since nothing said previously suggests that a Windows machine could be involved in either your ROCK accessing your NAS or your NAS accessing OneDrive.
If you share the steps you’ve tried to address your SMB issue, we might be able to get a better sense of what you’ve done and make additional suggestions.
I am having much the same problem in attempting to add a sooloos system and those files saved on it. It worked using a Mac mini but stopped working when I switched my roon core to a NUC ROCK. I have repeatedly attempted to add two different sooloos storage components together with a sooloos control 15 and its internal HDD. Beyond frustrating. .
Right - now sorted, but with a major issue remaining. Sorry it’s taken so long to reply to all you helpful people but I’ve been horribly busy over the last few days.
@Graeme_Finlayson I set up a new admin account, and disabled the default one, when I initially set up the NAS as advised by Symology.
There’s clearly something that’s changed in the latest DSM update. I can’t be 100% certain but it looks like it’s no longer possible to access a folder, even one with minimal security, without a username and password. Which is fair enough, I suppose.
I tried connecting using the NAS admin username and password, and hey presto it immediately worked. That’s great, but I obviously don’t want to connect as admin. The problem I have now is that I can’t find a way to edit the connection to replace admin with an ordinary user.
If I remove the connection and try to reinstate it, it just shows the folder as available and connects straight away if I select it, presumably because it remembers the previous credentials. Is there a way to totally remove it from Roon’s memory so it can be re-established with different credentials?
Ben here with the support team, I wanted to check in on your status with getting your local library added back into Roon. From reviewing your core diagnostics, it does appear that your local content is active on your core recently.
Is this the case? I hope it is, and that you’ve been able to get back to your music!
