Vr2Io

12.3.1.2 no problem. You can enable web debug logging and check the error in web console 20:51:01.642 HTP: Command 20:51:01.651 SRC: WebCommand from 0.0.0.0 20:51:01.653 HTP: Bad userid and/or password 20:54:41.001 HTP: Command 20:54:41.006 SRC: WebCommand from 192.168.X.X 20:54:41.009 CMD: Grp 0, Cmd 'STATUS', Idx 1, Len 1, Pld 8, Data '8'

Only powering hard disk exclude laptop ? I notice disk will spindown, if only powering hard disk ( from 5 to 2 now ) then the loading may be too low. So, you could try not spindown and check any different. And what is the input voltage ?

Usually it means bottleneck not on cache-drive. Confirm actual wifi throughput and test in wire path.

By apps / docker ? Notice a virtual interface with private address 10.19.1.5 have SMB service, what's that ? smbd 31765 root 35u IPv4 7746309 0t0 TCP 10.19.1.5:445->10.19.1.1:49937 (ESTABLISHED) zteb4iim7w: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 2800 inet 10.19.1.5 netmask 255.255.255.0 broadcast 10.19.1.255 inet6 fe80::d838:56ff:fe96:43e2 prefixlen 64 scopeid 0x20<link> ether da:38:56:96:43:e2 txqueuelen 1000 (Ethernet) RX packets 13602305 bytes 15614117860 (14.5 GiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 8446855 bytes 5871628423 (5.4 GiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 File copy on 18-Dec or 21-Dec ? Dec 21 19:59:14 S-DeathTheHusky smbd[4538]: [2022/12/21 19:59:14.303110, 0] ../../source3/smbd/files.c:1199(synthetic_pathref) Dec 21 19:59:14 S-DeathTheHusky smbd[4538]: synthetic_pathref: opening [Furry - DeathTheHusky/1492084907.deathofwarqc_minecraft_skin.png] failed Dec 21 19:59:14 S-DeathTheHusky smbd[4538]: [2022/12/21 19:59:14.335009, 0] ../../source3/smbd/files.c:1199(synthetic_pathref) Dec 21 19:59:14 S-DeathTheHusky smbd[4538]: synthetic_pathref: opening [Furry - DeathTheHusky/boop.png] failed Dec 21 19:59:14 S-DeathTheHusky smbd[4538]: [2022/12/21 19:59:14.413704, 0] ../../source3/smbd/files.c:1199(synthetic_pathref) Dec 21 19:59:14 S-DeathTheHusky smbd[4538]: synthetic_pathref: opening [Furry - DeathTheHusky/Bwark icon.gif] failed Dec 21 19:59:14 S-DeathTheHusky smbd[4538]: [2022/12/21 19:59:14.491381, 0] ../../source3/smbd/files.c:1199(synthetic_pathref) Dec 21 19:59:14 S-DeathTheHusky smbd[4538]: synthetic_pathref: opening [Furry - DeathTheHusky/Death Collection 2016-2017 by katsuke.png] failed Dec 21 19:59:14 S-DeathTheHusky smbd[4538]: [2022/12/21 19:59:14.766356, 0] ../../source3/smbd/files.c:1199(synthetic_pathref) Dec 21 19:59:14 S-DeathTheHusky smbd[4538]: synthetic_pathref: opening [Furry - DeathTheHusky/Energy.jpg] failed Dec 21 19:59:14 S-DeathTheHusky smbd[4538]: [2022/12/21 19:59:14.810003, 0] ../../source3/smbd/files.c:1199(synthetic_pathref) Dec 21 19:59:14 S-DeathTheHusky smbd[4538]: synthetic_pathref: opening [Furry - DeathTheHusky/photo_2020-10-21_05-22-28.jpg] failed Dec 21 19:59:14 S-DeathTheHusky smbd[4538]: [2022/12/21 19:59:14.882425, 0] ../../source3/smbd/files.c:1199(synthetic_pathref) Dec 21 19:59:14 S-DeathTheHusky smbd[4538]: synthetic_pathref: opening [Furry - DeathTheHusky/Adrian/photo_2021-03-04_05-20-59.jpg] failed Dec 21 19:59:14 S-DeathTheHusky smbd[4538]: [2022/12/21 19:59:14.948372, 0] ../../source3/smbd/files.c:1199(synthetic_pathref) Dec 21 19:59:14 S-DeathTheHusky smbd[4538]: synthetic_pathref: opening [Furry - DeathTheHusky/Casparr/death4.png] failed Dec 21 19:59:15 S-DeathTheHusky smbd[4538]: [2022/12/21 19:59:15.013776, 0] ../../source3/smbd/files.c:1199(synthetic_pathref) Dec 21 19:59:15 S-DeathTheHusky smbd[4538]: synthetic_pathref: opening [Furry - DeathTheHusky/Casparr/DeathTheHusky.png] failed Dec 21 19:59:15 S-DeathTheHusky smbd[4538]: [2022/12/21 19:59:15.082783, 0] ../../source3/smbd/files.c:1199(synthetic_pathref) time="2022-12-18T20:33:50+01:00" level=warning msg="containerd config version `1` has been deprecated and will be removed in containerd v2.0, please switch to version `2`, see https://github.com/containerd/containerd/blob/main/docs/PLUGINS.md#version-header" time="2022-12-18T20:36:52.171321391+01:00" level=info msg="loading plugin \"io.containerd.event.v1.publisher\"..." runtime=io.containerd.runc.v2 type=io.containerd.event.v1 time="2022-12-18T20:36:52.171358128+01:00" level=info msg="loading plugin \"io.containerd.internal.v1.shutdown\"..." runtime=io.containerd.runc.v2 type=io.containerd.internal.v1 time="2022-12-18T20:36:52.171366554+01:00" level=info msg="loading plugin \"io.containerd.ttrpc.v1.task\"..." runtime=io.containerd.runc.v2 type=io.containerd.ttrpc.v1 time="2022-12-18T20:36:52.171472012+01:00" level=info msg="starting signal loop" namespace=moby path=/run/docker/containerd/daemon/io.containerd.runtime.v2.task/moby/c349d176ecdd8855b68f8ed63cd2a2fd77e0c925f696eff61ac2ea6754c64fd8 pid=21265 runtime=io.containerd.runc.v2 time="2022-12-18T20:45:06.494713863+01:00" level=info msg="loading plugin \"io.containerd.event.v1.publisher\"..." runtime=io.containerd.runc.v2 type=io.containerd.event.v1 time="2022-12-18T20:45:06.494753218+01:00" level=info msg="loading plugin \"io.containerd.internal.v1.shutdown\"..." runtime=io.containerd.runc.v2 type=io.containerd.internal.v1 time="2022-12-18T20:45:06.494761849+01:00" level=info msg="loading plugin \"io.containerd.ttrpc.v1.task\"..." runtime=io.containerd.runc.v2 type=io.containerd.ttrpc.v1 time="2022-12-18T20:45:06.494887028+01:00" level=info msg="starting signal loop" namespace=moby path=/run/docker/containerd/daemon/io.containerd.runtime.v2.task/moby/1d689ba3a63b3fa49dd3364c7fa4ecd0a210e8f0d26435c579dd0b502ec1efd7 pid=23792 runtime=io.containerd.runc.v2 time="2022-12-18T20:46:14.508194086+01:00" level=info msg="loading plugin \"io.containerd.event.v1.publisher\"..." runtime=io.containerd.runc.v2 type=io.containerd.event.v1 time="2022-12-18T20:46:14.508252584+01:00" level=info msg="loading plugin \"io.containerd.internal.v1.shutdown\"..." runtime=io.containerd.runc.v2 type=io.containerd.internal.v1 time="2022-12-18T20:46:14.508261274+01:00" level=info msg="loading plugin \"io.containerd.ttrpc.v1.task\"..." runtime=io.containerd.runc.v2 type=io.containerd.ttrpc.v1 time="2022-12-18T20:46:14.508484068+01:00" level=info msg="starting signal loop" namespace=moby path=/run/docker/containerd/daemon/io.containerd.runtime.v2.task/moby/fbf72f6a3e97507ee55ed104bf8d77db3652fed4ba82696de39ed39b20b3499d pid=24552 runtime=io.containerd.runc.v2 time="2022-12-18T20:50:43.224854482+01:00" level=info msg="loading plugin \"io.containerd.event.v1.publisher\"..." runtime=io.containerd.runc.v2 type=io.containerd.event.v1 time="2022-12-18T20:50:43.224903803+01:00" level=info msg="loading plugin \"io.containerd.internal.v1.shutdown\"..." runtime=io.containerd.runc.v2 type=io.containerd.internal.v1 time="2022-12-18T20:50:43.224912877+01:00" level=info msg="loading plugin \"io.containerd.ttrpc.v1.task\"..." runtime=io.containerd.runc.v2 type=io.containerd.ttrpc.v1 time="2022-12-18T20:50:43.224999470+01:00" level=info msg="starting signal loop" namespace=moby path=/run/docker/containerd/daemon/io.containerd.runtime.v2.task/moby/27d949de3caad21a432289beeca9ca138f920265d8bb185338b48f83492d4fe2 pid=26810 runtime=io.containerd.runc.v2 time="2022-12-18T20:56:32.250241516+01:00" level=info msg="loading plugin \"io.containerd.event.v1.publisher\"..." runtime=io.containerd.runc.v2 type=io.containerd.event.v1 time="2022-12-18T20:56:32.250275861+01:00" level=info msg="loading plugin \"io.containerd.internal.v1.shutdown\"..." runtime=io.containerd.runc.v2 type=io.containerd.internal.v1 time="2022-12-18T20:56:32.250289614+01:00" level=info msg="loading plugin \"io.containerd.ttrpc.v1.task\"..." runtime=io.containerd.runc.v2 type=io.containerd.ttrpc.v1 time="2022-12-18T20:56:32.250403727+01:00" level=info msg="starting signal loop" namespace=moby path=/run/docker/containerd/daemon/io.containerd.runtime.v2.task/moby/4adea08808c80309a2e910d004dfeeb46f983e1fad7b015650142793a0841d03 pid=29876 runtime=io.containerd.runc.v2 time="2022-12-18T21:03:32.810496729+01:00" level=info msg="loading plugin \"io.containerd.event.v1.publisher\"..." runtime=io.containerd.runc.v2 type=io.containerd.event.v1 time="2022-12-18T21:03:32.810537847+01:00" level=info msg="loading plugin \"io.containerd.internal.v1.shutdown\"..." runtime=io.containerd.runc.v2 type=io.containerd.internal.v1

You could try bridge them on existing HW.

Then return it also a good choice.

If all ( or most ) disk clicking in similar level, then it probably not a fault, and some disks have design self execute "background media scan" to ensure disk health. For my fault disk, definitely abnormal periodic vibration, it pass all test but speed drop a lot when clicking.

Pls note the different between GB and TB.

Before any recover action, does disk assignment have change after moving ? Since they are same 10TB size and all other member disk are HGST.

Simple try reboot first. Intel CPU Freq driver have 5 option, usually use top 2.

it depends on how frequently of clicking happen. Try stick a thin paper on each disk for visual check which disk in abnormal vibration when clicking happen. Today, I use my finger to feel which disk got failure and this also match the pre-fault identify ( when clicking happen, speed drop a lot and check the target disk SMART data, it will pause little bit. )

Most onboard SATA controller nor LSI HBA will got same high performance, usually problem are cause by slow disk member in array. Diskspeed docker may help you identify which disk got problem. After that test it locally by file transfer, just no array to array, use SSD / external USB3 disk as source also fine. Enable reconstruct write usually got best performance.

Then you should restart rebuild by new disk or same disk. And must confirm the power connector in good connect state.

Fine. I just want to confirm does corrected parity check still in progress. If nothing have change it likely in stop. ( I currently in rebuild, finish time will change continue )

I am not provide the screen for you, OP should check that to decide next step. Sorry to interrupt "your" thread.

That's fine, check does "estimated finish" decreasing time to time.

Won't, because disk failure and no reason to waiting it end. Today, I also replace a pre-fail data disk and a trouble SSD ( only use 3 month+ ).

This not a firewall / docker network issue, you apply VLAN to separate network(s). For me, I setup several VLAN, but one VLAN can access by others ( inter VLAN routing at router ) and I put some container in that VLAN for local public access.

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

#2 common method was HBA + SAS expander, lot of post about this.

Really cool video for ipvlan L3 mode. I do the routing in router currently , but with L3 mode, it route through in Unraid should lot more faster. ( my router throughput max at 300Mb )

For my understanding, there have three NAT docker network, but it still under br0 or br1, If br1 gateway unavailable then it shouldn't route to br0 gateway. This still what I expect. Yes I doubt that, in general. Doesn't look like especially you use two independent router. If one router it may relate but I could be wrong. Due to large different network environment between you and me, so I have difficulties to perform more test or verify. Hope otherone can help you.

I can't reproduce the problem as you mention, I just simple assign docker to the network then it will route to correct gateway, no extra command or touch IP table need. Use 2 independent router would make thing simple, I also agree change to one (USG) no use. It really doesn't make sense br1 will route traffic to br0 ( or vice reverse ). I haven't assign IP to eth0.2 ( VLAN ), just set IP in docker setting, but I don't think this is the reason for the routing problem you mention.

Problem usually cause by age disk or some disk at specific region got abnormally slow. Diskspeed docker may help you identify that.

What router you use ? If you set GW 11.1 & 23.1, are you confirm router support multiple subnet ? ( subnet separate not truly network separate ). Otherwise you mess yourself. For truly network separate, you need VLAN. Or, to do your expect outcome, a solution was add a router, WAN to connect 11.1 and set the LAN be 23.1 then connect to eth1. Or, you can setup software router, but this some complicated. If you have advance router, you can do all in one even single ethernet.