Hi @Quicksilver,
Thanks for writing in and for sharing your report! Based on the description and screenshots, @Arlen may very well be correct in that this is a long-standing issue that has yet to be fully resolved for all users.
We were able to review a fresh Roon Server diagnostic report, and saw some interesting things we’d like to explore further.
First, we see your two SMB/CIFS network shares going offline (\Wishyouwerehere\music and \Wishyouwerehere\Uncompressed Music) at startup.
The shares finally mount successfully \Wishyouwerehere\music comes online a few moments later, and \Wishyouwerehere\Uncompressed Music as well. Roon rescans both.
But a few minutes later, around 01:52: Both shares go offline again (DirectoryNotReady), detaching within minutes of mounting. This triggers Roon to sweep those ~6,995 + ~674 + ~321 tracks (totaling ~9,000+ local tracks) as “deleted.” But Roon’s history has 40,000 play records loaded (you can see loaded 40000 plays), and since the library momentarily disappeared and reappeared, Roon’s database cleanup pass could be interpreting a large number of those historical entries as referencing now-deleted files.
So, it appears that the “40,000 deleted files” in Library Maintenance is Roon’s cleanup engine counting historical play records that point to tracks that were temporarily invisible when your NAS shares dropped off the network. It is not actual file deletion; your music files are safe. It seems to be a ghost cleanup artifact from the unstable SMB connection.
If you create a fresh backup, and then remove your play history, do you see the same number of tracks in your clean up library pop up?
We saw another interesting trace in your logs worth mentioning around the above issue:
loaded 40000 plays, 39,473 have tracks, 3,957 lib plays, 35,516 non-lib plays
Your 10,128 tracks are your local library. But you have 35,516+ “non-lib plays” in your history. These are tracks you’ve streamed from Qobuz, TIDAL, and nugs over the years that are not in your local Roon library.
When your SMB shares dropped at startup and Roon temporarily lost your local library, it may have showed all tracks from your play history as “My Tracks” combining your 10,128 local files with approximately 9,676 additional tracks from Qobuz/TIDAL streaming history that Roon had cached metadata for. That’s how you get close to 19,804.
Both issues trace back to the same root problem: your NAS (Wishyouwerehere) is mounting unreliably, with shares going offline within minutes of being available. You should investigate:
- SMB/CIFS stability on your NAS: check for timeout settings, sleep/hibernation of the NAS drives, or SMB version mismatches.
- Roon startup timing: Roon is starting before your NAS shares are fully available. Adding a startup delay or ensuring the NAS mounts before Roon launches would prevent this.
- Network initialization: The initial
Network is unreachable errors (for api.roonlabs.net) at startup suggest your network stack wasn't fully up when Roon launched, which may have cascaded into the SMB mount failures.
We’ll be on standby for your reply! 