Unable to Restore Backup on DietPi After Moving from ROCK (ref#L0CIJ2)

What’s happening?

· Other

How can we help?

· None of the above

Other options

· Other

Describe the issue

"No backups found" attempting to restore to DietPi NUC install. Backup originally created on ROCK.

I have moved from ROCK to DietPi (v9.18) roon server on the same hardware (NUC10i3). The DietPi install of roon is v2.56 (build 1582). The original backup from ROCK may have been roon v2.55 (build 1559).

Whenever I have attempted to restore the backup, I continually face "no backups found" message.

Things I have tried:
-- moving the location of the backup
-- copying the backup to a new location
-- checking permissions and "chmod -R 777" as a final resort

Still no luck in being able to restore. The backup files appear to be "just there" :) Any assistance in unblocking this restore is greatly appreciated.

Describe your network setup

Hardware: Intel NUC10i3, ethernet to router (Synology).

Hello @mookr,

Thank you for contacting Roon Support.

The “No backups found” message typically means that Roon Server cannot read or recognize the backup structure in the location you’re pointing to — even if the files are physically there. Let’s check a few things:

  1. Make sure you’re selecting the correct folder level.
    When choosing the backup location in the restore wizard, make sure you select the parent folder that contains the roon_backupt file.
    For example, if your backup is in:
/mnt/roonbackups/RoonBackups/

then select /mnt/roonbackups/RoonBackups, not the folder above or below it.
2. Verify file structure and permissions.
The correct backup folder should include several subfolders like 2d3f45ef-... and a _roon_backup_root_t file. Could you please confirm that your backup location looks like this?
Also, ensure that the user running Roon Server (usually roonserver in DietPi) has read access to that directory:

sudo chown -R roonserver:roonserver /mnt/roonbackups
sudo chmod -R 755 /mnt/roonbackups
  1. Try mounting the backup locally.
    If the backup resides on a network share (e.g. NAS), temporarily copy it to a local path on the NUC — for example /var/roonbackups/RoonBackups — and try restoring from there.
  2. Version compatibility.
    A backup made on build 1559 should restore fine on build 1582 — there’s no incompatibility between these two versions.

If possible, please share:

  • The exact path where your backup is stored
  • A quick ls -la output of that folder

We’ll review it and confirm whether the backup structure is being detected properly.

1 Like

Hi @vadim

Many thanks. Please find below responses to your queries.

Location of backups:

/mnt/dietpi_userdata/RoonBackups

Permissions: 
drwxrwxrwx  3 roonserver roonserver 4096 Nov  4 07:59 RoonBackups
/mnt/dietpi_userdata$ ls -l Roon*
drwxrwxrwx 259 roonserver roonserver 12288 Nov  2 21:05 3a9bf52d-4c2b-e82c-deb2-317c2ebc6141
-rwxrwxrwx   1 roonserver roonserver    19 Nov  2 21:05 _roon_backup_root_

ls -la output: 
/mnt/dietpi_userdata/RoonBackups$ ls -la
drwxrwxrwx   3 roonserver roonserver  4096 Nov  4 07:59 .
drwxrwxr-x  10 root       dietpi      4096 Nov  4 08:00 ..
-rwxrwxrwx   1 roonserver roonserver  4096 Nov  2 21:05 ._3a9bf52d-4c2b-e82c-deb2-317c2ebc6141
-rwxrwxrwx   1 roonserver roonserver  4096 Nov  2 21:05 .__roon_backup_root_
drwxrwxrwx 259 roonserver roonserver 12288 Nov  2 21:05 3a9bf52d-4c2b-e82c-deb2-317c2ebc6141
-rwxrwxrwx   1 roonserver roonserver    19 Nov  2 21:05 _roon_backup_root_

I notice your example root file is named _roon_backup_root_t – should there be a “t” on the end?

Many thanks.

Hi @mookr,

This looks like it’s possibly a nested target folder issue.

The restore path Roon expects is the parent directory, /mnt/dietpi_userdata, not /mnt/dietpi_userdata/RoonBackups.

The screenshot from the Backups screen you’ve shared shows you’re likely one level too deep. The roon_backup_root file is a marker — it tells Roon “this directory contains one or more backup sets.” So when you point Roon at /mnt/dietpi_userdata/RoonBackups, it looks inside that folder for yet another roon_backup_root, doesn’t find one, and reports “no backups found.”

When Roon says “Choose folder that contains your backup,” you should instead pick the parent directory, not the …/RoonBackups nested folder.

/mnt/dietpi_userdata

Roon should then see the roon_backup_root marker and show your list of available Backups.

Please let us know if this helps or if you’re still having issues.

Hi @connor

Thanks for your reply. Unfortunately, I have the same result when pointing to

/mnt/dietpi_userdata

I should note: I am just attempting to restore. There has been no other backup activity on this system at this time.

Many thanks.

That is how my setup look like

Torben

Hello @mookr

Would you kindly clarify under which user the Roon Server is installed?

Hi @vadim

I don’t recall if I installed as root or dietpi but the group “root” is on the roonserver dir, so likely root. However, Roon is running under the user roonserver.

I can reinstall. Any suggestions to ensure it’s a clean install path eg. as dietpi user?

Thanks.

Hello, @mookr

If this works, it is best to change the access rights to allow the root user to read this folder, or transfer ownership to it to verify the behavior.

Hi @mookr,

As long as you remove the old Installation directories, and install under the dietpi user, you should be good to go!

Then, under the dietpi user, run the installer:

sudo -u dietpi bash
cd /tmp
curl -O https://download.roonlabs.com/builds/RoonServer_linuxx64.sh
chmod +x RoonServer_linuxx64.sh
./RoonServer_linuxx64.sh
exit

This ensures /opt/RoonServer and related directories are owned by dietpi.

Let me know if this helps!

I have done chmod 777 on all files. Same result.

Does roon running under roonserver require root access?

@benjamin Thanks. Just to confirm, you are suggesting not installing via the dietpi installer (which is what I originally did)?

Update 1. root / dietpi reinstallation (using dietpi install)
Based on guidance to make sure things are owned either by root or dietpi, I have done two re-installations under both root and dietpi users. Unfortunately, the same outcome happened in both cases.

Update 2. Installing via linuxx64.sh
@benjamin the location of the script you reference has moved (got a 301), so need to ensure we do curl -O -L. After downloading, it executes with the following outcome:

<?xml version='1.0' encoding='UTF-8'?>NoSuchKeyThe specified key does not exist.
No such object: download-assets/builds/RoonServer_linuxx64.sh

I’m currently attempting to install via the linux instructions here and will be running the easy installer method as root, maintaining all defaults.

./roonserver-installer-linuxx64.sh

Will update when done.

I decided to use the “Restore a backup” at the initial prompt vs. logging in. The result? The same as before: “No backups found.”

I’m starting to wonder: could the backup be corrupt? Are there any methods to validate a backup?

Hello @mookr

Please follow the steps below:

  1. Zip up your RoonBackups folder (right-click it and select “Compress…”):
  2. Submit the .zip file to us through our Database portal

Hi @vadim

Many thanks - the zip file has been submitted.

(btw - this is on Dietpi - I used zip to compress; should be cross-platform.)

Thanks @mookr - we’ve shared your backup with our development team, who will inspect things further. We appreciate your ongoing patience here! :+1:

1 Like