JorgeB

Start the array without any cache device assigned to make Unraid "forget" current cache config, then stop array, assign old cache device and start the array.

Is it showing the same again after rebooting?

I don't see any format attempt on current diags, try formatting it again, if it fails post new diags.

Syslog snippets are rarely helpful, please post the diagnostics.

Not likely, that's corruption

This is a checksum error, i.e. data corruption, it's a good idea to run memtest.

That one is IT mode only, though you should update to latest firmware if using an older release.

Sorry no, I don't buy SATA cables, I use surplus cables from boards I assemble at work.

Then there's still a problem, and usually it's the SATA cable, Samsung SSDs are particularly picky about cable quality.

Try a different PCIe slot, also make sure there is some airflow around it, if that doesn't help it might be a bad or failing controller.

Not seeing a reason for that, it appears to be a false warning, reboot by typing reboot on the console.

Just another note, SAS3 models like the 9300 use SFF-8643 to SATA

There are, some are SAS2 and PCIe 2.0, some SAS2 and PCIe 3.0, some SAS3 and PCIe 3.0, for Unraid use with spinners (without expanders) they will all perform similar. Yes, there's no limit with any sizes for the foreseeable future. Some are IT mode only, e.g. 9207, 9300, but flashing to IT is easy if needed. Whatever works best for you, in terms of total cost and number of available PCIe slots. Yes, cables need to be forward breakout like that one, reverse breakout look the same but won't work for this.

It's likely a problem with the Linux kernel and/or the driver included with that kernel, a newer kernel/driver might fix it, might not.

It's a controller problem: Mar 30 23:15:06 TheNewdaleBeast kernel: hpsa 0000:03:00.0: scsi 5:0:2:0: resetting physical Direct-Access SEAGATE ST4000NM0023 PHYS DRV SSDSmartPathCap- En- Exp=1 Mar 30 23:15:38 TheNewdaleBeast kernel: hpsa 0000:03:00.0: Controller lockup detected: 0x00130001 after 30 Mar 30 23:15:38 TheNewdaleBeast kernel: hpsa 0000:03:00.0: controller lockup detected: LUN:0000000000800101 CDB:01030000000000000000000000000000 Mar 30 23:15:38 TheNewdaleBeast kernel: hpsa 0000:03:00.0: Controller lockup detected during reset wait Mar 30 23:15:38 TheNewdaleBeast kernel: hpsa 0000:03:00.0: scsi 5:0:2:0: reset physical failed Direct-Access SEAGATE ST4000NM0023 PHYS DRV SSDSmartPathCap- En- Exp=1 Likely a kernel issue, I believe there were other reports with problems with these HP controllers.

Doubt that is the problem but you should still update, latest release can be found under legacy HBAs. You'll need to move things around to try and rule things out out, cables, backplane slot, adapter, etc, disks detected are on port 1 only of both cables, which might be more than just coincidence, also don't forget you need to respect max SATA cables lengths, it can't be more than 1 meter from HBA to disks total.

And where did you find 20.00.06? Like mentioned latest release is 20.00.07, and AFAIK the ones before were 20.00.00 and 20.00.04. Also, and assuming it's connected to some sort of external enclosure, maybe also worth mentioning brand/model and if single/dual link is in use.

Latest firmware is p20.00.07, and it appears you're running an HP firmware, still, strange issue, but try with LSI firmware

This looks like a connection problem, replace cables for disk6, also for cache device.

This is a disk problem, aka bad sector.

sde isn't mounting because the UD plugin, together with some others, didn't install properly, try re-downloading them: Mar 23 11:07:31 Draco root: plugin: installing: /boot/config/plugins/unassigned.devices.plg Mar 23 11:07:31 Draco root: Mar 23 11:07:31 Draco root: Warning: simplexml_load_file(): /boot/config/plugins/unassigned.devices.plg:1: parser error : Document is empty in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 216 Mar 23 11:07:31 Draco root: Mar 23 11:07:31 Draco root: Warning: simplexml_load_file(): in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 216 Mar 23 11:07:31 Draco root: Mar 23 11:07:31 Draco root: Warning: simplexml_load_file(): ^ in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 216 Mar 23 11:07:31 Draco root: Mar 23 11:07:31 Draco root: Warning: simplexml_load_file(): /boot/config/plugins/unassigned.devices.plg:1: parser error : Document is empty in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 216 Mar 23 11:07:31 Draco root: Mar 23 11:07:31 Draco root: Warning: simplexml_load_file(): in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 216 Mar 23 11:07:31 Draco root: Mar 23 11:07:31 Draco root: Warning: simplexml_load_file(): ^ in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 216 Mar 23 11:07:31 Draco root: Mar 23 11:07:31 Draco root: Warning: simplexml_load_file(): /boot/config/plugins/unassigned.devices.plg:1: parser error : Document is empty in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 216 Mar 23 11:07:31 Draco root: Mar 23 11:07:31 Draco root: Warning: simplexml_load_file(): in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 216 Mar 23 11:07:31 Draco root: Mar 23 11:07:31 Draco root: Warning: simplexml_load_file(): ^ in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 216 Mar 23 11:07:31 Draco root: Mar 23 11:07:31 Draco root: Warning: simplexml_load_file(): /boot/config/plugins/unassigned.devices.plg:1: parser error : Document is empty in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 216 Mar 23 11:07:31 Draco root: Mar 23 11:07:31 Draco root: Warning: simplexml_load_file(): in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 216 Mar 23 11:07:31 Draco root: Mar 23 11:07:31 Draco root: Warning: simplexml_load_file(): ^ in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 216 Mar 23 11:07:31 Draco root: plugin: file doesn't exist or xml parse error

That doesn't mean you shouldn't, if nothing else at least update to latest RAID firmware, since it's using an ancient one, it might even detect the SSDs after that, though since trim won't work not the best place to use them anyway.

AFAIK you'll need a plugin like the dynamix system temp or IPMI plugin if the board has IPMI, but either one can't show you past temps.

Very unlikely, the temp sensor is inside the CPU. It only throttles during the overheat period, once the temperature decreases it will return to normal operation.