Hi, I just updated to the latest roonserver for qnap but it doesn’t appear to be working properly.
The program starts and shows it is running but when I open the actual program on my qnap it says “Status: Stopped”, and I have no way to “start” it. So none of my roon clients can find the server.
Never encountered an issue like this.
The Roon Server package no longer works, please switch to the official Docker image to run Roon Server on your NAS. See also:
Thank you. But since I cannot get onto my old roon server is there any way of creating a backup?
No, no more. Roon did nag you to setup a scheduled backup job in the past as it is highly recommended to have backups. If you did not follow the advice to set a backup schedule then you’re now out of luck. Else, just take the backups you already have.
This really leads to a question… prior to the latest release Roon had a pinned notice on top explaining how and why Roon will be incompatible with certain systems. They’ve removed it when the new version was released. But of course the majority of users, who haven’t had problems before, were not hanging out on the forum constantly and are coming in for support only now.
Could Roon maybe restore the pinned message and put links to Docker setup there?
Good point for @Stephen to consider
I’m sorry but that is messed up. If I didn’t have backups and my computer/nas failed that is on me. But for something to suddenly not be supported or available without any notice, allowing me to make backups is frankly ■■■■■■■■■ I don’t hang out on the forums and have been a roon user since literally day 1. The amount of playlists, favourited albums/artists etc. i’ve now lost is ridiculous, simply because I decided to “update” the software when I got a notice, like I have done ever since I bought a nas. Why even give qnap users notification for an update, if doing that update is going to brick their server.
If you run an older version QNap, like 251+, it won’t work. Even if you invest to higher RAM.
The communication was not great, you can post in Feedback. However your database could have been corrupted or a hundred other things gone wrong any day since day 1. Not having backups is just asking for it.
I agree, and that would be one me if something happened over the years.
However this isn’t the case. I received a notice, like I have a hundred times before, to update the roon software. I ignored it for a couple weeks like I usually do, and today finally decided to update. To my surprise, after updating, roon server was bricked. So again, why offer me an update that is going to brick me and prevent me from creating a backup?
It is an absolutely terrible way to go about progressing things. I had no idea things were changing until I came on the forum. I don’t hang out on the forum, so im not up to date on wth is happening.
There were some communication errors. It was mentioned in the monthly newsletter, but someone thought that it would be a good idea to have it as the last item rather than the first. There also was supposed to be a full-window in-app message that would block access until acknowledging it (this is apparently a built-in messaging system) but it seems that it either didn’t work at all or at least not everyone got it.
@Stephen Considering the communication errors and the surprisingly many users who care a lot about their database but don’t have backups, I really think Roon Labs should make a 2.64 QNAP installer available to help out. And in the future, maybe turn up the backup nagging a few notches and make users click an explicit „I accept the risk“ button to stop it.
Support this idea for QNAP, as it was the case with MacOS 10/11, s. link
All this information should still be in the database folder in RoonOnNas installation on your QNAP. Even if there is no way to make this readable by Roon 2.65 in the container, there should be a way to access it on a QNAP machine still running Roon 2.64.
So, either way, I recommend to make a backup of that folder, maybe there will be a way to read it in future. I wonder if installing legacy roon from the App Center, or .qpkg file, suppressing the update when firing it up, would help. Or is the database version too new to be understand by this 2023 distribution?
Roon isn’t in the package at all. It gets download on first run and after that it is self-updating as we all know it.
Don´t loose hope. According to a member of the roon team, it is possible to retrieve information from the V2.64 database generated by RoonOnNAS app, by running 2.65 in the container. If I understood the following post correctly, the complete database can be copied into the container running roon, so the new app would recognize all your data:
See last answer by @vova regarding transferring the /Database/ folder from RoonOnNAS to Container.
Good luck!
Vadim, just to avoid confusion 
Oh, sorry, @vadim of course. Michael Wolff would now tell the joke about names sounding all the same
Sorry for my absence this week. If theory (and some have reported success with it) you can install the container on QNAP and instead of using “/share/Container/Roon” you can point to the RoonOnNas directory and it’ll start up with your existing data.
I’d strongly recommend creating a copy of that directory first though.
For some folks, this path is anyways not ideal, for the reason /Container folder might have previously been created on an HDD volume, and come with user-specific write restrictions. I would instead recommend to create a tnew op-level folder, for example /RooninContainer on an SSD volume (where /RoononNAS or its database was residing), apart from the /Container for Container station. So the share path would look like this:
/share/RooninContainer/roon
I got bit by this same thing (mind-boggling that Roon installed an update on incompatible hardware, and with no warning where most of us would ever see it) but was able to get running again via Container Station. Now the Roon app on my computer tells me that there is an update version 2.65 (build 1653) available for Roon Server on my QNAP. Is there any way to tell if this or future updates are safe to install?