Roon auto-deleting tracks

Roon Core Machine

Windows 10, HP desktop, intel 8-core 3.6Ghz CPU, 64 bit, 32GB RAM

Networking Gear & Setup Details

Cox Cable provider router, WiFi and Internet, using Norton VPN

Connected Audio Devices

PS Audio DSD and QNAP NAS, all Ethernet connections

Number of Tracks in Library


Description of Issue

Have used Roon software almost daily for several years. Turned it on recently and page appeared that a software update required rebuilding the library. A few moments pass and the Home screen appears and I watch the number of artists/albums/tracks go effectively to zero (from over 2000 albums).

I’ve downloaded a current software copy and restored from backup. Same results on startup. Sometimes it doesn’t mention the need to update the database. 169 tracks contained in a file on the desktop are never “deleted”. Today 266 tracks were not “deleted” from the main file located on the NAS.

Not support but just a quick thought here.
Have you by any chance changed the location of your music directory?

Or by any chance after the new update is Roon not looking in the right location now for your music.
Settings: storage

No change in directory location. Room is “finding” 266 tracks contained in the file and treating the other 40,000+ as deleted.

Three more questions:

  • From what version of Roon were you updating, and to what version did the update complete?

  • The files are not physically deleted from your stored locations, correct?

  • Have you tried restoring from a backup, and if so, did the same behavior occur?

  1. Unknown
  2. Correct
  3. Yes. Same result.

OK, it’s good that the files are not being deleted. Two(ish) more questions:

  • Is your entire library stored on your NAS? Or do you have a mix of local files and streaming files?

  • Can you turn off your Norton VPN and see if you are able to load your library?

Hey @mistick,

Thanks for bringing this to our attention. For the next step, please use the directions found here and send over a set of logs to our File Uploader. If possible, provide a timestamp of when the issue occurred. That way, our team can pinpoint what might be happening at the time of the issue :+1: