Squid

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

The licence is tied to the flash drive, and the computer it is used on is irrelevant.  Copying over from one flash to another the /config folder (except for the .key file for that flash drive) moves the entire configuration from one to the other.
 

Try editing the path and select Slave as the access mode.  EG: Read/Write: SLAVE

From Main, Go to Boot Device, then click on Flash followed by Syslinux Configuration
 
In the section that has the radio button selected (ie: your default boot mode), add in to the append section
pci=noaer  
The section will wind up looking like this (assuming the default non-gui boot mode)
kernel /bzimage append initrd=/bzroot  pci=noaer  
Don't remove anything else that you may have added yourself (or was added in via another setting in the GUI - eg: the mitigations=off on mine).  
 
You'll need to reboot for the changes to take effect after applying them
 

You can also try running make_bootable on the flash drive via windows (run as administrator)
 
What you need to backup and move to the new flash if necessary is the contents of /config

5 Reallocated_Sector_Ct PO--CK 098 098 010 - 2272  
2272 reallocated sectors is over my comfort level by a significant amount and should be replaced.  Drill out the cover screws so you can get the cover off and you'll have some nice new wall art for your house.

Contact support and include q copy and paste (no screenshots) of what shows up within Tools -Registration
 

If the file being written already exists and is on the array then a re-write of the file is going to go onto the array.
 
 

The permissions would be incorrect.   Use Krusader or File Manager (both available within Apps) to delete or alternatively the command line

The triangle (if you hover over it) means that some (or all) of the files are unprotected by a parity system.   Since the ZFS and NVMEs are presumably protected, that means that the ISOs share is sitting on the array which doesn't look like you've added a parity drive to.

Try it in safe mode and without the dockerd command you're running in /config/go on the flash drive

It's not stuck.  DONE appears when everything is actually done.  Prior to that it actually says CLOSE which moves processing to the background

Looks like its working.
 
Highwater will fill all the 16s up to 8tb freespace.  After that's done, then it starts back over at disk 1 and fills every drive up to 4tb freespace in turn.  Then starting back at disk 1 it'll go to 2tb.
 
IE: Highwater is based upon the largest drive in the array (50%, 25%,...) not 50%, 25% of every drive.  Based upon your drive free space, it should still be on #1

Looks like you're using a USB HDD for your parity drive.  Many USB bridges do not pass through certain ATA commands to the drives, and this is likely your problem (and you're also not going to wind up seeing any SMART data for the drive either)

You've got emhttp running twice in the go file.
#!/bin/bash # Start the Management Utility /usr/local/sbin/emhttp & /usr/local/sbin/emhttp & . . . Does it work if you remove one of those lines?

From Finder, you have to first navigate to the TM share in order for TM to see it.  IE: The Mac has to have it mounted first.   After adding it in, TM will automatically mount it.
 
NOTE:  I don't recommend having TM shares moving to/from the array or cache.  IF something happens in the middle of the move and everything doesn't get moved for one reason or another, the backups get trashed.   Leave it on the cache pool or write directly to the array.  Also, TM shares moving from cache to array (and vice versa) has not been fully tested under all circumstances to begin with.

You're using docker as a "folder".  Nothing wrong with that per se, but it's within the "system" share which is currently setup to move files from the cache pool to the array.
 
Docker Folder does not like being moved around, as only part of the files will ever get moved around.  Either change it to be an image or switch the system share to a cache only share (primary storage of cache and no secondary storage)
 
Either way, you're going to have to go into Settings, Docker disable the service, switch to advanced view and then delete the image.   Then re-enable the service and head over to Apps, Previous Apps and check off what you want installed and from the bottom of the screen Install X Applications.
 
 

Probably from an automatic fsck being run on the flash drive

I *think* that this may have been addressed in 6.9RC2+

To be expected.  The docker system ignores all port mappings when network type is a custom IP (or host)
 

It's not that it's overclocked.  The RAM is actually running at it's SPD speeds.  But rather that at those speeds its greater than what your CPU supports.  You need to underclock the RAM to match what is in the graphs
 
FWIW, The QVL for the motherboard shows that RAM you have as only being supported for two sticks.  

Looks like an issue with corruption on the flash drive and the boot files.
 
Try moving the files from /previous to the root of the flash drive and then attempt the upgrade again.

From Main, Boot Device, Click on Flash then Syslinux Configuration
 
Add this to the Append line on which ever entry you have as default (the "radio" button that's selected)
pci=noaer  
It should look something akin to this after the fact
 

 
Reboot and see if that fixes you up