This issue was posted on Roon forum with no solutions yet, so I am posting here.
Last post wby me was: Network has been simplified so that Roon server running on Mac mini and dCS Lina both connected directly by cable to ATT/Nokia BGW-320 Gateway/Router. The Cache and Roon Server folders were refreshed. Roon Ready dCS Lina still not recognized as such, only appears as Airplay2 device. dCS Mosaic app controls Lina without issue. Any other ideas? It worked before and then abrubtly stopped working.
Hi Eric, had similar issue yesterday with Bartok after returning from travels. Roon wouldn’t see dCS nor my working desk KEF LSX IIs. Also upgraded Roon to latest version at the time and didn’t check whether it may have been related. Mosaic could see the Bartok and Tidal app could see the KEFs. Just Roon didn’t see either. Rebooted my entire network - still not working. Eventually rebooted my Mac and that did the trick, afterwards Roon worked again.
I am having the same issue with Roon and my dCS Lina DAC. It was connected fine to Roon then the other evening the DAC could not be shutdown using the front button (I shut it off at night so it does not heat my office). I turned off the DAC from the rear and the next morning on restarting the DAC it started relay clicking repeatedly. I reset it a couple of times with the same result and eventually did a factory reset and that resolved the issue. But now it will not show up in Roon as a Roon Ready device but does show up as an Apple Airplay device. I can also connect to the Lina DAC via the Mosaic app on my iPhone so there is no ethernet connectivity issues and no firewall problems. One interesting thing is looking at the unit status screen on the DAC the serial number is set at 0. This does not appear to be a good sign and I’m wondering if something has been corrupted in the DAC.
I have another seven Roon Ready devices connected to my Roon Server and they are all working correctly, my network settings have not changed and my Roon server (Roon server running on Ubuntu 22.04) is functioning perfectly fine. Everything works except for the dCS Lina that has been turned into a rather expensive Roon paper weight.
Really need some help on this as I have only had the Lina DAC for three months. Details on versions as follows:
App Version: 1.4.3 (151)
Front Panel Version: 2.00
Control Board Version: 2.00
Network Board Version: 1.4.3 (513)
Hi Ian. I am sorry that your first visit to the community forum is in such unfortunate circumstances. I hope that we can offer some help or, at least, encouragement. However you add a new ingredient so it might not be a totally similar issue to the others in this thread though other matters are.
You say that :
As you correctly say, this is not a good sign.
The unit is only three months old so is under warranty. I therefore suggest that your immediate course of action is to contact your dealer. However I am tagging @Phil at dCS support so that he is aware of your issue.
Can you drop me an email to [email protected] along with the serial number of your unit (it’s on the label on the unit and also on the boxes) and a note that it’s in reference to this thread and I’ll get onto getting that sorted - I’m curious as to why it isn’t showing a serial number.
Hi Phil,
I did check the serial number and emailed it to you as you asked. The serial number of the Lina doesn’t display in Mosaic or in the info display on the front of the unit.
Does the status screen on your Lina DAC look like this? This is a photo of what mine is showing as we both have what appears to be very similar issues. In Mosaic it just has the serial number as a dash so basically no value. Seems like something got corrupted in our units .
Well as they say “Misery loves company” :-). I actually take us both having the same issue as somewhat good as we are not just an isolated incident and there is an off chance there might be some correlation that enables dCS to find the root cause. I’m confident that dCS will get us sorted out and back up and running they have a solid support reputation and one of the reasons I was willing to shell out the money for the Lina stack. Also, apologies if I hijacked your support thread, your symptoms were identical to mine, so it seemed silly to create a second thread. I’ll be sure to point Phil in your direction in any communications I have with him or dCS support.
Prior to having these issues with your Lina DAC did you experience a lockup in the DAC requiring a hard power off? Thats what started my problems and after a hard power off and on I had a continual clicking from the relays on power up. I had to do a factory reset to stop the relay clicking and then it dropped off Roon and I guess something got corrupted.
I’ll update the thread here as I go through the support process with Phil and others, and if you would do the same, I’d appreciate it. Had to swap in a WiiM streamer in the meantime, whilst not horrible especially when used with Roon and pushing through the Lina DAC stage it’s certainly not ideal, but first world problems for sure.
Thanks Ian for the precious insights and I agree with you fully. I have had some glitchy behavior from my Lina, just as you describe, however it wasn’t temporally correlated with the RoonReady glitch.
I am certain we will get to the bottom of this and I will keep the whole adventure updated here.
I remember an issue a long time ago where a certain firmware release caused the Network Bridge to lose its serial number upon factory reset. I wonder if a similar thing might be happening here? Afaik that shouldn’t affect RAAT discovery but since that’s a bit of a black box it is hard to know if it is related or just coincidence. Serial numbers are typically sent in discovery handshakes, but typically not used as the unique identifier for the protocol itself which is most commonly the IP address. Anyway, I am sure Phil will figure it out sooner or later and it will be interesting to hear the explanation. Please do report back.
I’m very curious as to whether there was any commonality to these two units losing their serial numbers so I’ll be following up with Ian and Eric going forwards but obviously the first things to sort is getting them back up and running so we’ll get that sorted first and then do some digging.