i would like to ask if there is any solution? i experience same issue at the moment.
A few days ago, i have made a completely new database, i felt everything was slowing down and didnt work properly anymore, so i backed up my database and made a complete new one.
Im running my core on a QNAP NAS 473, Database is on an internal SSD Drive
After 3 days of scanning and importing roon stuck with cirlce constantly spinning and this numer of tracks:
I was setting up a new Roon backup on a Western Digital My Mac Passport, 2TB drive. After setting back up times and a force backup to update now, the drive began copying “something”, along with a small arcing circle spinning in upper right corner of the screen.
When I went back to check my content there were hundreds of copies of something, albums that I MAY have listened to but certainly didn’t mark as favorites.
I tried a force quit of Roon, but opening up again found it to be doing the same thing. I finally unplugged the external drive and everything returned to normal, even my content in my library.
I won’t try this again with the WD drive. Some direction and acknowledgment from ROON support would be helpful.
If you could post a screen shot of the files that would be helpful. Roon’s backup doesn’t copy over music, it copies over the database. Unlike a sql database you might be used to, a Roon database backup is made up of thousands of directories, sub-directories and small files.
When you set the backup, you should have pointed it to a section of the drive which is NOT watched by Roon for music.
Can you please upload the logs to Dropbox, Google Drive or a similar service instead? Please be sure to turn on “sharing by link”, instructions on how to do so for Dropbox can be found here and for Google Drive can be found here.
Thanks for sending those logs over! It looks like Roon is getting stuck on a file that contains special characters in the file name, but it is not clear what file is causing this issue exactly. Can you please reboot your Roon Core, let it run until you get this issue, and then send us a new set of logs? Hopefully, after the reboot, the logging is more clear. Let us know, thanks!