JonathanM

Are you the same person? If not, please start your own thread and attach your diagnostics. If this is still you, attach new diagnostics covering the time period when this happens. Rebuild negates all previous actions you listed, the emulated disk includes the format.

Memtest is only definitive if it finds errors, sometimes memory produces errors only under certain loads. Try running with only 1 stick and see if the disk errors change, then switch sticks and repeat. Also, make sure you disable any XMP profiles. XMP is overclocking, regardless of whether the motherboard and memory says it should support it.

How many hours of memtest have been run in the current config?

It means recovery from corruption can be impossible with encryption in the way. Corruption can happen with hardware errors, like bad RAM, cables, or power issues. The problem is, you don't know it's going to happen until it does, and RAID (of any sort, not just Unraid) can't always compensate, meaning unless you have complete backups, you will lose data. Unraid or any RAID can't help with file deletion or overwriting good data with bad, so backups are always needed, but with encryption, the recovery options are even more limited, so backups are even more necessary. If the data is important enough to encrypt, it's important enough to keep multiple copies in multiple locations.

UrBackup is what I use. Discussion here.

There are many different options in Windows safe mode. You didn't mention how many you tried, it implied just the single option (with internet)

https://forums.unraid.net/forum/79-french-français/

Nope. Wiping the disk writes all zeroes, removing any traces of files or filesystem formats. Think of a format as a filing cabinet with drawers and folders. It allows files to be stored in an organized fashion so they can be easily retrieved, as opposed to just tossing the files on the floor in an empty room. Filesystems take up space even when there aren't any files stored.

Windows safe mode might reveal some information.

Try looking in the support thread for this container. Click on the container icon in Unraid's GUI, and select support.

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.