Squid

Looks like a symptom of bad / failing memory.  Run Memtest from the boot menu for at least a couple of passes
 
看起来像是内存损坏/故障的症状。从启动菜单运行 Memtest 至少几次
 
 

Installing the unraid patch plugin is recommended on every Unraid system.  It will keep your system updated with any critical OS patches outside of full releases of the OS
 
建议在每个 Unraid 系统上安装 unraid 补丁插件。  它将让您的系统使用操作系统完整版本之外的任何关键操作系统补丁进行更新

What version of the OS is this on?  I had the same thing happen once during testing on 6.10.0 but couldn't replicate it afterwards.
 
Either way, you should be good to go -> just hit Tools/Unraid Patch

Emergency notifications

Edit the container and add in whatever other paths, variables etc that you need

Dec 25 11:22:33 UnRAID kernel: mce: [Hardware Error]: Machine check events logged Dec 25 11:22:33 UnRAID kernel: [Hardware Error]: Corrected error, no action required. Dec 25 11:22:33 UnRAID kernel: [Hardware Error]: CPU:1 (19:21:2) MC22_STATUS[-|CE|MiscV|-|-|SyndV|-|Poison|Scrub]: 0x98a889440000010e Dec 25 11:22:33 UnRAID kernel: [Hardware Error]: IPID: 0x0000000000000000, Syndrome: 0x0000000000000000 Dec 25 11:22:33 UnRAID kernel: [Hardware Error]: Bank 22 is reserved. Dec 25 11:22:33 UnRAID kernel: [Hardware Error]: cache level: L2, tx: RESV, mem-tx: GEN  
Whatever it is, the system corrected it

Installing Unassigned Devices Preclear (requires Unassigned Devices) will get it in there.
 
Beyond that, you have to manage packages yourself via the extra folder on the flash drive

The diagnostics show that there is no ethernet cable connected ethtool.txt
 
 

The system updating the templates as it updated the containers was removed a couple of years ago as it proved to be more troublesome than it was worth.
 
I would open two tabs to the OS.  One on the docker tab, and from there edit each container.  In the other tab, open CA and within Settings enable Allow install second instance, then within Installed apps if you hit install second from Actions you can compare the two templates between the tabs and make appropriate adjustments.
 
Other than that, delete and reinstall (not reinstall from previous) is the way to go.  So long as the name of the container matches the appdata will still point to the correct location

You can always add in any new additional paths that you choose (eg for Music).  Also, for the Nvidia visible devices you have to add in a new variable to support this
 
FWIW, the best place for support on any container from Linux Server is via their discord channel (click on the icon and select discord)

With high water and mismatched drives.
 
System will start at disk1 and fill it to 7.5T free, then move to disk 2 until its at 7.5T then disk 3->7.5T
 
Following that it will start again at disk 1 and fill to  3.75T, then disk2 -> 3.75T, then d3 ->3.75T
 
After those drives are done it will fill disks 4->9 to 3.75T then begins again at disk 1 and fills 1-9 to 1.875T and so on.
 

Look for a docker container that's continually restarting (The uptime for the container should show it)

Turn off template authoring mode in Settings - Docker with the docker service stopped

Looks like you've got a container which is restarting itself every 5-10 seconds.  The uptime on the docker tab should tell you which one is having problems starting up

You always need to use the "raw" URL, not a URL that is a web page:
 
EG: https://raw.githubusercontent.com/phyzical/docker.versions/main/docker.versions.plg

You have a share named "appdata:"  This is messing up the system because the ":" is an invalid character on the flash drive
 
Your default appdata location in docker settings is correct, but you've got likely a docker container referencing a host path of /mnt/user/appdata:  Edit each of the containers and change that offending path to be /mnt/user/appdata without the ending colon

Memtest is an option on the boot menu you select
 
memory speed you change in your bios

The system folder contains 22.5 GB (Likely the docker.img) on disk 1 which causes the spin up.  Disable the docker service, set the system share for Primary to be cache, secondary to be array and mover operation to move from array to cache.   After running mover (main tab), everything should be on the cache pool and you'll be good to go

Looks like a bad flash drive
Jun 8 14:00:12 gabry-nas kernel: critical medium error, dev sda, sector 60087297 op 0x0:(READ) flags 0x0 phys_seg 7 prio class 2 You should transfer it to a new device

Effectively unlimited compared to the size of drives you can buy.  While there may be some limitations somewhere over what the theory is on file system maximums (eg: XFS supports a maximum 8 exobyte drive size), not currently available hard drive even remotely comes close to this size.

Nothing to be done.  Just replace the old drives with the new ones one at a time and start the array and the OS will rebuild the appropriate contents and expand the file system to take advantage of the extra space (once you get to the data drives)

Long standing issue (fixed I believe in 6.13).  It also has the net result of whenever you go to the VMs tab it's a given that all/most of your drives will spin up

Nothing specific, but FYI when replacing fans, most people do it because of the noise level.  One thing to bear in mind however is that especially when you're dealing with drive bays, higher CFM (which your Noctua may or may not have over the stock fans) may actually be worse for cooling.
 
CFM has no bearing on trying to pull the air through the very small cracks in drive bays.   For that you need fans which have high static pressure.  The two ratings do not always conform to each other.  IE: High CFM != high static pressure.  
 
But for specifics, have you cleaned out the little gaps in the bays?  If they're clogged up with dust, then a high CFM but low static pressure won't have a hope of pulling the air through whereas a high static pressure but low CFM will do a better job on clocked gaps.

Error 8 usually means the URL isn't correct.  On older keys if something changed (name, email address etc), then the original URL might have changed.  
 
Either way, you need to contact support and also show them a copy & paste (no screenshots) of what is appearing within Tools - Registration and they'll get it all worked out for you.

shareExport="-" Checking your Media share, it's not exported.  You need to export it on the SMB settings for it to be available on the network