Vr2Io

Because docker network have IPVLAN and MACVLAN mode, in IPVLAN mode, all containers use same MAC address ( real interfaces's MAC address ). Most consumer network equipment will list / count device by MAC address ones only, so you will got either one of IP's with same MAC address instead same MAC address with different IP.

03:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 06)
    Subsystem: Gigabyte Technology Co., Ltd Onboard Ethernet [1458:e000]
    Kernel modules: r8169
04:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 06)
    Subsystem: Gigabyte Technology Co., Ltd Onboard Ethernet [1458:e000]
    Kernel modules: r8169
 
You have blacklist the driver ?
 

 
 

 
 
 
 

This is docker image file usage.

In Web term try press F5 to refresh.

When in virtio NIC, the link speed just a number, it can perform more then it. ( In some physical Switch / NIC also that, i.e. RJ45-SFP+ media converter, throughput could larger/smaller then link-speed ) 
 
Someone bridge NIC in Unraid network and you may test any performance different by Windows VM. I haven't bridge NIC.

Yes all lost, in fact no matter which storage technic, it can crash/corrupt, so backup was important. Raid0 just for speed, on store and recovery.
 
Btrfs RAID0 no need all disk in same size.

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