Vr2Io

Yes, this to verify does problem come from power source switching.

First to verify does PC unresponsive due to power source switching, disable APCUPSD then try turn off and on main power source.

Matter server must in Network mode : host. Your HA in VM or docker ?

But still showing discharging battery, lucky NUT won't go to shutdown announcement. Anyway, this should be UPS self issue and other person also report that.

You may request LT to add the driver, otherwise you need build or compile yourself. I don't know how to do that.

First time seeing this ethernet controller https://www.cnx-software.com/2024/11/26/geekom-mini-air12-lite-review-part-3-ubuntu-24-04-on-a-low-cost-mini-pc/ The first problem is that Ethernet does not work as while the Motorcomm YT6801 controller is detected, there’s no driver in use as reported by inxi. Luckily, there’s a driver on GitHub that we can install relatively easily on Ubuntu:

Sure.

I don't mean not trust your founding, but as mention, I haven't found HA will that, no matter it is VM or docker. Below are some capture for your ref. too. Capture the source.mac ( HA ) and destination.mac ( router ), you will got Internet traffic only. But if by source.mac ( HA ), then you will see local traffic also. Could you try setup a new HA for testing / troubleshoot ?

If only HA VM will route local subnet traffic through gateway then it is HA problem. But I never found this with HA in VM or Docker. Pls also note, local traffic ( same subnet ) won't route to gateway, so those traffic go out from the interface ( could be virtual interface binding ) are not in same subnet actually.

You should try disable bonding, those usually trouble and your problem also self fix in few min.

正常是兩邊各自用 1g 口上網, 與平常一樣, 之後兩邊加 10g 口直連, 同一網段 (異於 1g), 不設網关.

👍👍I never touch / add any IPv6 setting in Unraid, just enable IPv6 only in Unraid, physical network still IPv4 only.

Sorry no actual model have recommend because long time haven't buy any UPS, existing APC still work. Nowadays APC may not a must go choice, you may consider Eaton or Cyberpower.

I would suggest you try APCUPSD, if battery never indicate fully charge, you should return it and avoid APC BX series UPS. It look like BX series have different trouble.

Each error different in 11hrs, it look like battery can't charge to 100% and stay in 99% so cause those error. But those are my guess only. For 24v UPS, 27.2v actually fully charge for APC design. So I believe it won't raise. There are other similar report in this forum too.

Recommend need, for example I set my mobile can access different vlan, other member and guest only can access Internet. In general, you should put HA, MQTT, Z2M in same vlan, but as result those can access each other in all, if you want further protect HA, then HA must put to standalone vlan, but this will increase firewall complexity. You haven't mention WiFi AP, in fact you need a vlan AP, otherwise, all client in same vlan, then you need create many firewall rule to route or block traffic cross vlan. Expect that, but I only use one 10G for all, much simple then use multiple interface.

You have passthrough all NIC 01:00.0 Ethernet controller [0200]: Intel Corporation Ethernet Controller I226-V [8086:125c] (rev 04) Subsystem: Intel Corporation Device [8086:0000] Kernel driver in use: vfio-pci Kernel modules: igc 02:00.0 Ethernet controller [0200]: Intel Corporation Ethernet Controller I226-V [8086:125c] (rev 04) Subsystem: Intel Corporation Device [8086:0000] Kernel driver in use: vfio-pci Kernel modules: igc 03:00.0 Ethernet controller [0200]: Intel Corporation Ethernet Controller I226-V [8086:125c] (rev 04) Subsystem: Intel Corporation Device [8086:0000] Kernel driver in use: vfio-pci Kernel modules: igc 04:00.0 Ethernet controller [0200]: Intel Corporation Ethernet Controller I226-V [8086:125c] (rev 04) Subsystem: Intel Corporation Device [8086:0000] Kernel driver in use: vfio-pci Kernel modules: igc 05:00.0 Ethernet controller [0200]: Intel Corporation Ethernet Controller I226-V [8086:125c] (rev 04) Subsystem: Intel Corporation Device [8086:0000] Kernel driver in use: vfio-pci Kernel modules: igc

Those not relate this post, we talking about IPv6 communicate to VM ( Matter ) issue. The link post is about 2.4G radio ( USB radio stick ), if running Thread and Zigbee in same time then will unstable. Pls note BLE / WiFi / Zigbee / Thread all in same 2.4G, so those radio controller can support different protocol once with suitable firmware. An example for easy understand, when IoT device in initial state, it will run in BLE first, after commissioning then it will switch to WiFi mode ( or Thread ).

Welcome and note.

I notice disk 2-9 usage are same, this look like you setting most-free allocation method, if transfer small size file, then it will further affect the performance because concurrent file will be writing to PARITY array. I will check the diagnostics when I home, won't check with mobile.

Parity check should complete within 14hrs for 6TB, If no other disk activity. It indicate something limiting higest performance. What controller use to connect those disk. Pls provide diagnostics.

Problem likely once Synology enter standby mode when UPS on battery timer reach, as below post said you need reboot Synology ( to exit standby mode ), then reboot Unraid. Suggest solution are don't use Synology be NUT server or use other platform / device as NUT server. Or you can swap Unriad be NUT master and Synology as client, but if that, Synology must react before Unraid shutdown. Or very simple, restart Synology first. https://community.synology.com/enu/forum/1/post/188928

When UPS at mains, even low battery it wouldn't flag other to shutdown, I correct this first. Could you confirm does Synology correctly indicate Unraid, UPS in On-line instead orher states.

The best solution was buying some cheaper 10G switch, then PC and Unraid each have one cable to switch.

After power outage, the battery need charge up again, you need further check does battery / runtime still under triggering setting. It also a case, when you boot up Unraid, it will draw max power, then runtime will drop significant before completely boot up.