Manual backup of database failed at 1:42:41 AEST in Sydney (ref#2D1E8D)

Hi! What’s not quite right with Roon?

· None of the above quite fits

None of the above quite fits

· None of these quite match

Tell us what's going on

· Getting backup failed when doing manual back up of database. Time AEST (Sydney Australia)1:42:41

Tell us about your home network

· Use a Grimm MU-1 and a Synology NAS. Telstra Router.

Hey @Neville_Kapadia,

Thanks for sending this in. We were able to review fresh Roon Server logs and here’s what they show.

The failure isn’t caused by the backup destination. Every backup attempt since 10/21 has failed at the same point, whether it was going to your HEAP drive or your Synology. Roon Server can’t read one file inside its own database on the MU-1’s internal storage:

broker_4.db/LOG.old

That file is only a log and holds none of your library data. However, the error suggests the file or the storage it sits on has been damaged, so Roon Server stops the backup before it copies anything. Restarting hasn’t cleared it.

Your logs also show that the restore attempts from the NAS failed because part of that backup is missing. That means there’s currently no complete backup to fall back on. Until this is fixed, please don’t try any more restores or reset anything on the MU-1.

Next steps:

  1. Because the MU-1 is a closed appliance, this file needs to be removed with Roon Server stopped. Please contact Grimm support and pass on the file path above. They can clear it, and they can check the internal storage for errors if needed.
  2. Once that’s done, run a manual backup to your NAS again and let us know the result.

Separately, Roon Server has also flagged a few hundred WAV files on the HEAP drive as possibly corrupt, mostly in the “Sanjiv 2018” folder. It might be worth checking that drive’s health as well.

Let us know how you get on with Grimm, and we’ll take it from there.