Vr2Io

Seems network issue Wire <-> Pfsense <-> Wireless , does those are bridge or route ? If your AP have 2 LAN port, could you try after change as below wire <-> (LAN) AP (LAN) <-> Unraid

Work

Note with thanks, quite good.

So odd, hope never me too 🤣

When doing parity check, how much total read bandwidth reach ? no. of disk ? I want to estimate this model have how many PCIe lane allocate to the storage controller.

QNAP OS just will all up or all down, no matter put them in different pool.

BIOS detect 24G but Unarid show 32G 😵 Stable importance then how many memory useable, I would forget slot 4 if it cause problem.

Interesting and useful, my age APC not same type ( no any local display and RJ45-USB only )

If you can't found those setting in BIOS, pls forget it. If goggling you will got similar problem much and no matter old / new system, there also many different answer / solution. https://www.overclock.net/forum/24676509-post4.html DRAM Training (A stress test that occurs during POST that disables certain RAM channels if that channel is detected to be problematic) will cause less memory to be 'detected' (the RAM sticks will still show in utilities like cpu-z) The cause of the channels being problematic could be bad RAM settings or bad RAM itself. My MSI X99A XPOWER AC motherboard was very keen on disabling RAM channels, depending on the RAM settings (too aggressive overclock/timings) or memory controller (VCCSA or system agent). It's possible my RAMPAGE V was more lax in disabling RAM channels, but I could get it to happen still by being too aggressive. Try disabling your overclock, disabling XMP, using standard speeds, and see if the RAM comes back. Increase VCCSA if you deem necessary too. I don't know what CPU you have, but haswell-E system agent defaults to 0.85v, and the default 0.85v is enough for me to run 3000MHz DDR4 quad channel. So, if you confirm all stick and RAM slot work, then I would suggest you try underclock the memory from 1600Mhz to 1333Mhz and try.

Seems normal. Would you try to found any option in BIOS about memory remapping and enable it.

Pls type “dmidecode -t 17” in console and post the result.

I have Emulex NIC too, model should be OCE10102, rather old but work with Unraid (no driver for Win10)

That means OP identify problems on bonding interface only ？ Anyway, I just have trying on bonding but never use long. How about if simple config without bonding, just 2 interface and 2 subnet ?

You also can ref. below post

The NIC passthrough or used by VM (vfio-pci) ? 04:00.0 Ethernet controller [0200]: Mellanox Technologies MT26448 [ConnectX EN 10GigE, PCIe 2.0 5GT/s] [15b3:6750] (rev b0) Subsystem: Mellanox Technologies MT26448 [ConnectX EN 10GigE, PCIe 2.0 5GT/s] [15b3:0015] Kernel driver in use: vfio-pci Kernel modules: mlx4_core In, ethtool.txt, ifconfig.txt, no show of this NIC.

Pls go to the Tools tab, click on the Diagnostics icon, then click on the Download button and post the zip file. I haven't Mellanox card nor Finisar SFP+, but different type NIC / SFP+ / Switch all work well in server side and switch side.

Pls click "port up" on eth2, if you no need 3 NIC then config the 10G NIC be 1st or 2nd interface.

Your machine could handle those task easy, just try dig-out the problem.

As you have 32G RAM, could you put 2 file i.e. ~5GB each and cache both in memory and stream them will have any different ? How to put it in cache ? Just read whole file. How to know both file fully cache ? If you found no more disk activity during streaming ** I always cache media file in RAM when access, but this just because I don't want the drive spinup for watch movie only. **

If according the parity sync duration for 4TB, the speed was good, that means disk/array side should no issue too.

The network setting was normal. Does streaming buffer issue still happen if stop file transfer in eth2 ? ( Best haven't other disk activity ) Last, does test within array recovery ? I found it start on 19-Mar and complete on 20-Mar Mar 19 16:27:00 MediaNAS kernel: md: recovery thread: recon P ... Mar 19 16:27:08 MediaNAS kernel: md: recovery thread: exit status: -4 Mar 19 16:27:14 MediaNAS emhttpd: Stopping services... Mar 19 16:34:47 MediaNAS kernel: md: recovery thread: recon P ... Mar 19 16:40:52 MediaNAS kernel: md: recovery thread: exit status: -4 Mar 19 16:41:59 MediaNAS emhttpd: Stopping services... Mar 19 16:43:41 MediaNAS kernel: md: recovery thread: recon P ... Mar 19 16:44:04 MediaNAS kernel: md: recovery thread: exit status: -4 Mar 19 21:12:01 MediaNAS kernel: md: recovery thread: recon P ... Mar 20 09:26:27 MediaNAS kernel: md: recovery thread: exit status: 0 Mar 20 11:32:52 MediaNAS emhttpd: Stopping services...

Pls also check does Mellanox active or not in Unraid. Pls provide screen dump of Unraid network setting and diagnostic.

From your diagnosis, eth2 seems config with two subnet. That's I suspect problem source. Or could you simple try disconnect Eth1 and check all problem will gone ? ( This to exam problem relate Aggregate or not ) If result negative, pls provide screen dump of network setting in Unraid for ref.

Pls set Bond and Eth2 not in same IP subnet ( does Eth2 link to untag 192.168.2.x and VLAN 192.168.10.x network in smae time ? ) Usually I won't set tag+untag in same interface, if machine have more then one interface, just well config in switch side would be fine and simple. eth2: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.2.200 netmask 255.255.255.0 broadcast 192.168.2.255 inet6 fe80::226:55ff:fee5:5fbb prefixlen 64 scopeid 0x20<link> ether 00:26:55:e5:5f:bb txqueuelen 1000 (Ethernet) RX packets 288133287 bytes 438181193969 (408.0 GiB) RX errors 0 dropped 144 overruns 0 frame 0 TX packets 16044 bytes 1398463 (1.3 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 18 memory 0xdfd40000-dfd60000 eth2.10: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.10.100 netmask 255.255.255.0 broadcast 192.168.10.255 inet6 fe80::226:55ff:fee5:5fbb prefixlen 64 scopeid 0x20<link> ether 00:26:55:e5:5f:bb txqueuelen 1000 (Ethernet) RX packets 135580433 bytes 425739116534 (396.5 GiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 6326 bytes 531842 (519.3 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

Pls check Finisar 850nm multimode sfp transceiver is SFP or SFP+ type.