· My Roon App doesn't recognize my DAC audio sources. In fact, they are visible on the screen and enabled but no sound will come out of them. Meanwhile I get the sound on my iPad or my computer if these sources are enabled. It seems that the Nucleus One doesn't connect to my 2 DACs even if they are enabled. This happened since I last opened my application and got the last update.
Also, the Roon application says that ARC can securely access my Roon Server. But when I open ARC on my phone, it says that my Roon Server is on line but a problem prevents ARC from accessing it.
Thanks for writing in and for sharing your report! We were able to review a fresh daignstioc report from your Nucleus, and unfortunately found repeated traces pointing at a corrupt database:
Do you have any saved backups? The best first step here would be to test out restoring from a saved backup, ideally one that predates the issues you’re having.
Let me know if you have any backups, and if you’re able to restore from one. From there, we can review another diagnostic report to see if there are any corrupt traces like above.
We’ll be monitoring for your reply and results, thank you!
Thanks for your answer. Just looked at my App. As soon as I opened it it said: Problem with charging your library. To avoid the loss of data, restore a backup now or clic on the help center for more information.
If I clic on the backup, I get a few options: One is RoonBackups on the Nucleus One, another is my NAS Synology. The NAS contains more info than the Nucleus One from what I can tell. So I chose the NAS, found a backup from before my troubles clicked on it and I ended up exactly in the same window as before: Problem with charging your library…
So I’m going in circles here. Can’t get out of this.
I’m leaving tomorrow for 2 days. I’ll check my emails when I get back. Hoping you will have some solution for me,
Upon reviewing the diagnostics report, the team is seeing that the database that you restored is showing the same signs of corruption as the previous database.
There are a number of reasons why a Roon database can become corrupted, and this can include failing hard drives, as well as other environmental factors, like power loss, or sync programs tampering with the contents of the database.
It’s extremely hard to know what might be at play here, but what is certain is that when Roon reads the database back, the files are different from what was originally written to the drive, and the changes are significant enough that Roon cannot load the database properly.
There are times when the corruption can be “latent”: part of the database is corrupted, but the database can still load. Often, this latent corruption is revealed when Roon updates to a new database format, as this process requires that every record in the database is accessed.
This is likely the case here — The backup that you used to restore was made after the latent corruption existed.
Generally, the solution is to try using an even older backup if you have one in order to use a backup from before the corruption occurred. Otherwise, starting fresh is the second option.
I went back on my App. It is asking me to restaure from a Backup as you know. So, from the begining, I have set up backups on 2 different places. One is the NucleusOne. the other is my PC. In both cases, the backups that I have date from June and July 2025 and then there is a gap without backups and it continues on February and March 2026. Another mystery since I have programmed them every 4 days. So I chose one backup from my PC dated July 2025 and asked to restaure. And it didn’t work. It got me right back to the same message: “There is a problem with the loading of your library”. Then I tried the same maneuver wiht the July backup on the PC and got the same answer. So I am unable to get out of this vicious circle.
I have to say that I’ve had lots of trouble with my Nucleus One. To the point where I regreted having changed from Sonos to Roon many times. Every time there is a Power failiure (not so often, but maybe 5 to 10 times per year), I have to reset everything and play around with my system. I finally bought a surge battery in the hope that it would solve this problem. BTW I don’t understand why the restart system was not programmed into this Nucleus One. It would save a lot of trouble. Especially when I am in vacation out of my home and obviously not able to restart the machine manually.
So my gut feeling is that maybe the hardware itself could be corrupt from the start, kind of a lemon.
I’m sorry to hear you’re experiencing corruption across your other saved backups. That said, we reviewed another fresh diagnostic report from your Nucleus, and didn’t see any signs or traces pointing to a hardware malfunction.
We did, however see an interesting trace surrounding a connecting audio device, the Qutest:
First, the Audio Device was detected: A Chord Electronics “Qutest” Digital-to-Analog Converter (DAC) was plugged in, powered on, or detected on USB port 1-4.
We then see a Firmware Volume Warning: The Linux kernel read the device’s properties but immediately threw a warning: Warning! Unlikely big volume range (=32767), cval->res is probably wrong. This means the DAC’s firmware reported an abnormally massive range for the hardware volume scale (-32767/0/1).
Then, the Segfault error: Immediately after that warning, alsactl attempted to initialize the controls for the newly detected DAC. Because the volume data it received was unexpectedly large or malformed, the utility experienced a memory error (it tried to read an invalid memory offset at 28) and crashed.
Can you check and reinstall the latest firmware for your DAC?
If you’re not having any luck with your oldest backup, then the only alternative is to start with a fresh database, unfortunately. We know that many of us have a carefully curated database: our settings, album covers, metadata, tags, playlists and favorites are exactly as we want them to be. Having to start fresh sounds like a nightmare and we do hope it won’t come to it. But, if it does, please know this is so it will almost never happen again.
There is no firmware to be installed in the Qutest. I searched everything online and got in touch with a technician who works with the Qutest (recommended by the company). So the only existing drivers that can be installed are for computers in order to listen to music on that computer which is not the case here. There is no firmware availlable.
The only other possibility that I can imagine other than a problem with the NucleusOne itself would be somehow the failure of the Shanty that is plugged between the NucleusOne and my DACs. This is the only common denominator between the NucleusOne and the DACs since the music outputs function for the iPad and my PC (who is in line with a ethernet connection with my home network).
So right now, nothing works at all. I can’t go past the message “There is a problem with the loading of you library”. Then I am asked to chose a backup to reinstall and if I accept, I end up with the previous message. The snakes that bites it’s tail.
I removed the Shanty from my system for now and I would like you to test and see if you get a different diagnosis of my system. I have nothing else to suggest on my side. I’ve been out of music now for over one month. Can you please do that and keep me posted? Thank you
Thanks for the follow-up! You have my apologies as well, as you are correct in that for the Qutest specifically, there is no user-installable firmware.
As of April 2nd, I no longer see the same segfault errors as before, so I suspect you are correct in that the Shanty was causing some issues there.
I’m really sorry to hear this. In case you may have missed my prior message to this - If you’re not having any luck with your oldest backup, then the only alternative is to start with a fresh database, unfortunately.
I have restored the database and settings. And I am exactly where I was the first time that I wrote to you 16 days ago: “My Roon App doesn’t recognize my DAC audio sources. In fact, they are visible on the screen and enabled but no sound will come out of them. Meanwhile I get the sound on my iPad or my computer if these sources are enabled. It seems that the Nucleus One doesn’t connect to my 2 DACs even if they are enabled.”
What solution do you have for me now? Since you said that the problem would be solved by resetting the database which I did!
I was reading the signal path document in order to share the screenshot you asked for. Then I stopped and decided to try again my system and see if it works or not. And, SURPRISE, it works now. First the iPad sound came out. Then the Schitt Modi DAC and finally, after numerous tries, at last the Chord Qtest worked too.
I have to say it took me reveral attempts before it all worked. But now, I’m in business. However, I don’t know what caused all this and frankly, if there is a way not to live this whole drama again, I’d like to know it and prevent it.
Thank you for the support and please let me know if you can help me to avoid such another episode.
