Kilrah

Then post in that plugin's support outlet so that the maintainer can help you/fix it if necessary.

Why aren't you using one of the checkmk client containers available in apps?

What Unraid Version? Did you install the Python3 plugin?

if checkmk is a container then nothing on the host affects it in the first place.

That one's redundant That shows Plex does not have any configured appdata path, so it seems the Plex template itself is configured wrong, unrelated to this plugin. There should be an appdata path, that would then show with the "Internal volume" icon and be backed up. I was asking for checking on unraid itself in its file browser or terminal in case whatever method you used to copy to your external drive skipped some stuff. But it's moot, the issue is above.

You still didn't show how you set it up. What are the container-specific settings? What data is on the set destination itself? How does stuff end up on your I: drive? That wouldn't be the plugin doing it. Plugin does what it should unless configured wrong.

That shows only firefox being backed up. But that doesn't seem to be on the destination directly, seems like a copy somewhere else that may or may not include everything for some reason.

What's in the folders? What's the scheduling set to? You told it to keep 3 folders and you have 3 (plus something that's probably from something else than this plugin from back in 2023).

Not gonna work, since they're SATA you can't pass them fully without passing the entire controller to a VM. You'll have to run another OS if you want to flash them. You might be able to do that from iDRAC, most allow booting an OS to install a blank system. There would be quite significant risk of something going wrong so back up everything first of course.

XFS seems to keep crashing when trying to mount it. Possible the enclosure was not transparent and the drives won't be readable outside of it, i.e. would have to put them back in, offload all the data somewhere else before putting the drives back in natively and reformatting/copying back.

1) Seems it wants you to point to a directory, not the file itself. Probably needs the whole folder and structure extracted from the download without change. 2) How are they assigned in unraid? 3) Typically no. Larger drives being faster is common, data more dense on the platters, same rpm leads to higher speeds. I would not update firmware on drives without a full backup and physical access.

Do the disks show unmountable? Post Main page screenshot

No, it's been transferred to the unraid org. https://github.com/unraid/recycle.bin

Got removed some time ago, see footer bar or tools->preclear.

Did you install the virtio drivers yet?

[Template only, I am not the container author/maintainer] Project: https://github.com/owntone/owntone-server Registry: https://hub.docker.com/r/owntone/owntone Template: https://github.com/kilrah/unraid-docker-templates/raw/main/templates/owntone.xml OwnTone is a media server that lets you play audio sources such as local files, Spotify, pipe input or internet radio to AirPlay 1 and 2 receivers, Chromecast receivers, Roku Soundbridge, a browser or the server’s own sound system. Or you can listen to your music via any client that supports mp3 streaming. You control the server via a web interface, Apple Remote, an Android remote (e.g. Retune), an MPD client, json API or DACP. OwnTone also serves local files via the Digital Audio Access Protocol (DAAP) to iTunes (Windows), Apple Music (macOS) and Rhythmbox (Linux), and via the Roku Server Protocol (RSP) to Roku devices. OwnTone was previously called forked-daapd, which again was a rewrite of mt-daapd (Firefly Media Server). Host/br0 networking is required for use with hardware playback devices.

If that is a container it it should not be affected by what's installed / require you to install anything on unraid itself. You should also use its support thread for questions.

My understanding is those scripts are run by the plugin when it updates containers, standard manual update from the stock Docker page wouldn't know about any of this and bypass it all.

Flash drive backup is in the folder with the rest, so gets deleted with the folder. Sounds like you set an additional flash backup destination for a 2nd copy, if that's really what you want then it's yours to manage.

If you run the appdata backup plugin make sure you didn't enable autoupdate in that.

Found it:

Within the Docker system, when the container is created Docker looks up the name you gave to find the network ID and that's what it stores as the container network. But when the service is stopped/restarted the default br0 is recreated as a new network so the ID changes. Try turning on "Preserve user-defined networks" for a start but IIRC that's not enough.

Type a group name, save settings, then it'll be available to choose for others.

Click on container, set "Member of group", then you'll have them in a separate group you can reorder.

On each boot Unraid creates a new br0 so it'll have a different ID. The existing container still references the old one so won't start without doing a compose down/compose up to associate the new network with the same name. There's a trick to create your own macvlan/ipvlan network instead of using the system-provided one and to set Docker to preserve custom networks, should be somewhere in this thread.