Squid

Docker Folders installed?

Stop the docker service (Docker Tab).
 
Enable Template Authoring Mode
 
Now when you're on the template screen there will be an addition button named "Save"  Clicking it will show both the generated XML and the docker run command that would be issued

Top of my head, the mce is because of the microcode update being issued to the CPU and is probably no issue
Nov 19 16:35:03 Punisher kernel: microcode: CPU0: patch_level=0x08701021 Nov 19 16:35:03 Punisher kernel: microcode: CPU1: patch_level=0x08701021 Nov 19 16:35:03 Punisher kernel: microcode: CPU2: patch_level=0x08701021 Nov 19 16:35:03 Punisher kernel: microcode: CPU3: patch_level=0x08701021 Nov 19 16:35:03 Punisher kernel: microcode: CPU4: patch_level=0x08701021 Nov 19 16:35:03 Punisher kernel: microcode: CPU5: patch_level=0x08701021 Nov 19 16:35:03 Punisher kernel: microcode: CPU6: patch_level=0x08701021 Nov 19 16:35:03 Punisher kernel: microcode: CPU7: patch_level=0x08701021 Nov 19 16:35:03 Punisher kernel: microcode: CPU8: patch_level=0x08701021 Nov 19 16:35:03 Punisher kernel: microcode: CPU9: patch_level=0x08701021 Nov 19 16:35:03 Punisher kernel: microcode: CPU10: patch_level=0x08701021 Nov 19 16:35:03 Punisher kernel: microcode: CPU11: patch_level=0x08701021 Nov 19 16:35:03 Punisher kernel: microcode: Microcode Update Driver: v2.2. Nov 19 16:35:03 Punisher kernel: IPI shorthand broadcast: enabled Nov 19 16:35:03 Punisher kernel: sched_clock: Marking stable (11946833916, 343487151)->(12438976477, -148655410) Nov 19 16:35:03 Punisher kernel: mce: [Hardware Error]: Machine check events logged Nov 19 16:35:03 Punisher kernel: registered taskstats version 1 Nov 19 16:35:03 Punisher kernel: mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 27: faa000000000080b Nov 19 16:35:03 Punisher kernel: mce: [Hardware Error]: TSC 0 MISC d012000800000000 SYND 5d000000 IPID 1002e00000500 Nov 19 16:35:03 Punisher kernel: mce: [Hardware Error]: PROCESSOR 2:870f10 TIME 1668897207 SOCKET 0 APIC 0 microcode 8701021  

Unraid runs from RAM and the files are unpacked from the flash drive.
 
To make any changes persistent, you must reapply them via an appropriate script either via the user scripts plugin or via the "go" file (/config/go) on the flash drive

Go to /var/lib/docker  That's where the image (or folder) ultimately resides
 
But you might find it easier to simply go to the console of the individual container via the webGUI rather than sorting out all of the various layers etc within the docker subsystem.

Referencing everything by the user shares (/mnt/user/...) the system will sort it all out by itself.
 
Even if for some reason you directly reference the share by disk (/mnt/disk7/...) then you can either adjust the references or simply assign the disks to the same slot.  Nowhere does the system force you to have disk4, and the OS is perfectly happy having disks1-3 and disks 5-7 assigned with 4 unassigned

You probably entered in a custom value into the settings for mover tuning and there's a syntax error you made there.

Looks like a remnant of an old config that the system is enforcing, but no option to change it that I can find.
 
Delete /config/share.cfg on the flash drive and reboot.

You can't.

In SAB, you've set the downloads location to be Downloads/incomplete.  Since this is a relative path, it's being stored within /config/Downloads/incomplete (which maps to /mnt/user/appdata/sabnzbd/incomplete
 
You want to set the downloads folder to be /Downloads/incomplete  That way it'll map to /mnt/user/Media/Downloads/incomplete
 
Do the same for the completed downloads folder

Have you actually formatted the drives within Unraid yet?

This debate is really no different than if on a Windows box a loss of power happens during sleep if Hybrid sleep is not enabled (can only be done via Control Panel).  Data loss and corruption can / will occur
 
Plus, it has to be noted that Limetech does not even support Sleep in the first place.  This functionality is via a 3rd party plugin.
 
No matter how you cut it, the loss of power results in an unclean shutdown.  Not really any debate about that.  And if/when data loss results from the unclean shutdown and if it was possible to disable the automatic check then are you going to blame yourself or are you going to wind up blaming the OS?
 
That being said your options are the following either install a UPS (should be done anyways on any and all electronics in your house regardless) or stop the parity check from continuing that results.
 
Something like this via User Scripts set to run at first array start
#!/bin/bash sleep 300 /usr/local/sbin/mdcmd nocheck  

Assuming this is 6.11.x, can you rename python2.plg to instead be Python2.plg (capitol P)  within /config/plugins on the flash drive.  Reboot and see if that makes a difference.

Is Nginx allowing websockets through?

yes, because a write to the drive failed, so the OS automatically disabled the drive.  To re-enable you must rebuild the drive from the parity information
 
DO NOT FORMAT
 
Stop the array, unassign the drive 1
Start the array, stop the array
Reassign drive 1
Start the array and start the rebuild.

Nothing gets changed.  Caveat is going from 6.9+ back to 6.7 / 6.8 is that you will have to reassign your cache pools.  

You have the Dynamix Schedules plugin installed.  This adds another tab to the Schedules section which allows you to change the default times that hourly, daily, weekly, and monthly background task run at.

Try clearing out the history, cookies etc.  If that's Safari and still have problems, then try Firefox / Chrome and see if there's any change (not a solution, but would be a data point for the devs)

Groundwork has been laid in the soon to come 6.11 Stable release for 2FA on the actual logins to the server.  Not implemented as of yet, but the groundwork / infrastructure changes are now in place

Jan 29 04:47:51 Infinity kernel: mce: [Hardware Error]: Machine check events logged Jan 29 04:47:51 Infinity kernel: [Hardware Error]: Corrected error, no action required. Jan 29 04:47:51 Infinity kernel: [Hardware Error]: CPU:1 (19:21:2) MC11_STATUS[Over|CE|-|AddrV|PCC|-|CECC|-|Poison|-]: 0xd7894800017d60c0 Jan 29 04:47:51 Infinity kernel: [Hardware Error]: Error Addr: 0x0000000000000000 Jan 29 04:47:51 Infinity kernel: [Hardware Error]: IPID: 0x0000000000000000 Jan 29 04:47:51 Infinity kernel: [Hardware Error]: L3 Cache Ext. Error Code: 61 Jan 29 04:47:51 Infinity kernel: [Hardware Error]: cache level: RESV, tx: INSN  
Looks like it's a typical Ryzen MCE and nothing to worry about.

It's not Unraid per se, but the manufacturers of motherboards and devices themselves.
 
The timings etc on USB3 are more strict than on USB2 so the motherboards and devices (in particular) need to be higher quality.  Flash drives as an example are manufactured with the expectation that they will be lost.  If the manufacturer can save 1/10th of a cent on every stick made by substituting a different capacitor that *technically* hits the tolerances but may quickly degrade then it adds up to significant profit.
 
Lower tolerances = higher reliability.  Higher tolerances = lower reliability.  Q.E.D.

Settings - Docker with the service disabled

Does today's update to CA fix this?

Your flash drive is being mounted as read only due to corruption.   Toss it into a separate computer and run the file system checks on it
 
 
If problems continue replace it with a quality drive (kingston)

Yes you can do this.
 
For best results (ie: Trim Support) you would create cache-pools with the SSD's and only have a single flash drive (any size) as being part of the main array (Currently, the main array does not support Trim, and a disk has to be assigned to it -> hence the flash drive assigned)