Vr2Io

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.

You could ignore those error.

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.

Pls uninstall corefreq.plg - 2021.07.13

Pls try cross flash the HBA to IT mode.
 
https://dan.langille.org/2020/10/07/dell-r720-flashing-dell-perc-h710-mini-into-it-mode/
 
I haven't such RAID card, in the guide it state you may need remove the RAID battery from the adapter, pls go through the doc and decide flash or not.
 
https://fohdeesha.com/docs/perc.html
 

You have too much disk if all power by single PSU.
 
I will try disconnect 2 disk power ( non array disk ) then add parity to check does power down or not.

You have too much disk if all power by single PSU.
 
I will try disconnect 2 disk power ( non array disk ) then add parity to check does power down or not.

https://www.tomshardware.com/reviews/crucial-p2-m-2-nvme-ssd/2
 
However, the QLC variant averaged USB 2.0-like speeds of just 40 MBps after the SLC cache was full.
 
So slow write performance should be normal.
 

In this case, preserve or not not much different for array, because s/n incorrect and you need to reassign.