· Unable to index specific individual folders in QNAP Docker version
How can I configure the new docker version to only access certain folders on my QNAP NAS. I have my music divided into folders /music/jazz, music/rock etc? I also have some which I do not want to be indexed. This was possible in the previous version. I have created a docker version of Roon, restored a back-up (after copying it to the container folder – the instructions need to be more explicit here). But the new version did not show my local files, although I entered the correct folder (/music) in the configurator. In the iPad Roon interface, there is a message that all my previously entered folders were all unavailable. “Add Folder” came up with /Music as the only option. Selecting this sucked in all of the music files that I had on the NAS. When I go to “Folders” and click on /Music I can see all the folders on the NAS which are subfolders to my /music folder. Now, all the files have been reindexed and given today’s date. Please can you tell me how I can configure the system so that it will only index files from directories that I specify, and that this is done when I restore a back-up, keeping the original date of adding. Thanks!
I don’t think it is possible to preserve the original import dates, because the directory prefix of your music files changed; or you need to be creative and go through multiple trial & error iterations and hope to achieve that.
In your previous RoonOnNAS version of the server, i think you defined multiple storage locations (SMB shares exported by your NAS) which where mounted by Roon under subdir roonmnt in RoonServer QPKG ‘s install direcctory (in my case, that was /share/CACHEDEV1_DATA/.qpkg/RoonServer/roonmnt/Audio , where Audio was the name of my SMB share).
Theoretically, if you enable SMB support for the docker container (and don’t create the /Music volume mapping), after you restore the Roon backup you should be able to re-enable the original Music storage locations in Roon settings. BUT Roon will mount them in different paths which will not match the ones stored in Roon ‘s DB. Will this count as a new import because of the different OS/docker-container level mount-point (file location prefix), or the import date is linked to the storage definition and not the on-disk file-path? don’t know.
When you create your roonserver container, you can define more than one Music volume (one for each of the music directories you want to be indexed by Roon) - in the “RoonServer Docker Config Generator” web-page you can add more volumes (the + sign on the “VOLUMES REQUIRED” line).
NOTE: /Music is the default storage location automatically discovered / used by Roon. You can map jazz / rock / .. to subdirectories under /Music (ex: /share/music/jazz → /Music/jazz ; /share/music/rock → /Music/rock ; .. ) , and leave the default Music storage location as is in Roon (but you will no longer be able to filter your music based on storage location) or remove the default Music storage location in settings and define one for each mapped volume.
Please note that Roon does not match files by directory, but rather it matches it based on the music file’s fingerprint (hash function). If Roon only sees one copy of the same file at a time, it can match it up, so in your case it sounds like Roon possibly saw two copies at the same time. It may be best to restore to a backup and ensure that the correct folder is selected (and others disabled) so that Roon only sees the files once. If you are still having issues following this explanation, we kindly request that you share screenshots to help us clarify what is going wrong.
Roon is not finding my local files when I restore a backup. I presume that I have not correctly configured docker, but what exactly do I need to do? Here is a screen shot of my directory setup on the NAS. Everything is on one volume of an SSD drive. I have also included screen shots from my iPad looking at the storge screen.
mjw
(Father! Father! Resist not! Let us destroy the core! Set us free!)
5
You will need to update the storage locations since the mount point has changed to a folder in the container (that is mapped to the original location on the NAS.)
Thanks for the answer, but I don’t quite understand what you are suggesting.
I can access my local files, but only to re-index them. I want to restore a backup, and according to the instructions this should be possible.
However the restore process does not find the folders. Do I need to do something different in the Docker configuration or what do I need to do?
mjw
(Father! Father! Resist not! Let us destroy the core! Set us free!)
7
All the existing storage locations are no longer available, so you need to recreate them. It looks like you have mounted everything to /Music in the container.
Likewise, you need update the backup storage location to /RoonBackups.
Thanks for the update! @mjw is spot on correct with the above reply - since a few days have passed, I wanted to check in and see if you were able to get things sorted?
We’ll be monitoring for your reply and results. Thank you!
