JorgeB

Both passed so they should be OK for now, suggest swapping cables/slots with another drives to rule that out and re-use them.

I believe it's planned, but don't know an ETA.

You have link on eth1 but not on eth0, either swap the LAN cable to the other NIC or boot using GUI mode and go to Settings -> Network Settings -> Interface rules and make eth1 eth0

Unraid driver is still crashing, unclear to me from your first post if it now also crashes with v6.8 or v6.9? if you see this same issue with different Unraid releases, I would really suspect a hardware problem.

May 5 10:26:53 LuNAS kernel: ? Sys_DumpTask+0xe9/0xf1 [corefreqk] May 5 10:26:53 LuNAS kernel: Cycle_AMD_Family_17h+0x31b/0xb37 [corefreqk]  
Unisntall the corefreq plugin.

It shouldn't make any difference, you'll see the BIOS screen when a boot device is not found, try a different USB port/hub and make sure it's USB 2.0.

Jun 6 17:49:41 Tower kernel: ata4.00: disabled Disk dropped offline, this is usually a power/cable problem, before it dropped there are several ATA errors logged, same for the SSD, check/replace those cables and post new diags after array start.

You can do a new config then check "parity is already valid" before array start.

Parity isn't giving a complete SMART report, so it does look like a device problem.

Yes, only two devices are in the pool, suggest doing:
 
-stop array
-unassign nvme2n1
-start array
-stop array
-wipe that device with
blkdiscard -f /dev/nvme2n1 -assign it back to the pool
-start array
 
If it still doesn't work post new diags.

You can change the eth assignments in the interface rules, set the main NIC as eth0:
 

 
Reboot required to take effect.

First would recommend connecting the SSDs to the Intel SATA ports, if that's not possible at least update LSI firmware to latest to see if all the errors go away, then enable the mover logging, run it and post new diags.

You can try recreating the flash drive, manually or using the USB tool, before doing it backup the config folder, then restore it.
 
If that doesn't help and you want to go back to v6.9.2 just copy the all the bz* files from the v6.9.2 download overwriting existing files on flash.

From what I can see there are only 3 drives connected to the JMB controller, all 3 are being detected, the two that aren't are connected to the onboard SATA ports, though can't see why they aren't working, if there's space connect all 5 devices devices to the JMB controller, or try using the other two onboard SATA ports.

2 of the SATA ports are set to IDE, go to the BIOS and change them to AHCI/SATA, usually ports 5/6, that's where disks 2 and 4 are connected, if after doing that they are still unmountable run xfs_repair, don't run before correcting that.

Disk is not giving a SMART report, check replace cables and post new diags after array start.

Start here:
https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=819173
 

Jun 2 12:01:08 CicioneServer kernel: macvlan_broadcast+0x116/0x144 [macvlan] Jun 2 12:01:08 CicioneServer kernel: macvlan_process_broadcast+0xc7/0x110 [macvlan]  
Macvlan call traces are usually the result of having dockers with a custom IP address, switching to ipvlan should fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enable, top right)), or see below for more info.
https://forums.unraid.net/topic/70529-650-call-traces-when-assigning-ip-address-to-docker-containers/
See also here:
https://forums.unraid.net/bug-reports/stable-releases/690691-kernel-panic-due-to-netfilter-nf_nat_setup_info-docker-static-ip-macvlan-r1356/

Cache filesystem is corrupt, best bet is to copy all important data elsewhere then re-format and restore the data.

May 25 20:58:07 Skrumpy kernel: macvlan_broadcast+0x116/0x144 [macvlan] May 25 20:58:07 Skrumpy kernel: macvlan_process_broadcast+0xc7/0x110 [macvlan]  
Macvlan call traces are usually the result of having dockers with a custom IP address, switching to ipvlan might fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enable, top right)), or see below for more info.
https://forums.unraid.net/topic/70529-650-call-traces-when-assigning-ip-address-to-docker-containers/
See also here:
https://forums.unraid.net/bug-reports/stable-releases/690691-kernel-panic-due-to-netfilter-nf_nat_setup_info-docker-static-ip-macvlan-r1356/

Didn't read the entire post, if you're getting an IP that's not the problem, please post the diagnostics.

00:17.0 RAID bus controller [0104]: Intel Corporation Device [8086:43de] (rev 11) DeviceName: Onboard - Other Subsystem: ASUSTeK Computer Inc. Device [1043:8694]  
No SATA controller being detected, only this, see if there's an option in the BIOS to change it to AHCI/SATA

Can't answer that, never used those, just delete one of them.

Try this:
https://forums.unraid.net/topic/124055-unraid-6101-fails-to-boot-bzroot-checksum-error/?do=findComment&comment=1131675
 

If it's a Dell server see here:
 
https://forums.unraid.net/topic/119502-bzimage-checksum-error/?do=findComment&comment=1108354