I have seen similar issues, have not diagnosed it to needing a reboot of the ROCK, though. I thought my issue was network related. I will have to keep an eye out for this and pay more attention next time.
Oh, and adding @support so they get notified for you.
At 7:20 am PST (I am giving you times so you map to the logs)
I added back my SMB folders (since we rebooted both RoonServer and Roon ROCK this morning)
I power cycled the dCS Network Bridge
Everything is working again. As soon as dCS power cycled, ROON found it.
What is ODD is the dCS App never lost the dCS Network Bridge, but Roon likes to.
Let me know if you need any additional info.
I see this similar behavior about every few weeks.
This week I hit it in 5 days since I was playing almost continuously.
sorry, I misunderstood your steps… step #1 was the restart of roonserver only, and although it found other devices, it did not find the dCS Bridge.
the SMB issue is already being looked at by tech team. Can you tell me what SMB server you are using? is it windows/mac/nas/etc… ? what model/versions?
@support will have to look at logs for the dCS thing, unless they already know something about that unit.
Hi @Mohammed_Samji ---- It would be great if you can provide us with the logs from the dCS NBR. I will be contacting you with upload instructions via PM momentarily.
I had the same with my Rossini DAC.
Untill the update of dCS I let Roon usample/downsample to one sample rate.
The issue begins when the ROON/dCS combi changes from high to low sampler rates.
Not always…
Have you ever gotten into this state while Roon is actively playing back to the Network Bridge? In other words, playback just stops either mid track or at the transition to a new track then the queue starts being eaten.
Before rebooting ROCK are you able to play to any of your Sonos endpoints or do you see the same behavior with them?
If it’s only the bridge have you tried power-cycling the bridge before rebooting ROCK?
There are some known issues with the firmware on the Bridge as it relates to Roon and they’re being worked by dCS. I’m trying to figure out if your issue is a manifestation of one of those known bugs or something new.
I’ve used the Bridge in several situations with a similar complement of hardware (including Sonos) and haven’t run into an issue where the Bridge would get completely lost like that. This has happened with Sonos playback and a restart of the core was required (although in those cases I just rebooted ROCK), but the bridge has usually been pretty reliable in terms of self-recovery.
This behavior sounds like a known issue that is fixed in RAAT SDK 1.1.21 back in July. It was not a very common failure–most common for people with more than one core active on the network. We’ve only had maybe 2-3 reports of it in the wild across the whole ecosystem. It came up in QA at one of our partners where they have many cores running, and that gave us the clue to figure out how to reproduce/fix.
I believe that the bridge is still on an older version (maybe 1.1.18). I think this will be fixed once it is up to date.