No changes in my environment except for the usual ripping CDs or purchasing tracks in itunes and those files being added to the file system that roon scans.
This scan stuck happened a while ago but seemed to be fixed until recently.
This time, been sitting in this status for at least 12 hours. No changes to the count.
The log file shows essentially nothing happening.
I’ve resolved it before by restarting roon on my ROCK server but that’s annoying / worried about corrupting my database (as has happened before) and having to start from scratch with ingest (and losing all my metadata changes etc).
Thanks for the fast reply!
SoftRAID (which manages that drive) reports no I/O or other errors.
Stopped Roon, added tracks to my directory, restarted Roon and it added the tracks without problems (as it has when I had it running, added tracks, watched it get wedged, and then restarted it).
Network is stable for playback etc so don’t think that’s the problem (wouldn’t show up just during track scanning). Will swap the ethernet cable anyway.
Unless there are other ideas over time I’ll try both the “roon down” method and “roon up” method and see if I can spot any patterns. Worst case I guess if you suggest it is to shut down roon before adding tracks to my music directories…
Certainly let us know how it goes - I’m glad to hear things function properly with Roon Server temporarily off during import. Do you have success if you keep Roon Server on but temporarily disable the watched folder - import your files - and re-enable your watched folder?
Our team is investigating this issue further, and I should have more information to share next week.
No, disabling a storage device in Roon does not immediately remove all tracks from the database. Instead, Roon marks the tracks as unavailable, but their metadata remains in the library. If you *e-enable the storage device, the tracks should reappear as long as the file paths remain unchanged. However, if the storage is removed for an extended period or if the files are modified, Roon may treat them as new entries when re-added.