JorgeB

https://forums.unraid.net/topic/147759-key-replacement-loop/?do=findComment&comment=1329052
 
Install the Connect plugin.

Just type:
 

Looks more like CPU cache error, but it was correct, that memory has ECC, if it was one time I would just ignore for now.

Create a new flash drive (or just do a new config if you wan to keep the other settings) and after assigning the disks and before starting the array click on each data disk and then "erase".

Start here:
https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=819173
 
Also a good idea to run memtest.

Run a correcting check then a non correcting one without rebooting, if the 2nd one finds errors post new diags.

If it happens again enable the syslog server and post that after a crash.

Diags are after rebooting so we can't see what happened, two healthy disks getting disabled at the same time usually points to a power/connection issue, rebuild and if it happens again save the diags before rebooting.

Check filesystem on disk4, run it without -n.

Stop the array and click on "Add Pool"

There seem to be other issues, but this may get the filesystem to mount:
btrfs rescue zero-log /dev/sdg1 If it does recommend backing up and re-formatting, if it doesn't see here for some recovery options.

Disk looks fine, filesystem corruption is most often caused by an unclean shutdown or some lost writes to the device caused by power/connections issues, keep monitoring but I wouldn't worry much about it for now.

Try uninstalling the fan control/temp monitor plugins.

You can use the UD plugin to connect to a remote share, use the IP of a 10GbE NIC on the Synology (assuming the Unraid 10GbE is also separated from gigabit).

Yes, it's fine to delete the older ones.

Nov 13 20:38:28 Jupiter kernel: mce: Uncorrected hardware memory error in user-access at 23c638ee0  
This suggests a hardware problem, same for the server restarting on its own vs just crashing or hanging, start by running with just one stick of RAM, if the same try a different one, that will basically rule out the RAM.

There's likely an underlying hardware issue, but you can try importing the pool read-only:
 
zpool import -o readonly=on cache  
If it works backup and re-format the pool

Btrfs pool is crashing, it also logs a missing device, do you know where that is?
 
For now you can unassign the pool devices and the array should start, then see here for some btrfs recovery options.

Unfortunately there's nothing relevant logged, this usually points to a hardware issue, one thing you can try is to boot the server in safe mode with all docker/VMs disabled, let it run as a basic NAS for a few days, if it still crashes it's likely a hardware problem, if it doesn't start turning on the other services one by one.

Contact support.

Just run a correcting check, it's normal after an unclean shutdown to have some sync errors.

It depend for what you need it but 500Gb should be fine, a seconds device can be added for redundancy.
 
Basically yes.
 
 
 
 

You need to use the latest v6.9-rc for NIC support, also see here for max RAM speed, same as 3XXX models.

Share settings, default filesystem, default warning and critical temps, any custom SMART settings, default shutdown timeout, probably one or two more things, but those are the main ones.

Nov 17 03:05:51 anraid root: Creating new image file: '/mnt/user0/docker.img' size: 20G Nov 17 03:05:51 anraid root: failed to create image file  
That's an invalid path, go to docker settings and set it correctly, ideally to a pool.