· I have ROON server on a QNAP NAS and the ROON App on an Android Tablet playing to a Cyrus Stream XR. The App and server are the same version: 2.65 (build 1653) production. The NAS and Cyrus are on a wired network and the tablet is WiFi. It all worked fine and then I went on holidays and when I came back it didn't work. The App is stuck on "looking for the ROON server" and never finds it. Entering the NAS IP address makes no difference. Using BluOS from the same tablet and using the same music files on the QNAP NAS everything works fine. So the network is not a problem. I have uninstalled the server and the App and then reinstalled everything (several times) and this makes no difference. Rather than have a magnifying glass going around for ever, it would be useful if you provided some informative diagnostics when things are obviously not working. How do I solve this problem?
Tell us about your home network
· Router: tp-link Archer MR600 2 UniFi Flex Mini switches No VPN in use
I have no idea what a “container” or a “docker” is.
The instructions provided by ROON seem to assume engineer level understanding.
Particularly for long time NAS users (and subscription payers) this is a very big change which should have been handled much better.
Is everything now in the “container” ?
Can i now safely delete my “old” ROON database?
I missed the inconspicuous bit in the instructions that said to “restore from backup”, so I am now starting from scratch and have lost all my carefully curated playlists created over many years.
I agree that communication on this was not top notch and there are lessons learned here for Roon.
Someone from Roon support will pick up this case and assist you further, but one question, did you have a regular Roon backup setup on your QNAP? If yes you should be able to restore everything one you have setup Roon in docker.
It’s my understanding that you have to restore from a backup made from Roon server software. I.e, have a regular backup schedule scheme setup inside roon. I do think Roon bugs you about if if you don’t start one.
Roon support can confirm if there are any workaround when there is no proper backup.
I completely understand your frustration. The transition to the new Docker-based setup for QNAP has been a significant shift, and the lack of explicit warnings regarding backups beforehand is a valid criticism.
While we typically recommend restoring from a built-in Roon backup, there is a manual workaround we can try to rescue your existing raw database and recover your carefully curated playlists.
Please perform the following steps to manually migrate your old database into the new Docker environment:
Create the Docker Container: Follow the official QNAP Docker guide to set up the new Roon Server container.
Crucial Detail: Pay close attention to the folder mappings in your configuration. You need to remember the exact folder path on your NAS where you are telling the container to save its data (this is the path on the left side of the colon : in the volume configuration).
Stop All Roon Services: Once the new container is created, stop it. Next, go to the QNAP App Center and ensure the old, native Roon Server application is also completely stopped.
Locate the Old Data: Using QNAP’s File Station, navigate to the directory where your old native Roon installation stored its data.
Copy the Database: Inside that old Roon storage location, locate the folder specifically named Database. Copy this entire folder.
Paste into the New Location: Navigate to the new host folder you designated for the Docker container in Step 1. Paste the copied Database folder directly into this new location, replacing the existing folder
Restart and Connect: Start the Docker container again. Open your Roon Remote app, connect to the server, and log in.
If the folder was placed in the correct directory, the new Docker container will read your old database upon startup, and your previous library state and playlists will be restored. Provide an update once you have attempted this file transfer.
/share/DataVol2/Container/roon-backups:/RoonBackups
restart: unless-stopped
logging:
driver: local
This is the log
tar: RoonServer/RoonDotnet/shared/Microsoft.NETCore.App/10.0.7/System.Security.Cryptography.Cng.dll: Cannot write: No space left on device
tar: RoonServer/RoonDotnet/shared/Microsoft.NETCore.App/10.0.7/System.Security.Cryptography.Csp.dll: Cannot write: No space left on device
tar: RoonServer/RoonDotnet/shared/Microsoft.NETCore.App/10.0.7/System.Security.Cryptography.Encoding.dll: Cannot write: No space left on device
tar: RoonServer/RoonDotnet/shared/Microsoft.NETCore.App/10.0.7/System.Security.Cryptography.OpenSsl.dll: Cannot write: No space left on device
tar: RoonServer/RoonDotnet/shared/Microsoft.NETCore.App/10.0.7/System.Security.Cryptography.Primitives.dll: Cannot write: No space left on device
tar: RoonServer/RoonDotnet/shared/Microsoft.NETCore.App/10.0.7/System.Security.Cryptography.X509Certificates.dll: Cannot write: No space left on device
tar: RoonServer/RoonDotnet/shared/Microsoft.NETCore.App/10.0.7/System.Security.Cryptography.dll: Cannot write: No space left on device
tar: RoonServer/RoonDotnet/shared/Microsoft.NETCore.App/10.0.7/System.Security.Principal.Windows.dll: Cannot write: No space left on device
tar: RoonServer/RoonDotnet/shared/Microsoft.NETCore.App/10.0.7/System.Security.Principal.dll: Cannot write: No space left on device
tar: RoonServer/RoonDotnet/shared/Microsoft.NETCore.App/10.0.7/System.Security.SecureString.dll: Cannot write: No space left on device
tar: RoonServer/RoonDotnet/shared/Microsoft.NETCore.App/10.0.7/System.Security.dll: Cannot write: No space left on device
tar: RoonServer/RoonDotnet/shared/Microsoft.NETCore.App/10.0.7/System.ServiceModel.Web.dll: Cannot write: No space left on device
tar: RoonServer/RoonDotnet/shared/Microsoft.NETCore.App/10.0.7/System.ServiceProcess.dll: Cannot write: No space left on device
tar: RoonServer/RoonDotnet/shared/Microsoft.NETCore.App/10.0.7/System.Text.Encoding.CodePages.dll: Cannot write: No space left on device
tar: RoonServer/RoonDotnet/shared/Microsoft.NETCore.App/10.0.7/System.Text.Encoding.Extensions.dll: Cannot write: No space left on device
tar: RoonServer/RoonDotnet/shared/Microsoft.NETCore.App/10.0.7/System.Text.Encoding.dll: Cannot write: No space left on device
tar: RoonServer/RoonDotnet/shared/Microsoft.NETCore.App/10.0.7/System.Text.Encodings.Web.dll: Cannot write: No space left on device
tar: RoonServer/RoonDotnet/shared/Microsoft.NETCore.App/10.0.7/System.Text.Json.dll: Cannot write: No space left on device
tar: RoonServer/RoonDotnet/shared/Microsoft.NETCore.App/10.0.7/System.Text.RegularExpressions.dll: Cannot write: No space left on device
tar: RoonServer/RoonDotnet/shared/Microsoft.NETCore.App/10.0.7/System.Threading.Channels.dll: Cannot write: No space left on device
tar: RoonServer/RoonDotnet/shared/Microsoft.NETCore.App/10.0.7/System.Threading.Overlapped.dll: Cannot write: No space left on device
tar: RoonServer/RoonDotnet/shared/Microsoft.NETCore.App/10.0.7/System.Threading.Tasks.Dataflow.dll: Cannot write: No space left on device
tar: RoonServer/RoonDotnet/shared/Microsoft.NETCore.App/10.0.7/System.Threading.Tasks.Extensions.dll: Cannot write: No space left on device
tar: RoonServer/RoonDotnet/shared/Microsoft.NETCore.App/10.0.7/System.Threading.Tasks.Parallel.dll: Cannot write: No space left on device
tar: RoonServer/RoonDotnet/shared/Microsoft.NETCore.App/10.0.7/System.Threading.Tasks.dll: Cannot write: No space left on device
tar: RoonServer/RoonDotnet/shared/Microsoft.NETCore.App/10.0.7/System.Threading.Thread.dll: Cannot write: No space left on device
tar: RoonServer/RoonDotnet/shared/Microsoft.NETCore.App/10.0.7/System.Threading.ThreadPool.dll: Cannot write: No space left on device
tar: RoonServer/RoonDotnet/shared/Microsoft.NETCore.App/10.0.7/System.Threading.Timer.dll: Cannot write: No space left on device
tar: RoonServer/RoonDotnet/shared/Microsoft.NETCore.App/10.0.7/System.Threading.dll: Cannot write: No space left on device
tar: RoonServer/RoonDotnet/shared/Microsoft.NETCore.App/10.0.7/System.Transactions.Local.dll: Cannot write: No space left on device
tar: RoonServer/RoonDotnet/shared/Microsoft.NETCore.App/10.0.7/System.Transactions.dll: Cannot write: No space left on device
tar: RoonServer/RoonDotnet/shared/Microsoft.NETCore.App/10.0.7/System.ValueTuple.dll: Cannot write: No space left on device
tar: RoonServer/RoonDotnet/shared/Microsoft.NETCore.App/10.0.7/System.Web.HttpUtility.dll: Cannot write: No space left on device
tar: RoonServer/RoonDotnet/shared/Microsoft.NETCore.App/10.0.7/System.Web.dll: Cannot write: No space left on device
tar: RoonServer/RoonDotnet/shared/Microsoft.NETCore.App/10.0.7/System.Windows.dll: Cannot write: No space left on device
tar: RoonServer/RoonDotnet/shared/Microsoft.NETCore.App/10.0.7/System.Xml.Linq.dll: Cannot write: No space left on device
tar: RoonServer/RoonDotnet/shared/Microsoft.NETCore.App/10.0.7/System.Xml.ReaderWriter.dll: Cannot write: No space left on device
tar: RoonServer/RoonDotnet/shared/Microsoft.NETCore.App/10.0.7/System.Xml.Serialization.dll: Cannot write: No space left on device
tar: RoonServer/RoonDotnet/shared/Microsoft.NETCore.App/10.0.7/System.Xml.XDocument.dll: Cannot write: No space left on device
tar: RoonServer/RoonDotnet/shared/Microsoft.NETCore.App/10.0.7/System.Xml.XPath.XDocument.dll: Cannot write: No space left on device
tar: RoonServer/RoonDotnet/shared/Microsoft.NETCore.App/10.0.7/System.Xml.XPath.dll: Cannot write: No space left on device
tar: RoonServer/RoonDotnet/shared/Microsoft.NETCore.App/10.0.7/System.Xml.XmlDocument.dll: Cannot write: No space left on device
tar: RoonServer/RoonDotnet/shared/Microsoft.NETCore.App/10.0.7/System.Xml.XmlSerializer.dll: Cannot write: No space left on device
tar: RoonServer/RoonDotnet/shared/Microsoft.NETCore.App/10.0.7/System.Xml.dll: Cannot write: No space left on device
tar: RoonServer/RoonDotnet/shared/Microsoft.NETCore.App/10.0.7/System.dll: Cannot write: No space left on device
tar: RoonServer/RoonDotnet/shared/Microsoft.NETCore.App/10.0.7/WindowsBase.dll: Cannot write: No space left on device
tar: RoonServer/RoonDotnet/shared/Microsoft.NETCore.App/10.0.7/createdump: Cannot write: No space left on device
tar: RoonServer/RoonDotnet/shared/Microsoft.NETCore.App/10.0.7/libSystem.Globalization.Native.so: Cannot write: No space left on device
tar: RoonServer/RoonDotnet/shared/Microsoft.NETCore.App/10.0.7/libSystem.IO.Compression.Native.so: Cannot write: No space left on device
tar: RoonServer/RoonDotnet/shared/Microsoft.NETCore.App/10.0.7/libSystem.Native.so: Cannot write: No space left on device
tar: RoonServer/RoonDotnet/shared/Microsoft.NETCore.App/10.0.7/libSystem.Net.Security.Native.so: Cannot write: No space left on device
tar: RoonServer/RoonDotnet/shared/Microsoft.NETCore.App/10.0.7/libSystem.Security.Cryptography.Native.OpenSsl.so: Cannot write: No space left on device
tar: RoonServer/RoonDotnet/shared/Microsoft.NETCore.App/10.0.7/libclrjit.so: Cannot write: No space left on device
tar: RoonServer/RoonDotnet/shared/Microsoft.NETCore.App/10.0.7/libcoreclr.so: Cannot write: No space left on device
tar: RoonServer/RoonDotnet/shared/Microsoft.NETCore.App/10.0.7/libcoreclrtraceptprovider.so: Cannot write: No space left on device
tar: RoonServer/RoonDotnet/shared/Microsoft.NETCore.App/10.0.7/libhostpolicy.so: Cannot write: No space left on device
tar: RoonServer/RoonDotnet/shared/Microsoft.NETCore.App/10.0.7/libmscordaccore.so: Cannot write: No space left on device
tar: RoonServer/RoonDotnet/shared/Microsoft.NETCore.App/10.0.7/libmscordbi.so: Cannot write: No space left on device
tar: RoonServer/RoonDotnet/shared/Microsoft.NETCore.App/10.0.7/mscorlib.dll: Cannot write: No space left on device
tar: RoonServer/RoonDotnet/shared/Microsoft.NETCore.App/10.0.7/netstandard.dll: Cannot write: No space left on device
tar: RoonServer/Server/Base.dll: Cannot write: No space left on device
tar: RoonServer/Server/Broker.Messages.Core.dll: Cannot write: No space left on device
tar: RoonServer/Server/DnsClient.dll: Cannot write: No space left on device
tar: RoonServer/Server/ICSharpCode.SharpZipLib.dll: Cannot write: No space left on device
tar: RoonServer/Server/JetBrains.FormatRipper.dll: Cannot write: No space left on device
tar: RoonServer/Server/JetBrains.HabitatDetector.dll: Cannot write: No space left on device
tar: RoonServer/Server/JetBrains.Profiler.Api.dll: Cannot write: No space left on device
tar: RoonServer/Server/LevelDb.Database.dll: Cannot write: No space left on device
tar: RoonServer/Server/MessagePack.dll: Cannot write: No space left on device
tar: RoonServer/Server/Messaging.dll: Cannot write: No space left on device
tar: RoonServer/Server/Metadata.Messages.dll: Cannot write: No space left on device
tar: RoonServer/Server/Roon.Messages.dll: Cannot write: No space left on device
tar: RoonServer/Server/Roon.ServiceProxy.Base.dll: Cannot write: No space left on device
tar: RoonServer/Server/Roon.ServiceProxy.DeviceMapService.dll: Cannot write: No space left on device
tar: RoonServer/Server/RoonApp.PlatformTools.dll: Cannot write: No space left on device
tar: RoonServer/Server/RoonApp.dll: Cannot write: No space left on device
tar: RoonServer/Server/RoonBase.dll: Cannot write: No space left on device
tar: RoonServer/Server/RoonServer: Cannot write: No space left on device
tar: RoonServer/Server/RoonServer.deps.json: Cannot write: No space left on device
tar: RoonServer/Server/RoonServer.dll: Cannot write: No space left on device
tar: RoonServer/Server/RoonServer.runtimeconfig.json: Cannot write: No space left on device
tar: RoonServer/Server/Sentry.dll: Cannot write: No space left on device
tar: RoonServer/Server/System.CodeDom.dll: Cannot write: No space left on device
tar: RoonServer/Server/System.Management.dll: Cannot write: No space left on device
tar: RoonServer/Server/System.Security.Permissions.dll: Cannot write: No space left on device
tar: RoonServer/Server/System.Windows.Extensions.dll: Cannot write: No space left on device
tar: RoonServer/Server/VERSION: Cannot write: No space left on device
tar: RoonServer/Server/libleveldb.so: Cannot write: No space left on device
tar: RoonServer/Server/libroonbase.so: Cannot write: No space left on device
tar: RoonServer/Server/processreaper: Cannot write: No space left on device
tar: RoonServer/Server/relaunch: Cannot write: No space left on device
tar: RoonServer/VERSION: Cannot write: No space left on device
tar: RoonServer/check.sh: Cannot write: No space left on device
tar: RoonServer/start.sh: Cannot write: No space left on device
tar: Exiting with failure status due to previous errors
Roon Docker image 1.0.6 starting.
VERSION file at /Roon/app/RoonServer/VERSION is empty — treating as no existing install.
Resolved ROON_INSTALL_BRANCH=‘production’.
No install present; installing branch ‘production’.
Downloading from https://download.roonlabs.net/builds/production/RoonServer_linuxx64.tar.bz2…
Had the same issue, and I solved it by removing the volume alias names from the path, the top-level folder name is sufficient:
/share/Container/roon:/Roon
/share/Music Nas 2:/Music
/share/Container/roon-backups:/RoonBackups
I assume your /Container folder as used by Container Station, is on an SSD volume, and there is no second top-level folder of the same name on /DataVol1? The latter situation should be avoided, in this case it would be better to set up a new top-level folder, for example named /RoonInContainer on the SSD volume, and route to that one instead of /container
If you are uncertain regarding correct folder path syntax, feel free to share a screenshot of your volume´s and top-level folder´s names in File Station.
Space is not the issue here, but insufficient rights of Container Station to write anything into that folder, and seemingly invalid folder syntax in the share path as well.
After uninstalling and reinstalling Container Station & Roon Server a few times it now seems to be working as intended. When setting-up Container Station it is essential to ensure that the “Container” folder is created on the Volume you want it to be. From there on your instructions work.
I am still not completely clear why “roon-backups” is created inside the container which also contains the original database. Is this a ROON requirement? Normal practice I would have thought would have been to create the backups in a different location (ideally on a different volume or NAS)?
This has worked to the extent that I now have my playlists with the correct tracks and album art.
However, all the tracks are labelled “Unavailable” in red.
Can this be fixed?
A few points:
There are many folders called “Database”. I assumed you meant the top folder with that name - was that correct?.
The old data base contained a folder “bin” and a file with suffix “.log.txt”. I did not copy these into the new location (ie I only copied the folders “RAATServer”, “RoonGoer” and “RoonServer”. Was this correct?
Could you go to roon Settings > Storage pls, and check, if the main music folder is disabled? It is the one pointing roon to the new share path. You might see remnants of non-existent folder paths from the previous install being unavailable.
I would recommend to do a fresh database backup first, and then remove all the unavailable folders, before enabling the new path. This might help roon identifying the new location of your existing albums.
