· Updating firmware to QTS 5.2.10.3568 results in ROON completely disappearing from the NAS. Container Station shows no containers and no applications. File Manager shows no containers. Is this going to happen every time I update the NAS firmware? Having to go through the same complicated process to reinstall ROON all over again is ridiculous. ROON has become more trouble than it is worth.
Just to update, I have restored the container from a backup and rebooted the NAS.
ROON seems to be running OK now.
Still a headache if this is going to be a regular occurance.
mjw
(You want nice, supportive? Call a damn helpline.)
3
That’s probably a question for QNAP since containers should persist with firmware or app (Container Station) updates. This is certainly my experience with Linux in general.
What where you looking there for? Why not using Container Station? Where did you install Container Station to, where Roon Server to? Sounds a bit like you possibly chose a non-persistent storage location for at least one of the two.
What you’re experiencing isn’t normal or expected behavior and most Roon QNAP users find that the server instance is retained after an update. This will likely depend on the particular location and nature of the Docker install in this case.
Did you follow the steps in this guide when you initially set up this server?
I had a closely related problem which after a lot of trial and error and frustration I have now sorted out.
I understand why ROON has shifted to container and I also understand the push to your own hardware. However, the attraction of ROON for many is that it is largely hardware independent and was really all about the software. Please bear in mind that for a user like me containers are completely new and we only have to use them for ROON. Hence we really do need “hand holding” and a very transparent process for updating. When an update fails the error message means nothing and there is no logical way to find a solution other than trolling through the posts to find someone who had a similar problem or lodging a support request. Having a warning message when an update is required which warns to “pull” (a completely new term to me) a new “image” (another new term) first and then “recreate” (another new term) the application would be a way to at least warn users that it was not simply a matter of clicking the update. By the next time I encounter a similar problem I will have forgotten all about this experience and a memory jogging warning message would be a great help.
Hi @derekrs, thanks for coming back, and no problem about the mixed up thread.
There is better news than you might expect. What you ran into was a specific defect affecting QNAP, not the normal state of Docker installs. It was tracked down in August and fixed in the Roon Docker image released on 13 August. Once you are on that image, updating Roon from inside the app works the way it does everywhere else, and you should not need to pull an image or recreate the application each time an update appears.
So the terms that were new to you are not something you will need to keep using. They were the workaround for a problem that no longer exists.
We will close this thread, since your issue is resolved and the other one is where it belonged. If an update does fail again, please start a new thread with the first few lines of your container log and we will take it from there.