Remotes can't connect to ROCK if NAS connection fails

Roon Core Machine

Brand new ROCK build, NUC10i7FNHN1, 128 SSD, 8 GB RAM
Version 1.8 (build 831) stable
Remotes: iPhone X Pro, iPhone XR, Windows 10 XP, iPAD 9th Gen
(All on current Roon software)
Music files on an old Synology NAS DS212.

Networking Gear & Setup Details

Netgear Orbi Mesh Router: RBR50/RBS50
Netgear Ethernet Switch GS-108
ROCK Core is plugged directly into the router

Connected Audio Devices

Using Tidal and Qobuz to stream
Main system streams to LUMIN D1 in Roon Ready Mode, WIFI backhaul connection
Also have Sonos, both S1 & S2 components, using sonosnet with either a wired boost or wired streamer.

Number of Tracks in Library

Approximately 3000 tracks in library

Description of Issue

I am brand new to Roon, in fact just finishing up my trial membership. I’ve been running Roon on a dedicated seven-year-old ThinkPad without issues. I just purchased a NUC, installed ROCK on it and migrated the database. All seemed good at first, then we started having lock-ups and problems streaming Qobuz.

In the process of troubleshooting those issues (still unresolved), I unplugged and rebooted all of my network devices in the appropriate order. After that, I was no longer able to connect to the ROCK core. I could still connect to the old Thinkpad Core.

So, I went digging around in the logs and discovered that the ROCK core was circling around trying to connect to my NAS, which I had forgotten to turn back on. Here are the logs showing the issue. It just kept circling around trying to connect to the NAS.

Once I turned the NAS back on, I was able to connect again. This is concerning. The Thinkpad Core was smart enough to move on and connect without the NAS connection. Can this be fixed? What if my NAS breaks? Would I have to rebuild my CORE?

I’m still working on the other issues but thought it worthwhile to get this sorted out first. Thanks in advance for your help.


Section from log that kept getting repeated:

10/25 21:10:42 Warn: [roon/cifs] failed to connect to CIFS storage: mount error: could not resolve address for diskstation: Unknown error
10/25 21:10:42 Info: [broker/filebrowser/volumeshare] Volume's CIFSMount's availability changed: False
10/25 21:10:42 Debug: [broker/filebrowser/drive] availability on drive's volume changed: False: VolumeShare[networkpath:\\diskstation\sonos,mountdir:<null>]
10/25 21:10:42 Info: [broker/locations/directorystoragelocation] drive availabilitychanged: False, FileBrowser.Entry: \\diskstation, sonos : \ (it was False)
10/25 21:10:47 Debug: [roon/cifs] tryremount, path: \\diskstation\sonos, username: music, password 9 chars
10/25 21:10:47 Debug: [roon/cifs] mounting \\diskstation\sonos
10/25 21:10:47 Debug: [roon/cifs] alreadymounted? //diskstation/sonos => false
10/25 21:10:47 Debug: [roon/cifs] alreadymounted? //diskstation/sonos => false
10/25 21:10:47 Debug: [roon/cifs] cleaning mount points: /roon/sys/storage/smbmounts/RoonStorage_*
10/25 21:10:47 Debug: [roon/cifs] domount: PASSWD="******" /sbin/mount.cifs "//diskstation/sonos" "/roon/sys/storage/smbmounts/RoonStorage_c5e2d51e625047f9328ce6e8e2296ca2a097a8f7" -o guest,nounix,iocharset=utf8,user="music",domain="WORKGROUP",vers=2.1
10/25 21:10:48 Debug: [roon/cifs] returned 1: mount error: could not resolve address for diskstation: Unknown error
10/25 21:10:48 Debug: [roon/cifs] PASSWD="******" /sbin/mount.cifs "//diskstation/sonos" "/roon/sys/storage/smbmounts/RoonStorage_c5e2d51e625047f9328ce6e8e2296ca2a097a8f7" -o guest,nounix,iocharset=utf8,user="music",domain="WORKGROUP",vers=2.1 failed: (1): mount error: could not resolve address for diskstation: Unknown error
10/25 21:10:48 Debug: [roon/cifs] domount: PASSWD="******" /sbin/mount.cifs "//diskstation/sonos" "/roon/sys/storage/smbmounts/RoonStorage_c5e2d51e625047f9328ce6e8e2296ca2a097a8f7" -o guest,nounix,iocharset=utf8,user="music",domain="WORKGROUP",vers=2.0
10/25 21:10:48 Debug: [roon/cifs] returned 1: mount error: could not resolve address for diskstation: Unknown error
10/25 21:10:48 Debug: [roon/cifs] PASSWD="******" /sbin/mount.cifs "//diskstation/sonos" "/roon/sys/storage/smbmounts/RoonStorage_c5e2d51e625047f9328ce6e8e2296ca2a097a8f7" -o guest,nounix,iocharset=utf8,user="music",domain="WORKGROUP",vers=2.0 failed: (1): mount error: could not resolve address for diskstation: Unknown error
10/25 21:10:48 Debug: [roon/cifs] domount: PASSWD="******" /sbin/mount.cifs "//diskstation/sonos" "/roon/sys/storage/smbmounts/RoonStorage_c5e2d51e625047f9328ce6e8e2296ca2a097a8f7" -o guest,nounix,iocharset=utf8,user="music",domain="WORKGROUP",vers=1.0
10/25 21:10:49 Debug: [roon/cifs] returned 1: mount error: could not resolve address for diskstation: Unknown error
10/25 21:10:49 Debug: [roon/cifs] PASSWD="******" /sbin/mount.cifs "//diskstation/sonos" "/roon/sys/storage/smbmounts/RoonStorage_c5e2d51e625047f9328ce6e8e2296ca2a097a8f7" -o guest,nounix,iocharset=utf8,user="music",domain="WORKGROUP",vers=1.0 failed: (1): mount error: could not resolve address for diskstation: Unknown error
10/25 21:10:49 Debug: [roon/cifs] Mount deleting: /roon/sys/storage/smbmounts/RoonStorage_c5e2d51e625047f9328ce6e8e2296ca2a097a8f7

I’m not sure this is related, but Windows and ROCK / Linux have different mount syntax. You may try following the Linux mounting format at the bottom of this page instead and see if it makes any difference (e.g. smb://192.168.1.120/Multimedia/Music ):

Well … I was suspicious but gave it a try. I’m assuming you meant to change the path designation in the settings on the remote … which I did by deleting the drive connection and reestablishing. Interestingly, despite me referencing it with the smb syntax, it reverted to the the old \DISKSTATION syntax after I set it. Go figure.

But, I was eventually able to turn off the NAS and disconnect/reconnect to the ROCK core on my remote, with the NAS still turned off. There are so many variables, that I’m not sure what’s going on; this has been a steep learning curve for me. For now, everything is working. If I have issues down the road, I will post another request and try to do some troubleshooting first.

Thank you for your help.

1 Like

This topic was automatically closed 36 hours after the last reply. New replies are no longer allowed.