· Other
· I am experiencing freezes or crashes
· Other
Error message: 'too many failures' shuts down all play. Worked perfectly the day before.
Isolated network: NAS>ORendu>DAC>Linestage
Hello @David_Martinez
Thank you for reaching out. At the moment, there isn’t enough detail in your report for us to understand what’s happening and provide specific guidance.
Could you please provide some additional information:
With these details, we’ll be able to better understand the cause and suggest the right next steps.
Hi @David_Martinez,
We wanted to reach back since we haven’t seen a response to this thread yet.
RoonServer logs from 8/24 that automatically reached our diagnostic servers indicate that the Roon Ready Zone in question (the opticalRendu) is not expecting to receive 16/44 PCM from Roon Ready when served a standard FLAC file.
This type of low-level “format not supported” error with standard 16/44 PCM can usually occur if the endpoint firmware is configured to receive only DSD/DoP.
Please double-check any settings in the opticalRendu and downstream devices to ensure that they’re not expecting a sample rate above 44KHz.
I’d restart both the RoonServer machine and the endpoint in sequence and disable/re-enable the Zone.
To proceed from here, we’ll need a screenshot of Signal Path and precise description of the network pathway (ethernet vs. WiFi and any hardware involved). Keep in mind this thread will close automatically after several days without any response from the OP. We’ll keep an eye out for a post - thank you!
Hi Conner, Vadim
Thank you so much for your support response. I apologize for not replying sooner but have been swamped with work.
I will prepare a response with techinical details you ask for and screen shot later today. Please do not close this tread at this time. Thank you. David
Hi @David_Martinez ,
No worries, do send us the info when you can. Your case will remain open until the auto-closer kicks in (9 days with no response) or the thread is solved.
Noris, Thank you.
David
Hello @David_Martinez
We are in the standby mode.
Thank you all. ROON is restored after the re-start sequence suggested by Conner. Both DSD and PCM play normally. My apologies for taking so long to address this issue per your suggestions.
FYI: None the less here is the information you requested:
Music Server: Green Computer Sonic Transporter: v. 2.9
Network Player: Optical Rendu: v. 2.9
Roon Server Version: 2.54 (build 1554) production
+Router>ethernet>Synology NAS
+Router>ethernet> Sonic Transport
+Router>ethernet> Optical Rendu>USB>EMM DA3>IC>Linestage
Thank you again for your gracious help.
Cheers, David
Good day @David_Martinez !
Thanks for reaching us back!
Can you please confirm whether your issue is still relevant because from your last message it’s not clear whether it’s fixed or not by steps advised by Connor.
If you experience the problem still could you please confirm the exact time stamp (day + time (AM/PM)) so we could precisely check it in the diagnostics data ?
Thanks!
Regards.
Hello Alex,
I forgot to mention in my email (I was listening to an album at the time) that I routinely restart the Roon server (Sonicorbiter), Roon itself on the Sonicorbiter web page and Roon Remote on my iPad…And I check for loose connections and power since we have frequent local (Normal in California!) power ‘brown outs’ and flat out power failures which happen randomly, and did happen recently. The Roon server and ORendu components do not routinely re-start when power is restored. In addition, there is the ‘House keepers Hazard’- that is my housekeepers are compulsive about chasing every speck of dust and will move components such as ORendu and its power supply and other components.
It turns out that the power supply to the ORendu power unit was just barely unplugged but not visibly obvious. I re-plugged it firmly as part of the process and thought nothing of it as the error message of ‘too many failures’ seemed to point to Roon software rather than the power supply. I made the mistake of not noting whether the indicator LEDs on the ORendu were on. They were not.
Can Roon add an error message advising the user that there has been a power interruption instead of displaying the cryptic ‘too many failures’ error message. Or at least remove the error message; it is confusing and points the user in the wrong direction for the source of the malfunction. Ultimately, this, indeed, was not a Roon issue; rather it was a user issue.
And, Roon functionality is now fully restored. My apologies for not communicating this to you in detail in my initial response that Roon was restored.
Again, thank you and the Roon Team for your kind and gracious support.
David
Good day @David_Martinez !
Glad to hear it is figured out !
Thank you for your suggestion. We will consider discussing it internally and maybe one of the future updates will feature the discrete error indication.
As of now we wish you a good day and listening experience!
Have a nice day!
Regards.
This topic was automatically closed 9 days after the last reply. New replies are no longer allowed.