I’d like to use another external hard drive as my music storage.
It has the same content as my current drive, after I connect the new drive should I use a backup of the previous drive’s Roon database to avoid having to generate a new one?
In Roon, Settings/Storage disable the drive you are going to remove. Remove the drive. Attach the new drive. Under Storage, there will be an edit (in blue) to edit the old location to the new attached drive. After a quick rescan everything should be ok.
I have noticed that when I’ve done this previously, Roon scans the new drive and seems to take many days to complete. While this procedure is taking place Roon is very slow and almost unusable.
Is there anything else I can do to avoid this?
Ahh, I was hoping to avoid the interminable Roon scan , is my Nucleus+ a NAS, sorry of course it’s not. I do have a WD mycloud EX2 Ultra which i could never get working with Roon
I’ve less than 10,000 tracks on Tidal, the rest are mine. I’ve always had large libraries. Vinyl, Cd , cassette and now digital.
I used to own a record store for 20 years which helped fuel my music addiction
I don’t have/never have used rock, but I’m wondering why it wouldn’t act the same as RoonServer, since it is basically RoonServer for Linux…
@Rugby, I am under the impression you are very familiar with ROCK… will below work anything below work?
There should be some reboots/start or stop server that are not listed. This is just a concept based off of what I have done using RoonServer when the external storage is moved to a new drive/location.
This may work for me as I:
I Use RoonServer (not rock)
and
I create a folder on the root level of my external storage drive and do not use a default location.
I Once again I do not and have not used rock.
And again… I do not know if rock will work this way… but I it know it will cause RoonServer to not find the storage location initially, which I do intentionally.
Now if you can use a custom folder path on the external drive when using Rock, I do not see why this wouldn’t work:
When initially setting up your external storage… keep your album folders in a dedicated folder on the root level of the drive called audio.
Disconnect the external drive and clone it.
Then rename Audio to Audio2.
When attached to the core, the core will not find the storage location because the name was changed.
So then just redirect it in Settings → Storage to the new location.
The core should not have to do the identifying album rescan.
It should just to a quick scan for verification of albums.
Well, your question isn’t about ROCK per se, but RoonServer. As far as I understand, ROCK is the RoonOS running basically the same Linux RoonServer.
ROCK’s RoonServer does not automatically map a watched location on an external USB drive. However, it will automatically use ALL of an internal storage drive as a watched location (which is why you shouldn’t make a Roon database backup to an internal storage drive).
So, for ROCK, if you plug in a USB drive, you have to setup a watched storage location on it. This should be a sub-folder, like Music, and not the whole drive. This allows you to create different folders on the drive and only have RoonServer watch those you want it to.
This allows the user to create a sub-folder like Backups, and not have it being watched. This is also a reason I suggest the use of external drives as it makes it easier to do Database Backups; otherwise you are having to setup a network location as a backup destination.