Backup not found issue during restore on new Grimm MU2 (ref#42SAJS)

Hi! What’s not quite right with Roon?

· Music won’t play or issues with my library

Music won’t play or issues with my library

· Trouble creating or restoring backups

Tell us what's going on

· I bought a new server and when I try to restore it says no backup found. I backed up from my Innuos Zenith to a USB hard drive, then plugged it into my new Grimm MU2.

Tell us about your home network

· Ubiquiti

Hey @Wynne_Walker,

Thanks for the details, and congratulations on the new Grimm MU2, the logs show it’s up and running perfectly as a Roon Server (it’s licensed, playing music, and already making its own nightly backups). So the hardware and setup are all healthy. The “no backup found” message is coming from one specific thing.

The backup on your USB drive appears to be an Innuos backup, not a Roon backup, and Roon can only restore from backups that Roon itself created.

These are two different things that are easy to mix up. The backup tool built into your Innuos Zenith saves the Innuos device, its own settings plus your music files (that’s the folder on your drive named like backup-017681, with “system” and “music” inside it). Roon’s own backup, on the other hand, saves your Roon database your playlists, edits, play history, tags, and audio settings. When Roon looks at the drive, it reads through the Innuos folder, doesn’t find a Roon backup inside it, and reports “no backup found.” Your drive is fine and fully readable, it just doesn’t contain the type of backup Roon needs.

Here’s how to get your library moved over:

If your Innuos Zenith still turns on and runs Roon: This is the ideal path. On the Zenith, open Roon and go to Settings → Backups, then create a backup there (you can save it to the same USB drive or to a network folder). If you’d previously set up scheduled Roon backups on the Zenith, even better, those already exist and you’d just copy that backup folder to the drive. Then on your MU2, go to Settings → Backups → Restore and point it at the folder that contains the backup. Your restore points will show up and you’ll be back exactly where you left off.

If the Zenith is no longer available: Unfortunately the Roon library itself can’t be rebuilt from an Innuos backup, so you’d start with a fresh Roon library on the MU2. The silver lining is that your actual music files are safe inside the “music” folder on that USB drive, we can walk you through copying those over and adding them to the MU2 so your collection is right back where it should be.

One quick question so I can point you the right way: did you ever run Roon’s own backup on the Zenith (Settings → Backups), or was the USB backup made only through the Innuos backup tool? That tells me immediately whether we’re recovering an existing Roon backup or setting up fresh.

Happy to stay on this with you until it’s sorted. :+1:

Thanks for the quick reply. That all makes sense. I still have the Zenith and will create a Roon backup.

I have two other questions:

  1. On the new Grimm, when I search, it says “Can’t connect to Roon search.”

  2. I have never been able to connect Roon to my Ubiquiti NAS. It always says “There was an unexpected error. Invalid network path.”

Hey @Wynne_Walker,

Thanks for your patience, I pulled the fresh logs from the MU2 and have answers on both counts. Good news on the search one.

The NAS connection

I found the exact moment this failed, and it’s a smaller problem than it looks. The path that was entered was:

smb://192.168.0.35

That’s the IP address of the NAS, but it doesn’t include the share on that NAS, so Roon Server rejected it as incomplete before it ever tried to connect. That’s what’s behind the “Invalid network path” wording. Nothing is actually wrong with your network or the NAS itself.

What Roon needs is the machine and the folder being shared, like this:

\\192.168.0.35\Music

…where Music is replaced with whatever the share is actually called on your Ubiquiti NAS. You’ll find that name in the UniFi Drive interface; it’s the name of the shared folder you set up there.

A couple of things worth confirming while you’re in there:

  • SMB sharing is switched on for that share
  • There’s a username and password on it. Roon connects far more reliably to a share with real credentials than to an open/guest share, so if it’s currently set to allow anonymous access, creating a dedicated user with read access is worth the two minutes.

Then in Roon: Settings → Storage → Add Network Share, enter the full path above along with the username and password.

If it still refuses once the share name is included, send me a screenshot of the share settings from UniFi and I’ll take it from there.


"Can't connect to Roon search"

This one turned out to be a genuine bug, and I think it’s already fixed.

Despite what the message says, it wasn’t a connection problem at all. There were a handful of stale album entries in your library database that Roon’s search index was still pointing at. When a search happened to touch one of them, search would fail internally and never return anything, and the app reports that dead end as “Can’t connect to Roon search.” Searching for “bill” or “billy” hit it every time, which is likely what you ran into.

The Roon 2.71 update that installed on your MU2 on the evening of August 5th cleaned those stale entries up. Every search in your logs since then has completed normally.

Could you try searching again, specifically for “bill” or “billy,” the ones that were failing, and let me know what you see? If it’s still happening, tell me and we’ll go a step further.

One related note for when you restore the backup from the Zenith: if search starts misbehaving again afterwards, let me know right away. It would suggest those stale entries also exist in the Zenith’s database and came across with the restore, and we’d want to handle that differently rather than have you chase it twice.

One thing I noticed that you haven’t mentioned, your scheduled Dropbox backups have been failing since the morning of August 6th. Roon’s authorization with Dropbox has expired, so every backup attempt since then has been rejected, it’s been retrying quietly in the background without success.

Given that this whole conversation started with a backup, I’d rather you know now than find out later. The fix is quick:

Settings → Backups → remove the Dropbox backup location → add it again and re-authorize when Dropbox prompts you.

Your last successful backup was August 4th, saved locally on the MU2 itself, so nothing is lost.

Let me know how the NAS path goes and whether search is behaving now, and we’ll keep going from there. :folded_hands:

Thanks for the help!

Backup restored … NAS added … backup scheduled to NAS … search is working now!

Hello @Wynne_Walker

Thank you for the update.

Glad that you have sorted this out. We are closing this thread. Feel free to raise a new one in case of any questions or concerns.