Had power outage that required me to reset all of my devices and basically start from scratch redoing my network and I have limited IT skills. I have an xfinity router set up up in bridge mode, a LUXUL EPIC 5 ABR5000 router, a LUXUL switch XMS-2624P, a Ruckus Zone Director 1200 with two 710 WAP’s, I have a Synology NAS DS918+ with 48 TB of storage using Seagtae Iron Wolf internal drives. I have a GRIMM MU1 streamer. Thankfully I had things backed up but it took me a week to figure everything out…well, almost everything. My issue and where I need some help is the working relationship between my Nas and Roon. When I reset my system it was giving out .5.114 IP address to the synology nas, problem was everything else was on a .0.## IP address and as a result my library went from 46K songs to 3K songs and Roon could not find the NAS as it was on a .5.114 IP. Therefore, my Roon/Grimm was not connecting to the NAS. Miraculously, after much trail and error I did my network up and after actually trouble shooting with synology they suggested a .0.## STATIC IP address. So, I did that and instantly they connected; however, my music was in a nice Music file and now it looks like
I can’t figure out how to get my original 46K songs back as now I can only see 43K after adding all the music folders one by one. To reiterate I am seeing my synology now that i have gone back to .0.### it is just that they are on a .5.### file from the synology…I think, because my system is still showing 6.5TB’s of music and I have not backed up.
This sounds like a network segmentation problem caused RoonServer to temporarily lose sight of the storage location. It began to re-index the library without those tracks available, but then re-added the storage location as a new filepath.
Since Roon monitors watched folders independently via filepath, RoonServer had no way to map the new filepath to the old filepath. RoonServer is likely stuck in the middle, attempting to index the library via the new filepath, but unable to locate all of the content it expects.
There are really two options here, depending on how granular you’d like to get.
If you are confident that the filepath’s you’ve added above do map to the location of all your original music files, then I would wipe the database, restore a Backup, and then map to these locations once more in Settings → Storage by re-adding the network share one more time.
Rename the “RoonServer” folder to “RoonServer_old”
Reinstall the RoonServer App from our Downloads Page to generate a new RoonServer folder
On the Roon Remotes, press “Use another Roon Server” and connect to the new database
Otherwise, you’ll need to check the files in the Synology using a file viewer and verify that the current filepaths are indeed correct. Also verify whether you’ve added multiple separate folders (e.g., /volume1/Music/Rock, /volume1/Music/Jazz) instead of the root music folder (/volume1/Music). You’ll then need to check “Skipped Files” for any content Roon might have failed to import during re-scanning.
The folder I have blacked out is Music and matches up to my synology NAS location. So it is not as easy as going into backups, restore from back up and selecting a back up pre-meltdown and restoring from that date?
Here is a copy under my library maintainance, clean up library, NOTE the 2369 files that are not associated with a storage location. Could those be the files 43147 + 2369 = 45516 that gets me to my total tracks?
This is how many files I was able to get over.
@vadim I checked and verified the files are in tact and there. I also discovered that under my backups folder. I then went into Roon and noticed that some backup file existed. I then deleted my old NAS file that was .5 and redid my .0 ip addresses that contained Music. After that I went into one of my older backups in mid April before my system melted down and restored from backup. I now have all 45,000 tracks back. So my system is back up and running properly.
