I recently updated my network router which changed the network address of my NAS where my music is stored. My network share in Roon uses a fixed IP address to navigate to the shared music folder. This is now broken. Is it possible to edit this storage path rather than adding a new network share? I would prefer not to have Roon rescan everything from scratch which will take ages because I have a large library.
In Roon, go to Settings > Storage, click the “3 dots” menu and choose Edit to modify the storage path.
1 Like
I’ve already tried that. That just lets me delete the existing share and set up a new one. I’m trying to avoid that because Roon will then have to rescan everything which will take ages.
Can you change to a static IP on your NAS in your router (or NAS) to force the NAS to use the old IP?
Another option:
In the router can you “reserve” or Assign the IP Roon is looking for to your NAS?
Unfortunately no. It’s a different IP range.
That’s very odd. What you should get is something like this:
- Click the 3 dots menu:
- Click the Edit option to get this:
- Click the Browse button to be able to set up the new network address (by adding a new network share)
I have a feeling that even if you were able to modify the storage location that it will rescan the location.
I have been testing this with temporary storage locations that have the same albums in them (about 40 albums and 10 Gig) and then editing the location from one to the other and it rescanned after the edits. The initial scan of the first test location went as I would expect, it took a bit to identify the albums, but when I edited the link from the first location to the second test location the rescan went very quickly. I think because it had the information for those files already in the database it did not have to go get the information and identify the albums again.
I think you may need to just do it and see what happens. Just make sure you give the analysis as many cores as you can, under settings\Library, and then clean up the library after the analysis is done to get rid of any lost link entries in the database.
I think you’re right. It’s funny, this is the second time this issue has come up for me in the last couple of months and Roon’s behaviour was different each time. A month or so again we changed our Internet and cable provider which changed the IP range of the network. I had to set up a new network share and Roon scanned it. Even though the music collection didn’t change at all, Roon rebuilt the database which took a few days (I have a pretty large collection). This time I changed the router which again changed the IP range of the network. So once again I had to set up a new network share and was preparing for Roon to rebuild the database again. Accept it didn’t. It rescanned everything and I was up and running again in a few minutes. I’m not sure why it reacted differently to each of these situations.
1 Like
Are you saying it is up and running now? With only a few minutes of scan time? If so, that’s great!