Kilrah

No problem here, but probably depends quite a bit on the apps/integrations you use.

In the group field, type the group name you want instead of selecting one.

Power is unlikely to make a difference, temperature could, but I'd imagine more like the moving itself nugdged something enough to make a bad contact. Would try cleaning contacts/reseating the RAM first, CPU second, if still bad then RMA.

They changed ownership, you have to update them and rerun FCP.

Filesystem probably got hosed too badly then, likely not much choice but to move everything out, format and copy back.

Would check filesystem on the affected disk.

It's in the list of fixes for 7.2.1. Version 7.2.1-rc.1 2025-11-07 | Unraid DocsThis is a small update with some great fixes and improvements.

Uh, as you can see there's no package called "yq", the search returned all packages that include that in the name, if you want one of those you need to pass the full name...

Sometimes better to go with "time on battery". I.e. if the outage lasted more than 30 seconds it's unlikely to come back up, so initiate shutdown.

Should be able to assemble/export the image, then you can mount that wherever you want (obviously you need temp storage big enough to store the full uncompressed image) https://www.urbackup.org/administration_manual.html#x1-9400010.7 But yeah the point of image backups is to restore an existing machine as is easily and fully, not give easy access to individual files.

Might want to look at the zip manager plugin

That's the linux kernel version, not unraid version I'm not aware of it ever been possible to mount images within the container.

Normally no container should have a mapping to the whole of /mnt/user, only the required shares under it.

FWIW I updated and everything works fine for me.

AFAIK the timeout used is the global one set in Docker settings, might want to increase that

shfs is the process that provides /mnt/user i.e. merges the filesystems for all disks and pools. So yeah it's always there.

Whatever the reason was for the disk to be disabled again sadly isn't visible in the logs because the server was rebooted and the log of the previous run is incomplete because it's filled with overheating messages from your HBA. Would start by addressing cooling.

If you changed the destination how would it know about the old one anymore? It'll clean up in the configured destination folder.

Mine ran successfully today on 7.2.

CA on the website isn't live, it's just a static example that was taken as a snapshot sometime at the beggining of the year.

What are the drives? How are they connected? Diags suggest it's a virtual machine? If so they're probably not passed through correctly.

Try disabling auto-updates. AFAIK when the VPN container updates the others then can't find their dependency since the container got replaced by a new one. The Docker page update button takes care of that but maybe not this plugin. Could be that your manual tests are always close enough to the previous one that there haven't been updates inbetween, but there is after a week.

I send a copy of my appdata backups (so including the "main" flash backup) to another machine on my network. EDIT: and also to an external HDD that I plug to the server once in a while and uses an Unassigned Devices script to rsync the backup share to it.

Not a great thing to do, since it's zipped it's not usable as is anyway without taking it to a PC and extracting it, and that flash drive will get premature wear from all the writing.

Generally recommended not to use USB for array or pool drives for reliability reasons.