· None of the above quite fits
· None of these quite match
· Files marked as unavailable in playlists
· tp-link router, unifi switches, no VPN
In “Storage” there are 2 Storage Folders shown.
As far as I can tell they are both exactly the same location and exactly the same files.
The first location “Music Folder” cannot be removed and the storage location cannot be edited.
The second location “NAS7E9F85> >/ Music” can be removed and the storage location can be edited.
With both folders enabled ROON tells me I have twice as many tracks (30,772) as shown in the folders (15,386).
If I disable the first location everything looks normal (ie . number of tracks = 15,386 and tracks in playlists all there). Under “Library - Maintenance” it shows 17,234 tracks to be cleaned up.
If I disable the second location everything looks normal except all the tracks in my playlists are marked as “unavailable”. Again under “Library Maintenance” it shows 17,234 tracks to be cleaned up.
How do I remove the duplicated Storage Folder and keep the tracks in my playlists available???
Why the difference between 15,386 tracks shown in the folders and 17,234 tracks shown to be cleaned up???
The first location is the share path you have specified when running docker generator, so to speak the new primary music folder.
The second one seems to be the old, non-existent (inside the container) file path as used by RoonOnNAS installation, which only exists as a result of restoring a backup. You seem to have successfully pointed to the new share path, so it has recognized all the previous tracks, edits and links to playlists.
That is to be expected, as you had already pointed roon to the new location of the previous folders when restoring the backup, so it recognized these as your existing ones, not the “Music Folder” stuff (which in the end of the day is the same files twofold).
Fast way: disable the main “Music Folder” and keep it disabled.
If you don´t want that, keep it disabled, in the first place, restore a backup from RoonOnNAS times, subsequently delete remnants of the old folder path which roon marks as ´unavailable´, and only then enable the new Music Folder. With the previous paths being deleted prior to roon scanning, it should identify the existing tracks and that they have been moved to a new location.
Both methods works, the second bears a risk of a few tracks being not recognized.
Unfortunately I don’t have a backup from RoonOnNAS.
But with only “Music Folder” enabled I can see the playlists, just the tracks are marked unavailable.
The tracks are only stored in 1 location and “Music Folder” can see the tracks and play them.
So it must be a bug in ROON that the tracks are marked as unavailable in the playlists.
Can this be fixed?
Hello @derekrs,
Thank you for the detailed screenshots and explanation! @Arindal is spot on about what is happening under the hood here.
To answer your question: this isn’t exactly a bug with Roon’s playlist logic, but rather a side effect of how Docker mounts volumes compared to how Roon’s database remembers file paths.
When you migrated to Docker and restored your database, Roon remembered the exact file path to your music from your old native NAS app (NAS7E9F85...). Your playlists are firmly tied to that specific path. However, your Docker configuration (the docker-compose.yml file) automatically forces a hardcoded volume mount into the container, which Roon sees as the undeletable “Music Folder”. Because this new mount points to the exact same files, Roon scanned them as brand-new files rather than recognizing them as your old ones.
Since your playlists are mapped to the old NAS path, disabling that old path makes the playlist tracks “unavailable.”
The Fix: You cannot delete the “Music Folder” from inside the Roon UI because it is hardcoded into the container’s configuration. However, we can simply edit the container configuration to mount an empty folder instead. This allows you to keep your working NAS path (and your playlists) without duplicating the tracks.
Here is how to do it:
Roon_Empty_Mount).docker-compose.yml file (or your container configuration UI, depending on how you set it up).- /share/YourActualMusicFolder:/music.- /share/Roon_Empty_Mount:/music.The Result: When you open Roon, the undeletable “Music Folder” will still be there, but because it is now looking at an empty directory on your NAS, it won’t scan any duplicate tracks. Your original NAS7E9F85 path will remain the only active source of your music, keeping your playlists perfectly intact.
Once this is done, you can safely go to Settings > Library > Clean Up Library to clear out those 17,234 ghost tracks for good!
Hi Vadim
I followed some of your advice from the other thread - Roon Labs Community
Roon app unable to connect to server after holiday (ref#39WEFF)
I clicked on the 3 buttons next to some of the playlist tracks and selected edit - nothing changed.
Then when I went back to the main playlist screen there was a green diamond (like for signal path) next to each playlist (which hadn’t been there before). When i clicked the diamond it asked if I wanted to relink the tracks and I clicked yes. Then when I went into the track lists for each playlist 99% of the tracks were now linked correctly!!!
There was no apparent reason for the few tracks still marked as “unavailable” as the files were all still present in the correct locations. However, it was a fairly quick process to go through and delete these tracks from the playlist and then reinsert them.
When I look now there is no longer any green diamond next to the playlists. Did I imagine it or is this a feature of ROON? Can you show me where it is described on the website?
Anyway, I am very glad that I am finally back to where I started before this botched upgrade.
Thank you
Hello,
This feature is also known as the playlist improver.
Introduced a while ago and designed to upgrade your tracks in the playlists.
I am glad to hear that the issue is solved and you are back up and running.