Are we able to download a pre-broken .QPKG file for QNAP just to get it back up and running temporarily? I got the new Docker running but I can’t seem to restore a backup properly, so I am out all of my playlists, etc. I’d like to get the old Roon running on my NAS, do a proper backup somewhere else, then restore into the new Docker version.
@Justin_Crosby if I understood it correctly, it is not possible to downgrade roon server on NAS to pre-2.65 version.
If you have an existing backup, it should be doable to copy the whole backup data into the /Roon-backup folder that has been shared with the container, and run a backup restore. You don´t need to create another backup.
If you don´t have any backup or it is very old, you can try installing roon server in the container, get it running, and subsequently replace the whole internal database in the container with a previous version from the RoonOnNAS folder. I have not tried this, but according to Roon staff member @vadim this should work:
Good luck!
With the help from Adrinal the backup is fully restored and all favorites, playlists, etc are back alive.
Many thanks!
3 Likes
I ended up moving Roon to a Docker container. Just a heads-up: after restoring the backup, you need to update the storage path and backup path — then all the media will come back.
Indeed. It’s important to re-associate your old path using the “edit this folder” link, i.e.:
Easy answer: to avoid spending 1k to 4k Euro or $ money on a new device, especially when you have a streamer/DAC connected via network (so no need to attach it directly to the NAS).
I ensure that with 8gb RAM the speed is totally comparable with a Nucleus One at least (I have a friend that owns one).
About 2k albums, 15k songs here
g
1 Like
Hi everyone,
I have successfully installed Roon Server on a QNAP TS-1655 using Container Station with the official image ( Package roonserver · GitHub ).
However, I have a problem: Roon does not detect any USB DAC.
Specifically:
-
Denon PMA-2500NE connected directly via USB to the QNAP
-
Another amplifier connected via USB to a Windows 11 PC
Interestingly, Roon does detect other Roon Ready devices (two Oppo UHD Blu-ray players), but USB DACs do not appear at all in Settings → Audio.
I have already tried the usual troubleshooting steps: restarting the Core, restarting the QNAP, unplugging/replugging the USB cable, reinstalling the Roon app on the phone, etc.
Is there a known issue with USB DACs when running Roon in Docker on QNAP? Has anyone managed to make a Denon PMA-2500NE (or any USB DAC) work with Roon in Container Station?
Thank you very much.
Yes of course.
And, did you rebuild the container if/when changes to the configuration were made?
Hi, I managed to run roon as a docker container as described by roon. However, I haven’t managed to access and load my old roon backups. I think I have added the right files in the docker-configurator, but it only shows empty direcories in roon running in docker. Has anyone any suggestions?
Also, I did not succed to add my Innous Zenith as a network folder, as it used to work before. I always receive an error when trying to add it (location: \\zenith\Music, user: guest, pw: innuos).
Any help is greatly appreciated.
Thanks!
Rainer
It seems you should mount it on the host (in which case the mounting has nothing to do with the container) and then use a path in the container configuration to pass the local mount to the container. Alternatively, enable the SMB option in the container config. Did you do either?
Thanks a lot, activating SMB mount support worked!
Also, I finally managed to load my old backup (coyping it into /container/roon-backups worked)
Thanks!
1 Like
My docker system works fine after the transistion, however I cannot use the USB output of my QNAP NAS although I have selected the related option in creating the yaml file.
Can someone help?
BTW: USB output worked well before the docker transition.
Thanks
Have you rebuilt the container after changing the setting?
I have not changed anything with the container. Did I miss something?
If you change the docker-compose file, via the configuration tool, you must remove the container and rebuild.
O.K., not sure that I understand this.
My existing container was newly created with the modified configuration file (USB function enabled).
What would be different if I remove the container and create a new one?
You said…
So, it is unclear if you built the container with USB passthrough, or changed the setting after building the container. To apply any changes to the configuration, the container must be rebuilt.
I built the container with USB passthrough, but USB does not work.
What is wrong? Any idea?