There was an issue loading your database every few days

[benjamin]

Hi @Alan_Spool,

Thanks for the update!

@Alan_Spool

Then I got cocky and moved the 3 artists with large numbers of tracks back into the scanned folder, rescanned, cleaned the library and tried to do a backup. i got the corrupted library message again.

Which three artists are you referring to specifically? We may be able to review your Roon logs to better understand if there is a specific track/album causing this corruption.

Let me know, thanks!

[Alan_Spool]

@benjamin the 3 artists were Yo Yo Ma, Antal Dorati, and John Eliot Gardner.

I no longer am clear that this was the issue, I since tried many things, including briefly going back to the MacBook server, and then starting over on the sonic transporter after moving those artists out again. After several scans and restarts and cleaning up the library, I got a backup to work on the sonic transporter. However, then I set up automatic backups, and 4 days later my system had stopped again with the issue loading my database.

There is clearly something I don’t understand. Every scan seems to rediscover recordings I have had for many years. Meanwhile when I clean up my library, I find hundreds to up to 1606 deleted files when no files have been deleted since the last time I cleaned the library. Meanwhile, even trying to start from scratch, I have all my playlists. I can turn off backups. I can make all my playlists on Qobuz, and then I don’t have to worry about losing anything (I can always rescan the hard drive). It is continually irritating that rescans that happen all the time slow the system down so much, but i guess I can live with that.

So I have a number of requests to finish this off.

1. Is there a way to cleanly start over, delete the existing database, have it scan from scratch? I have lists of items in my playlists and I can repopulate them, which will take less time than I have been spending on this problem over months. I see no way to do this. There must be a way to make a clean start. Then we can see if a completely new database behaves better.
2. Is there a way to stop the system from constantly scanning the drive? I would like to turn this feature off and only turn it on after I have actually made changes. This would prevent the system from slowing every few hours.
3. Can you tell me if when trying number 1 above I should or should not include the 3 artists in the scanned folder mentioned above with >1000 tracks each?

[benjamin]

Hi @Alan_Spool,

@Alan_Spool

Is there a way to cleanly start over, delete the existing database, have it scan from scratch?

Follow the directions below:

Accessing the Roon Database on your sonicTransporter

I have been getting requests to access the Roon database on the sonicTransporter. There are two reasons users want to do this. to backup the database to move a database from an existing Roon Server In this post I’ll cover how to do this. Expose the Roon Database Before you do anything else you must expose the Roon database to a file share. Be careful! Once the database is exposed it can be deleted or destroyed. Go to the sonicTransporter web user interface from sonicorbiter.com go to Se…

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.

@Alan_Spool

Is there a way to stop the system from constantly scanning the drive? I would like to turn this feature off and only turn it on after I have actually made changes. This would prevent the system from slowing every few hours.

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.

@Alan_Spool

Can you tell me if when trying number 1 above I should or should not include the 3 artists in the scanned folder mentioned above with >1000 tracks each?

Based on what you’ve mentioned here -

@Alan_Spool

Then I got cocky and moved the 3 artists with large numbers of tracks back into the scanned folder, rescanned, cleaned the library and tried to do a backup. i got the corrupted library message again.

I would for now set these tracks aside to avoid any potential corruption during this process. You can always add them back in later

[agillis (Andrew Gillis)]

You can always delete Roon and reinstall it from scratch. This fixes all known issues with Roon. There are steps to do this on the sonicorbiter.com FAQ in the Roon troubleshooting section.

-Andrew

[Alan_Spool]

Deleting Roon and re-installing it completely solved this problem. I still have some work to do to recreate playlists lost in the process, but I exposed those so I have the original lists, so that should not be too bad.

The problem solved was not only the corrupted database message when backing up. Scans now are much more efficient and slow the system less. I also discovered where you could set the system to only scan on startup. The backups are also quite fast now. I added the directory I had moved the 3 artists with large track numbers as a separate directory to scan. This scan took place with no problem, and everything is still healthy. The verdict is that this database has been usable but sick for months. How it got that way and what bug it was exhibiting is a mystery. Hopefully it is rare enough @benjamin that you don’t have to deal with it much, but there is definitely a non-trivial programming issue here.

For my part, I hope that I am quite done.