After 2.0 upgrade getting “There is an issue loading your library” message

Support
1

Roon Core Machine

NUC i7 roon version 2.0 (build 1128)

Networking Gear & Setup Details

Router and everything is wired with cat 5

Connected Audio Devices

Bluesound POWERNODE

Number of Tracks in Library

Description of Issue

After updating everything to 2.0 (core and remotes) I’m stuck on the remotes at (see screen shot).

Going to my ROCK via IP shows all is good ( see screenshot).

Add images

image
image1920×1440 196 KB

image
image1920×1440 325 KB

2

Hi Nichoals,

Have you tried rebooting the core?

3

A core reboot sorted this for me, I actually needed to power off via the web page and then restart my core manually

2 Likes
4

I’ve tried multiple reboots by powering down via web interface and then hitting the power button on my ROCK unit to power back on. Same result.

In the past when there is an issue with the library there is an option to restore a backup (I back up to Dropbox).

But there are no options now. I’m confused.

5

How do I get someone from Roon to look into this issue for me? If it’s not resolved in a few days I’m canceling my subscription.

Thanks

6

Bumping this post up. @moderators, how do I flag this thread to support?

Thanks!

7

You can ping support by @support.

8

Hi @Nichoals_Bellomo,

The error indicates an issue with your database.

I decided to enable diagnostics and here is what I found. A log completely full of dropbox error messages!

The article I provided above should help with getting you back into Roon and leave you with the ability to address the drop box errors. It should also provide the information you need to bypass and restore a backup.

Wes

1 Like
9

Hi @Support

After doing the server reset I was able to connect with my app and my audio devices were available.

After restoring my back up no audio devices are found…

At this point the only way I can use ROON is start with a fresh database. Please advise.

10

Hi @Nichoals_Bellomo ,

Errors like the one you’ve seen now are signs of low-level corruption in the database. This means that the records Roon is reading from your database are different from what was originally written. This can happen for a number of reasons, like failing hard drives or an unstable power source (frequent outages, hard power cuts, etc).

We’re sorry you’re experiencing this extremely rare error: not only is our database infrastructure designed specifically to prevent this type of corruption, but starting with Build 880, Roon detects database corruption “on the fly”. So if corruption is detected during a backup or during normal use of Roon, you’ll be immediately prompted to restore from a backup.

What’s Next?

Install Roon fresh on your Core machine and roll back to one of your older backups. You can use these instructions to do so:

  • Stop RoonServer from running in ROCK’s WebUI
  • Navigate to your ROCK’s Database Location
  • Find the folder that says “RoonServer”
  • Rename the “RoonServer” folder to “RoonServer_old”
  • Restart the RoonServer in the WebUI to generate a new Roon database folder
  • On the Roon Remotes, press “Use another Core” and connect to the new database
  • (Optional) - Restore your database from a Backup prior to the issue starting

If you do not have any older backups, unfortunately, the only other solution is to use a fresh database.

11

This topic was automatically closed 36 hours after the last reply. New replies are no longer allowed.