@vadim @benjamin @noris are there any new developments on your end that would help me here?
Hello @DNack
Two things from you, and then we will send you the finished file, and you will not have to build anything yourself.
First, the part of Step 1 is still outstanding. In that permissions list, every shared folder has its own row. We need the row named Container and whether RW is selected for it. Your screenshots show the screen, but not that row, and the account appears disabled in one image and enabled in the other, so we cannot tell what the state is.
Control Panel, then Privileges, then Users, edit the account, Edit Shared Folder Permissions, scroll to the row named Container, and send a screenshot of that row with RW visible. If RW is not selected, please select it and apply. Your screenshots show the screen but not that row, and the account appears disabled in one image and enabled in the other, so the state is not clear to us.
Please leave your admin account enabled for now. We do not know which account the container runs as, so turning it off could remove the access we are trying to grant.
Second, the real paths. This is the one piece we cannot work out for you. A screenshot of File Station is not enough, because it shows the share names rather than the actual path, and your music sits on more than one volume, so each folder has a different one.
In File Station, right-click a folder, choose Properties, and note what it shows. You are looking for something in this shape:
/share/CACHEDEV1_DATA/Music
/share/DataVol2/Multimedia
Please do that for each of these:
roon, insideContainerroon-backups, insideContainer, creating it first if it is not there- every folder that holds music, however many that is
Send them as text or as screenshots, whichever is easier. If a folder gives you something that does not look like the examples above, please send it anyway, and we will work it out.
Then we send you the complete file with your paths already in it, and all you do is:
- Container Station, open the dropdown next to Explore, choose Create Application.
- Name it
roon-server. Lowercase only, no spaces or capitals, or it will refuse to build. - Paste our file into the YAML box and press Validate. You want a green checkmark.
- Press Create, and wait for the task to finish.
- Open the container’s Logs and paste the last twenty lines here, whatever they say.
When it starts it will look like a brand new server with an empty library. That is expected, and we will bring your existing library across afterwards. Your original RoonServer app stays installed and untouched until then.
I will do my best to show you the detail around how I cannot see this container file row as you suggest.
- Container Station is running, and the ‘roonserver’ app seems to also be running, ‘somewhere’ [see screenshot]
- Control Panel > Privileges > Users > ADMIN has been enabled [screen shot verification below]
- Clicked on ‘Edit Shared Folder Permission’ and this is what is checked [below screen shot]
*** After doing the above, I clicked into ‘Shared Folders’ and subsequently enabled ‘guest’, and also then checked ‘Read/Write’ and then it seemed to show the ‘Container-Station’ hierarchy [see screenshot]
Now after allowing ‘guest’ access Read/Write my QNAP is crashing. I now seem to be making my existing 872 NAS worse, and not even functioning …
Is this some sort of joke that you are playing on me? This is unacceptable, I have no idea how to stop the system from ‘spinning’ …
@vadim @benjamin @noris this is from QNAP support …
"Hello Daniel,
Your issue is that ROON suddenly created a random folder within the root share directory. Is this in regards to the new ROON update or is this something you did? There is not supposed to be anything in the root “share” directory or it causes the NAS to not work properly. This appears to be their app database and information. We cannot remove this share because we do not know if this app database may cause ROON within container to stop functioning. We would recommend you getting a backup of the music files just in case."
I just followed the initial instructions, which seemed to have placed the container somewhere that it was not supposed to live.
@vadim @noris @benjamin are there any devlopments for my QNAP docker/container install?
my 872xt is running stable now, do you have a next step for me? I have a substantial amount of sunk cost into Meridian, QNAP servers and iPads in my walls that Roon Labs was running on … I think it’s been about a month w/o service, what is the latest?
Hi @DNack,
Thank you for your patience. This has been an arduous process for you and we’ve escalated this case to ensure we resolve it as soon as possible. You have our apologies this has taken so long.
Let’s take a step back and provide a little context on what’s happening, because this thread has grown technical and verbose.
When Roon Server starts for the first time on this QNAP, it unpacks its installation files to a path inside the Container you created. That path is supposed to be a pointer to a real folder on your NAS, but it never resolved to one in this case. Rather than failing, Docker created an inside the Container’s own storage, not on the system volume. This container storage is tiny and quickly overfills when Roon Server unpacks the installation files. This is the “random folder on root share” to which QNAP Support is referring.
It’s also why the unpack kept failing with “No space left on device,” and why the container restarted continuously despite showing no memory consumption. Your SSD was never actually full, and your hardware is fine. Removing the Container stabilized the NAS, which corroborates that was the problem.
We have two housekeeping items and then one quick step. These are separate from any support steps with QNAP.
In Control Panel → Privilege → Shared Folders, turn guest access back off on the share you changed. Enabling guest Read/Write is what destabilized the NAS, and Roon does not need it.
Leave the old RoonServer app installed and stopped. Do not uninstall it. Your existing library database lives with it, and that is the only thing here that cannot be replaced.
In File Station, right-click each of these folders, choose Properties, and note the full path exactly as shown. It will look like /share/CACHEDEV1_DATA/Music. I need your roon folder, your roon-backups folder, and every folder your music lives in, including any on other volumes.
Post that list here as text. Pause there and we will share next steps.
@vadim @benjamin @noris Stanley from QNAP went into my NAS and removed and reconfigured to enable the NAS to install the new docker/container. See below for our records.
It appears I was able to now connect to this new Container therefore I am now at Step #6, however I have a new challenge. It’s as if my Roon system is being set up ‘as new’ and doesn’t remember any of my zones, etc.
Can we just restore my Roon from a Backup or something? I have like 12+ zones I had all of these preferences saved … Now that my Roon Server seems to be running in this new Container can you see that I have initialized and shifted the license from my old server? My main Roon App on my Mac Pro is up but not playing any music. I was able to successfully login to Tidal, Qobuz but I only show 749 artists normally I believe I have > 10k something is off
@connor @vadim @benjamin @noris good morning happy Thursday. Seems Roon on my iMac Pro [App] is syncing with the roon-server [in docker container], I pasted the YAML below:
services:
roonserver:
image: Package roonserver · GitHub
container_name: roonserver
network_mode: host
environment:
- ROON_INSTALL_BRANCH=production
- TZ=America/New_York
volumes: - /share/Container/roon:/Roon
- /share/Music:/Music
- /share/Container/roon-backups:/RoonBackups
restart: unless-stopped
cap_add: - SYS_ADMIN
- DAC_READ_SEARCH
security_opt: - apparmor:unconfined
- label:disable
logging:
driver: local
Can we set up my Roon from a Backup so it’s just like prior to this migration? please advise, I am around 100% and committed to completing this migration appreciate in advance
@connor @vadim @benjamin @noris Hello there team I am working with QNAP I believe they found the legacy settings, does this help? /share/ZFS530_DATA/.qpkg/ROONServer
I really would like to get my Roon instance up and running as it was prior to this migration, I now have full confidence that the prior settings exist on my QNAP and all of the music files are safe … we just need to re-map it and I’d appreciate this assistance.
Hello @DNack
Yes, this is recoverable, and a backup is the clean way to do it. One question first.
Were Roon backups running before you moved to the container? Roon writes them to a folder called RoonBackups, wherever you pointed it at the time. That would be somewhere on your NAS shares, not the roon-backups folder in your new YAML, which the container created empty.
If you find one, everything comes back: your twelve zones, playlists, favourites, play history and settings. Here is the procedure, and the section headed “If you’re restoring to an existing Roon Server” is the one that applies to you:
Two things from that page worth knowing before you start. Select the RoonBackups folder itself rather than one of the dated folders inside it. And after the restore, go to Settings, then Storage, and edit the existing music folder to the container path /Music rather than removing it and adding a new one. Playlists and play history are tied to that entry, and editing the path keeps them.
If there are no backups, please tell us and we will work with the old installation instead. You have confirmed the previous data is still at /share/ZFS530_DATA/.qpkg/ROONServer, so there is a route through that. It is not something we would hand you as a set of instructions to run alone, so we will take it step by step with you here.
Either way, please do not make further changes to the container or the storage settings until we know which of the two we are doing.
@vadim @connor @benjamin @noris I do strongly believe the answer is ‘yes’ due to the following screenshots, I am not a programmer or versed in the following screen shots or how QNAP ‘files’ these folders however all of my QNAP issues began roughly 1 month ago. Accordingly I see the following location(s) for ‘Backups’.
Furthermore, the latest ‘timestamp’ on the last backup appears to be 08/01/26 timeframe which is about when I started having issues. See below:
It appears I have a few additional ‘backup’ locations that date even back to my initial migration from Sooloos to ROON, but my assumption is that the latest Backup above would be sufficient?
Please let me know thoughts and instructions as per above I will do my best to implement ASAP
Hey @DNack,
Thanks for the screenshots, that’s exactly what we needed to see, and it does look promising. Before we point you at the restore, we want to confirm one detail, because this is the step where a wrong assumption costs the most.
The dates visible in your screenshot are from 2024 on both RoonBackup and RoonOnNAS. That doesn’t necessarily mean the backups are old, a folder’s date often doesn’t change when files are written inside a subfolder , but we can’t yet see the backups themselves. Could you open RoonDB → RoonBackup → RoonBackups and send a screenshot of what’s inside, with the Modified Date column showing? That tells us in one glance how recent your newest backup is.
Two other things while you’re in File Station. First, right-click and choose Properties on each of these, and paste the Location line as text: the RoonBackups folder, the RoonOnNAS folder, and every folder that holds music (Roon Music, Multimedia, Music Export, External MQA Files, Sooloos). They’ll look like /share/ZFS530_DATA/RoonDB/… rather than the short names in the sidebar. We need the real paths because of the second point.
Your container currently has no access to those folders. The configuration you posted maps only /share/Container/roon, /share/Music and the empty /share/Container/roon-backups, which is why your library shows 749 artists instead of your full collection, and it also means the restore screen won’t be able to find your backups yet. Once we have the paths above, we’ll send you one corrected configuration that maps your real backup folder and all of your music folders, and that will be the last rebuild.
One safety step in the meantime. Please make a copy of the RoonBackup and RoonOnNAS folders somewhere else on the NAS. Your library exists in those two places and nowhere else, and there has been a lot of reconfiguration on this machine recently. If the backups turn out to be older than you’d like, RoonOnNAS is very likely your original database and we can recover from that instead, so we want both protected before we touch anything.
Also, if guest access is still switched on from the earlier steps, please turn it off in Control Panel → Privilege → Shared Folders. That was what destabilised the NAS, and Roon doesn’t need it. Leave the old RoonServer app installed and stopped as before.
Nothing else needs changing on the container or in Settings until we’ve seen those paths.
@benjamin @vadim @connor @noris here is the snapshot(s)
Two other things while you’re in File Station. First, right-click and choose Properties on each of these, and paste the Location line as text: the RoonBackups folder, the RoonOnNAS folder, and every folder that holds music (Roon Music, Multimedia, Music Export, External MQA Files, Sooloos). They’ll look like /share/ZFS530_DATA/RoonDB/… rather than the short names in the sidebar. We need the real paths because of the second point.
I don’t fully understand 
above but I will do my best.
like this? above
