Vr2Io

Pls note the different between GB and TB.

Unraid usually won't support those hardware assist raid.
 
No issue. AHCI, raw mode ... always correct.

You mean parity check speed ?
 
It doesn't matter how disk are connect in LSI HBA ports.
 
This was happen in long time ago.
 
Error 21 [0] occurred at disk power-on lifetime: 224 hours (9 days + 8 hours)
  When the command that caused the error occurred, the device was active or idle.
 
  9 Power_On_Hours          -O--C-   097   097   000    -    24564
 
Anyway no cause found.
 

Input some number in eth0 default gateway metric, i.e. 1

Yes, if org. disk confirm mountable.

Ensure BIOS time was UTC, when large different with BIOS and NTP, it won't update.

You RAM run in 1.2v @3600MT, if according mfg spec., it is 1.35v, pls tuning your BIOS setting and execute memory test.
There are something wrong with "Maximum Voltage: 1.2 V" in SPD detection, you may need lower both speed.
 

Yes, you can reorder on the fly for single parity array.

WOL is a series ethernet packet relate MAC address only, doesn't protocol TCP/UDP. WOW ( wake on wan ) was a way to bridge both. Even you need WOW, that NIC also don't need IP. 

First ver. actual throughput will be 300MB/s and I am not sure Unraid support newer version or not even you have 3.2 gen 2 controller & device.

You don't need apply VLAN as you have two NIC, in fact, you can't use VLAN because your equipment seems doesn't VLAN capable.
 
Just set eth1 ( WISP ) in different subnet & gateway ( again no need VLAN ) then assign docker in this network. Client also need connect to WISP router to access corresponding docker.

Don't bond them and set 1G NIC IP to none.
 

Native Unraid haven't router / bridge two physical network port function, a common method was make a direct 10G connection between NAS ( one 10G port be eth1 ) and PC for file transfer, setting them in different IP/Subnet in static IP.
 
Then onboard 1G NIC in NAS ( eth0 ) and PC WiFi, for access internet and manage Unraid.

If that, you can use Nut in Unraid or APC PowerChute in Windows to verify.
 
If battery supplying power instead charging, then you will found large voltage drop on battery.

Docker app can set in different network mode, i.e. bridge / host / custom, I usually use custom and static the IP to docker, so I don't need care about port no.

You have several disk connect to USB1 and USB9 bus, but USB1 was USB2.0
 
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 0951:1666 Kingston Technology DataTraveler 100 G3/G4/SE9 G2/50
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 152d:0567 JMicron Technology Corp. / JMicron USA Technology Corp. JMS567 SATA 6Gb/s bridge
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 011 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 010 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 009 Device 003: ID 1058:0748 Western Digital Technologies, Inc. My Passport (WDBKXH, WDBY8L)
Bus 009 Device 002: ID 1058:0820 Western Digital Technologies, Inc. My Passport Ultra (WDBMWV, WDBZFP)
Bus 009 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 008 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Look like problem on init two 9235 SATA controller. Pls try disable IOMMU or downgrade Unraid OS.
 
Jul  8 20:22:41 NAS00 kernel: DMAR: [DMA Write NO_PASID] Request device [01:00.1] fault addr 0x104500000 [fault reason 0x02] Present bit in context entry is clear
Jul  8 20:22:41 NAS00 kernel: DMAR: [DMA Write NO_PASID] Request device [07:00.1] fault addr 0x105440000 [fault reason 0x02] Present bit in context entry is clear
 
01:00.0 SATA controller [0106]: Marvell Technology Group Ltd. 88SE9235 PCIe 2.0 x2 4-port SATA 6 Gb/s Controller [1b4b:9235] (rev 10)
    Subsystem: Marvell Technology Group Ltd. 88SE9235 PCIe 2.0 x2 4-port SATA 6 Gb/s Controller [1b4b:9235]
    Kernel driver in use: ahci
    Kernel modules: ahci
 
07:00.0 SATA controller [0106]: Marvell Technology Group Ltd. 88SE9235 PCIe 2.0 x2 4-port SATA 6 Gb/s Controller [1b4b:9235] (rev 10)
    Subsystem: Marvell Technology Group Ltd. 88SE9235 PCIe 2.0 x2 4-port SATA 6 Gb/s Controller [1b4b:9235]
    Kernel driver in use: ahci
    Kernel modules: ahci
 

👍

Yes

For NIC issue, pls try disable VT-d ( not VT-x ) for tg3 NIC until fix on kernel.
 
 
 
You can disable VT-d by command line or set it in BIOS.
 

Use Broadcom NIC with tg3 driver and enable VT-d ?
 
If yes, you can edit the config file ( "Syslinux Configuration" ) to add intel_iommu=off or unplug the USB to another PC to edit it.
Or
Create a blank tg3.conf file to un-blacklist the driver if you confirm no corrupt issue by tg3+VT-d.
 
Data Corruption possible with tg3 driver when Intel VT-d is enabled.
The combination of Linux 5.15 kernel, tg3 driver, and Intel VT-d enabled appears to be causing data corruption.  This has been verified on several platforms which include a Broadcom NetXtreme Gigabit Ethernet NIC (note: there may be others).  This release includes the following workaround:
 
Very early in server startup (rc.S) if Intel VT-d is detected enabled, then the script will unconditionally create the file:
/etc/modprobe.d/tg3.conf
with following content:
blacklist tg3
Hence by default if VT-d is enabled, which is to say, it has not been disabled in either bios or via kernel "intel_iommu=off", then we are going to blacklist the tg3 driver on all platforms.

What if someone has a platform where tg3 does not give them any trouble with VT-d enabled? In this case they must create an empty file on their flash device:
config/modprobe.d/tg3.conf
When the startup sequence continues it will get to the point where it executes:
install -p -m 0644 /boot/config/modprobe.d/* /etc/modprobe.d
A blank tg3.conf file stored on the flash then effectively un-blacklists it.

There will be users who will lose network connectivity because their NIC is blacklisted. If you are running on a problematic platform you should go into your bios and disable VT-d. If this is a platform without issue, then you will need to create the blank tg3.conf file on your flash config/modprobe.d directory.

It may take some time to identify and integrate a proper fix for this issue, at which point we will remove the auto-blacklisting code.  I want to thank @JorgeB for his incredible help in identifying and isolating this issue.
 
 
 
 
 

No need, simple as put the 10G NIC be eth0 then fine.
 
If you haven't local concole, you need 1G NIC for remote management in first.

I never try iSCSI or ZFS at Unraid, just notice some performance issue when access share through virtual network bridge, no matter array pool / RAID pool, passthrough a NIC have lot better performance.

Those are individual disk SMART setting to override global SMART setting.
In "settings" -> "disk settings", you will found "Tunable (poll_attributes):" and global SMART setting too.
 

 
BTW, it look like disk spin-up was due to USB-SATA bridge beehive not relate file access , those are hardware related ( also for Unraid can't read SMART ).
I have some multi-bay USB enclosure, Unraid can read disk SMART and spindown ( but either enclosure disk spinup, all disk will spinup too ), different USB-SATA bridge will have different result.

Pls try disable spindown.