JorgeB

The HBA is being initialized correctly and the driver loaded, unless there's an issue with the ports and since you've ruled out the cables it could be the backplane.

Unassign all pool devices, start array, stop array, reassign all pool devices, including the logs device, in the same order as the zpool import output, so sdg, sdh, etc, logs device in the end, then start the array and post new diags if the pool doesn't mount.

Try this:
 
sgdisk -o -n 1:1M:0 /dev/sdX  
Replace X with correct letter, then reboot and the disk should no longer show as wrong.

Disks are dropping offline, looks more like a power/connection issue.

Zfs pool is crashing, see if it mounts in read only mode:
 
zpool import -o readonly=on newcache  
If successful you can then start the array, the GUI will still show the pool unmountable, but the data will be under /mnt/newcache, you can then try to backup anything important and then reformat the pool.

For some reason your pool is set to raid0 in the cfg:
 
diskFsProfile="raid0"  
Edit /boot/config/pool/cache.cfg and change that to raid1 and then try again, I would think an array start/stop would be enough, but try rebooting if you still see the same after the change.

That's strange if you see that with multiple browsers, are you using an adblocker or firewall?
 
You can edit /config/plugins/dynamix/dynamix.cfg on the flash drive and make theme="white", then reboot.

LnkSta: Speed 5GT/s (downgraded), Width x1 (downgraded)  
Controller is linking at PCIe 2.0 instead of 3.0, and worse than that at x1, instead of x8, so bandwidth is being severely limited, see if you have a better slot where you could use the HBA.

UDMA CRC errors are usually a SATA cable problem, that's a very lower number but if it keeps increasing replace the SATA cable, note that the attribute never resets/goes down.

If the old disk is still intact you can try typing with the array stopped:
 
sgdisk -o -a 8 -n 1:32K:0 /dev/sdX  
Replace X with correct letter, then post the output of:
 
btrfs fi show  

You are running into the included disks bug, update to 6.12.6 and try again.

That script should not be used with recent releases, it's not compatible, but see here for a workaround:
 
https://forums.unraid.net/topic/145821-cant-unraid-stop-when-array-already-unmounted/?do=findComment&comment=1323316
 

There are constant HBA issues like this:
 
Jan 17 08:50:06 Tower kernel: mpt3sas_cm0 fault info from func: mpt3sas_base_make_ioc_ready Jan 17 08:50:06 Tower kernel: mpt3sas_cm0: fault_state(0x2810)!  
It keeps resetting, make sure it well seated and sufficiently cooled, you can also try a different PCIe slot.

Make sure the plugin is up to date and reboot, then retest.

For these first try this:
https://forums.unraid.net/topic/118286-nvme-drives-throwing-errors-filling-logs-instantly-how-to-resolve/?do=findComment&comment=1165009
 
For these try booting in safe mode and/or closing any browser windows open to the GUI, only open when you need to use it then close again.
 

Try booting in safe mode and/or closing any browser windows open to the GUI, only open when you need to use it then close again.

There appear to be other issues with the filesystem, but it didn't mount initially because of a bad log tree, this may help getting past that:
 
btrfs rescue zero-log /dev/sde1  
Then re-start the array, if the pool mounts good idea to make sure backups are up to date.

Syslog starts over after every boot, so not much to see, if it keeps happening enable the syslog server and post hat one after a crash/hang.

Currently you need at least one device assigned to the array, an old flash drive can fulfill that requirement.

It's missing from the System Devices, similar to Windows device manager, at least I'm not seeing it there, you can confirm by going to Tools -> System Devices.

This is a bug, it will be fixed for v6.12.7, it happens if the drive has an existing partition starting on sector 2048, and it did:
 
Jan 16 09:44:53 Flint kernel: mdcmd (5): import 4 sdc 2048 9766435820 0 WDC_WD100EFAX-68LHPN0_JEKXKXVZ  
For now if you manually wipe the drive (or use UD to do it) and reboot first this will not happen.
 
 
 

Regular Tp-link should work, though it's a Realtek.

That is correct, and there's no other way I know off other than limiting the disks for that share, but like you mentioned, you'd need to change once it gets full.

Likely GiB vs GB.

Jan 15 09:39:21 Hyperion root: Warning: The kernel is still using the old partition table. Jan 15 09:39:21 Hyperion root: The new table will be used at the next reboot or after you Reboot and try again.