It will work, but it's not recommended, and keep in mind that for example two 4TB drives in raid0 will be slightly smaller than one 8TB drive, so parity will always need to be larger than the data drives you intend to use.
Jul 13 14:07:54 ADL-Server kernel: macvlan_broadcast+0x10e/0x13c [macvlan]
Jul 13 14:07:54 ADL-Server kernel: macvlan_process_broadcast+0xf8/0x143 [macvlan]
Macvlan call traces are usually the result of having dockers with a custom IP address, more info below.
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/
There are also a lot of ATA errors on disks 1 and 2, replace cables.
There are a couple of call traces but can't see the reason, could be the kernel doesn't like your board, the number one issue for crashes on v6.9.2 appears to be this:
Though this is usually visible in the syslog, still might be worth checking if it applies to you.
You just need to boot with DOS and run that command, if the board has UEFI support you'll need to use a UEFI shell instead, it's possible to update an LSI using Unraid but unfortunately the Linux binary doesn't work with the delete BIOS option.
You can just delete it:
https://forums.unraid.net/topic/12114-lsi-controller-fw-updates-irit-modes/?do=findComment&comment=632252
Note: with multiple controllers you need to select the controller or it will delete the BIOS from the first one.
They will spin down with a Supermicro JBOD (or similar direct connect JBDO) they should also spin down with Netapp, but you should search for that, and SAS devices might not spin down even with the plugin.
No, other way around, rebuild aborted because the disk got disabled.
Disk looks healthy, you should update the LSI firmware though, that version has known issues.
Disk dropped offline, this is usually a connection/power problem, but since it dropped there's no SMART.
The rebuild aborted, you started a parity check, and no, the disk won't be re-enable when it finishes.