Been away for a few days. When I switched on the PC, everything was fine. But nothing was done in the mean time. Chromecast was fine.
I did a new setup, factory settings and reinitialized the NAS, so a fresh start. The NAS is only a few months old and everything is brand new and QNAP compatible. Tried the setup wich Roon advises. Roon and database on a SSD and the library in a RAID on the HDD’s. Used one SSD for cache acceleration and used overprovisioning on both SSD’s. (encouraged by the fact the tests revealed no hardware failures)
QNAP issued a firmware update.
Played music from my library and TIDAL via QNAP HDMI/RAAT/Pioneer SC-LX58. Everything fine.
The problems started after a restart of the NAS, ending with lost storage. As a partner of QNAP and a advertisment companion, this looks like something on your side, QNAP and/or Roon.
So, because I’ve got nothing better to do (…), reinitialized the NAS one last time to set it up as a QTier (the NAS puts the system and apps on the SSD) and without overprovisioning as in @crieke his setup. The only thing I did since is removing the corrupted files from my library and loading the library. Roon is analyzing as we speak, no TIDAL yet.
Can you please take a look at the logs from just after the crash and the most recent from a few hours ago when everything is stil okay? It looks like a problem in the way/sequence QNAP shuts down Roon when busy. The same happened earlier after a manual back-up, so a restart of the core. Do you now if somebody else is using Roon with this NAS (HS-453DX 8GB)?
I can reach out to QNAP, but it looks like everything is working fine, except Roon. What do I ask them?
Still a lot of questions. This is my final attempt. I’m willing to help, you’ve build a beautifull program. Just not for this combi, it seems. And that was just what pushed me towards this NAS…
Edit: The new update is installed and because I’ve got a license for one device, the core is now again back on the NAS.
Edit2: In the System Resources app the RoonAppliance process is showing as a System Proces, after some installs it was grouped as a bunch of Roon Processes, with it’s own Roon icon.