JonathanM

Did you get an auto reply? If not try sending again. Generally containers put their executables and other common program parts inside the docker.img file, and their customizable parts live in ./appdata/* and the templates are on the flash drive. Do you have any backups of the flash drive? If you only had a single parity drive in Parity1, then data drive order doesn't matter. If for some reason you had that parity drive in Parity2, then order does matter. The two parity slots use different calculations.

Pick one app to work on, read the first post in that app's thread and follow the troubleshooting steps. When you have the appropriate log file, read through it and XXXX out any credentials then post it in that app's thread with a description of what you have done so far and where you are getting stuck. Since you say you have the same issue on multiple containers, I'm betting if you fix one, you can easily figure out how to deal with the rest.

Restore it from your last flash drive backup.

There are at least 5 different implementations of nextcloud, each with their own support areas. Please click on the nextcloud icon in the gui and select the support item, then read and post in that specific area.

I don't know if the time being wrong will give that error, but try setting the BIOS time to GMT. You should be able to save the diagnostics zip file to the flash, shut down the machine, then attach the zip file to your next post here.

According to your previous screenshot you aren't using that file.

80% is about 16GB, not 737GB

I don't understand what you think is wrong, everything looks good to me.

Everything will only be files not in use, so to get "everything" moved you need to stop the docker and vm services in settings. You will know when the services are stopped because the docker and vm tabs will be missing from the GUI.

Motherboard reported, may be accurate, maybe not. fixed allocation by Unraid It's the percentage of space used INSIDE the docker.img file. Not the free space on the drive holding the image file.

Use the 6.12.10 files, overwrite everything on the USB except the config folder. Make sure you keep the config folder, make a backup of it before you do anything else.

Pretty sure that didn't work like you thought it did, because those locations are the same. /mnt/user paths are the combined view of all the root paths on the array disks and the pools combined. user share and disk share should never be mixed in a file operation.

It does, I use it extensively, each of my VM's runs apcupsd in slave mode, and is set to begin shutting down a minute or two after the host server reports a loss of power. Server shutdown is much smoother for me if the VM's are all shut down before the server itself starts the shutdown sequence.

Block the entire 140.210.*.* network in your firewall.

Ask your ISP if they put you on a CGNAT address. If so, ask if they can put you back on a direct internet address instead.

I just thought of a another VERY good reason I want the parity drive to be read all the way to the end. Hidden errors. Unless you run a complete SMART test, that portion of the parity drive beyond the last data drive is NEVER read or written during normal use. The last thing I want is for there to be a bad sector lurking in the last bit of the parity drive, just waiting for me to add a data drive and start exercising it. At least with a parity check that portion of the drive is read regularly. Count me as 1 vote to keep the current behaviour, for the above reason alone.

Just be glad that one of your current data drives wasn't in use as a parity with that old backup. That sort of error is generally fatal to the data that was on said drive. Lesson here, keep current backups, and delete any old backups made before a drive change. You really don't want to accidentally use an old backup.

If that were implemented, it would require a change in the drive addition and replacement code, because it would no longer be a given that the full capacity of the parity drive is indeed zeroes. I don't see that kind of code rewrite happening, mainly because what is there now works, and mucking around with such important code that is currently working would require a VERY strong reason, given the amount of work needed to test for edge cases and general bugs that could be introduced.

Try a different USB stick. It's possible the GUID for the stick you tried isn't usable.

This video is rather old, but covers the basic principles. "Cache yes" terminology is not used anymore because it was confusing, it's been replaced by primary and secondary along with the direction mover should act.

https://forums.unraid.net/topic/82198-support-binhex-urbackup/?do=findComment&comment=918119 pinned post in the support thread

I strongly recommend not doing this. There are many reasons, but the most important in my mind is the need to evaluate the entire situation before allowing the server to come back up. If you are not on site to make that evaluation, there very well may be circumstances that you are not aware.

Try creating a new VM, but point the primary vdisk to the existing file.