I’ve just gotten unRAID 6.3 installed from 5 and am still figuring out the dockers. I installed the Roon docker as described in the first post but there is no option for port and volume mappings. unRAID says it is running and was downloaded but I have no way to access it that I can figure out.
Should I be installing on the docker page using the “add container” button or should I be using the Community Apps plugin? Any help would be appreciated. Thanks
I’d move the app and library folder to the same name _bak and the docker will create new ones.
Then go through and reconfigure in a client app.
This will of course remove your existing library files too, but you can move them back by moving the library dir back (although if you can it would be far better starting fresh, as you may get more problems in the future).
Thank you so much for the help… been out of sorts for a couple of days, but finally got around to doing a fresh installation… it’s building the library as we speak… let’s see how it goes… will report back in a few days!
A little history. My initial installation was without any “/library” and “/opt” paths. So I don’t know where the initial library is stored.
I installed it again as per the above, and the symptoms I’m having are this: Every now and then when I go to Tags or Artists, Roon Remote (running on a Galaxy Tab) seems to disconnect for a bit and then reconnects a couple seconds later. But the list is unpopulated.
Don’t know how to troubleshoot and see if it’s the server at fault or the tab. Will try running the remote tomorrow on my laptop and see.
I’m going to try to move my roon server from windows to unraid this weekend. I’d like to keep the database I created while on windows. I’ll back it up and then restore it into the roon core docker on unraid.
The database was created from multiple unraid user shares accessed by network paths, ie, //unraid/jazz and //unraid/rock. I expect roon core on the unraid box (hostname “unraid”) should be able to resolve these paths to itself during import, but it will probably be less than optimal if the new database keeps these network paths instead of local disk mounts. For example, it would be better if they were pointing to the /mnt/user/jazz and /mnt/user/rock shares, or better yet avoid fuse altogether and point to /mnt/disk1, /mnt/disk2, and /mnt/disk3.
Any insights from @support if roon import will do the right thing here?
How does the /music docker volume mapping play into this? Should I map it to a new user share that includes all disks, or as I do on windows, just disable and ignore the “Music Folder” storage entry that roon puts in the storage list? This is presumably how /music will show up in roon.
Finally, roon says to store the library on an SSD. Should the library volume (and maybe the application volume) be mapped to an SSD that’s outside the unraid array?
Roon doesn’t track files by path – each file is hashed and re-identified when you migrate your database to a new location and reimport your content.
Once you restore the database, make sure you remove the old watched folders or edit them to reflect the new paths – don’t leave the old folders in place and simultaneously add new folders for the new paths. That will cause problems.