Hi @Alan_Spool,
Follow the directions below:
Are you able to access the Sonicorbiter web interface and delete the database?
If not, stop Roon Server first, and then reach the Roon database via network share from your sonic transporter, and rename “RoonserverDB” to “RoonServerDB_old”. That should provide a fresh database for you.
This isn’t intended behavior, and is likely getting caught up on a certain track/tracks. That, or it’s losing connection with your NAS - triggering a rescan.
Based on what you’ve mentioned here -
I would for now set these tracks aside to avoid any potential corruption during this process. You can always add them back in later 