I've been running this UnRaid server with very few problems for 4 or so years now.  Absolutely love UnRaid.  Due to the lack of problems, I am not a very strong troubleshooter...  A couple days ago we had some power outages occur.  My UnRaid server should have shut down gracefully as it is on a UPS and configured to shut down at 50% battery but it seems it failed to do so.  When I turned it back on I was unable to access Radarr WebUI.  Tautulli and Overseer seemed to have lost their database too because they are acting as if I just installed them freshly.  Radarr logs say I should restore from backup but I don't know how to do that without a WebUI.  I can't find instructions to do so.  Radarr WebUI tells me "refused to connect" when I try to access it.  I have tried in a few browsers and all give me the same result.

I noticed my network interfaces status state the following: (not sure what the status was before the power outage - could this be a factor?)

bond0 = fault-tolerance (active-backup), mtu 1500
eth0 =  interface down
eth1 = 1000 Mbps, full duplex, mtu 1500

I also noticed there was stuff stuck on my cache drive.  It looks like the docker image and the docker appdata folders are both on my cache drive.  I stopped all dockers and ran the move operation.  It cleaned up the cache drive quite a bit but did not solve my problems.  
/mnt/cache/system/docker/docker.img
/mnt/cache/system/libvirt/libvirt.img 
/mnt/cache/appdata

I don't see anything very helpful in the UnRaid system logs.  I did download the UnRaid diagnostics before and after the move operation, in case that gives any clues.

Any recommendations on next steps would be sincerely appreciated.  

nas-diagnostics-20241111-2253.zip
nas-diagnostics-20241112-1942.zip
 

do you have a backup?
this sounds more like docker libvrit coruption.

 

Let’s troubleshoot your UnRaid server issues step-by-step, especially since you've had a power outage that likely affected some critical services.

 

Step 1: Network Configuration Check

Since you noticed issues with bond0 and eth0 after the outage, let’s start by checking and resetting your network configuration, as network issues could be affecting access to your Docker containers:

Check Network Settings: Go to the UnRaid WebUI, then go to Settings > Network Settings. Verify that:

bond0 (your network bonding) is correctly set up.

eth0 should not be showing as "interface down." If it’s down, try re-enabling it or switching to eth1 temporarily.

 

Restart Network Services: Sometimes, restarting the network services on UnRaid can help resolve issues. You can try restarting UnRaid or, if you have console access, use:

/etc/rc.d/rc.inet1 restart

ifconfig eth0 up

 

Step 2: Rebuild Docker Image

If your Docker containers (like Radarr) aren’t accessible, they might have been corrupted by the ungraceful shutdown. Rebuilding the Docker image can often fix these issues:

Stop the Docker Service: Go to Settings > Docker and disable the Docker service.

Delete and Rebuild Docker Image:

Go to /mnt/cache/system/docker/ and delete the docker.img file.

Re-enable the Docker service in UnRaid, and it will recreate the docker.img file.

Reinstall Containers: Go to Apps, navigate to your “previous apps,” and reinstall Radarr, Tautulli, and Overseer. This should pull the existing configurations if appdata is still intact.

 

as data should still exisit in appdata...

Step 3: Restore Radarr Database

Since Radarr is prompting for a restore from backup, let’s locate the backup files and manually restore them:

Find Radarr Backups:

Navigate to /mnt/user/appdata/radarr/Backups/ (or similar). There should be backup files if Radarr had its backup feature enabled.

 

Restore Backup Manually:

Stop the Radarr Docker container.

Locate the most recent backup .zip file and extract it to /mnt/user/appdata/radarr/.

Start the Radarr container again.

see:

 

Step 4: Address Cache Drive Issues

If some appdata was stuck on the cache, it could indicate an incomplete mover operation:

Ensure Mover is Working: With all Docker services stopped, run the mover manually and confirm that everything is correctly transferred off the cache:

 

run mover...

Check Docker and Appdata Locations:

Ideally, the Docker image and critical appdata should be on the array or on an SSD cache drive. Make sure Use cache disk for shares is set to Only or Prefer if they’re intended to be on cache.

 

Step 5: Review Diagnostics and Logs

If issues persist, checking diagnostics and system logs can help:

Check UnRaid Logs:

In the UnRaid WebUI, go to Tools > System Log to see if there are any error messages after the reboot.

Review Docker Logs:

For each Docker container (like Radarr), go to Docker > Radarr > Logs and see if there are any error messages related to startup issues.

 

Edited November 14, 20241 yr by bmartino1

This is great. But does anyone know how to setup Radarr to create a scheduled backup. Sonarr has this ability. Would be great if Radarr did this.

Edited March 27, 20251 yr by roblewis

it should be enabled by default. You can view that in system/tasks menu

Basically it's the same as in sonarr.

Edited March 28, 20251 yr by caplam

I have to assume you are following trash guides for setup...

Review:
https://trash-guides.info/File-and-Folder-Structure/How-to-set-up/Unraid/

https://trash-guides.info/Radarr/

https://trash-guides.info/Sonarr/

 

and server wiki:
https://wiki.servarr.com/en/radarr
 

Radarr automatically performs scheduled backups of its database to safeguard your configuration and data. These backups are executed at regular intervals and are enabled by default. To manage and access these backups within the Radarr interface, navigate to System and then select Backup. Here, you can initiate a manual backup by clicking the Backup Now button, restore from a previous backup using the Restore Backup option, or download existing backup files for external storage.

--https://wiki.servarr.com/radarr/system
 

When running Radarr as a Docker container on unRAID, it's essential to ensure that the backup files are stored in a location that persists across container restarts and updates. This is typically achieved by mapping Radarr's /config directory to a persistent volume or a host path on your unRAID server. By doing so, all configuration files, including backups, are retained even if the container is recreated.

 

For a comprehensive guide on setting up Docker containers, including Radarr, on unRAID, you can refer to the TRaSH Guides. This resource provides detailed instructions on folder structures, volume mappings, and other best practices to ensure data persistence and system reliability.

--https://trash-guides.info/Prowlarr/ and https://trash-guides.info/Radarr/

 

By ensuring that Radarr's configuration directory is correctly mapped to persistent storage on your unRAID server, you can maintain regular backups and safeguard your media management setup effectively.

 

Then use plugins and other linux tools to back up data you have on unraid. Such as appdata backup plugin.