Declan

I found this thread, https://www.reddit.com/r/WireGuard/comments/m16v3k/unable_to_start_wg_interface_with_wgquick_up/ After removing the DNS field from my config it works. Hope it helps if anyone else finds the same issue

root@helios4:~# lsmod | grep 'tun\|wireguard' tun 40960 0 wireguard 61440 0 curve25519_neon 28672 1 wireguard libcurve25519_generic 20480 2 curve25519_neon,wireguard libchacha20poly1305 16384 1 wireguard ip6_udp_tunnel 16384 1 wireguard udp_tunnel 20480 1 wireguard libblake2s 16384 1 wireguard

Following the install instructions from: https://www.wireguard.com/install/#debian-module-tools Wireguard server is working correctly as I have other devices working. I recieve the following output: root@helios4:/etc/wireguard# wg-quick up PiVPNHelios4 [#] ip link add PiVPNHelios4 type wireguard [#] wg setconf PiVPNHelios4 /dev/fd/63 [#] ip -4 address add 10.6.0.5/24 dev PiVPNHelios4 [#] ip link set mtu 1420 up dev PiVPNHelios4 [#] resolvconf -a tun.PiVPNHelios4 -m 0 -x Unknown interface 'tun': No such device [#] ip link delete dev PiVPNHelios4 Have I setup something wrong with wireguard? or is it not fully supported? Solution: remove the DNS value from the configuration

@gprovost I ordered a UK power supply: https://www.amazon.co.uk/gp/product/B07VL83VCP Arrived yesterday, so far everything is back up and running. Very much appreciate the help troubleshooting, thanks

With 2 HHDs plugged in: 5V: 5.08 12V: fluctuated with range of 10.09 - 12.2 with the hdd sounding like they were failing to start up repeatedly Also, armbianmonitor -U output: https://paste.systemli.org/?7b660a360e84f4ad#99fbr5bfjwR6yij3bcKv1xufgu541hWvo4CV9a9PPr6w I now believe it is the power supply. Do you have a recommendation for a replacement power supply?

@gprovost Thanks for the suggestions, Using a voltmeter both molex measured 5V rail: 5.15-5.21 V 12V rail: 12.27 V Therefore its not the power supply?

New to this forum, seems like the best place to ask this, My Helios4 encountered some errors and now will not boot up. It has OMV running from an SD card supplied with the kit and has 4 data drives, synced with Snapraid. The first sign was monit sent me an emails with a parity disc 1: Filesystem flags changed Service filesystem_srv_dev-disk-by-label-Parity1 Description: filesystem flags changed to 0xc00 Status failed Service mountpoint_srv_dev-disk-by-label-Parity1 Description: status failed (1) -- /srv/dev-disk-by-label-Parity1 is not a mountpoint Data disc 2 Filesystem flags changed Service filesystem_srv_dev-disk-by-label-Data2 Description: filesystem flags changed to 0x1009 These emails were sent just after midnight which has me thinking that a daily service may have changed something, possibly unattended-upgrades? It does now not fully boot when connected to the serial port this appears to be the issue: [ TIME ] Timed out waiting for device dev-disk-by\x2dlabel-Data2.device With all the discs timing out, the discs do not seem to power on, which has me thinking it might be a power supply issue Serial output: https://paste.systemli.org/?d42d768fe6789c45#7HrQSfMdpemMUeQMX3hSJeXHfw1yNeDGdXM9iHpt88CE serial journalctl -xb output: https://paste.systemli.org/?70aaaa320420d245#Cu1PPmKjpTbodMdjcprefi3TcAaXXnPwpFpNZccxtdid I have tried to figure it out but am stuck, Anyone have any ideas? Happy to provide more information if needed Thanks in advance