Psybernoid

So...if a drive becomes unmountable with the error I had, Unraid won't recognise it as a failed disk? That's actually terrible.

Just done that. Now stating the disk is emulated. However, no data is present. Fortunately I had anything important backed up to another device.

I have 4x2TB drives in my system. 2 of which are parity. I've lost Disk 1 (sde) with the error Unmountable: Unsupported or no file system. Fair enough, drives fail. However, my main concern is, why hasn't the parity kicked in? These files now appear to be lost. Logs attached. Appreciate any insight. totem-diagnostics-20231019-0622.zip

That worked, got an expected response. However, it remains that I cannot connect to wireguard on Unraid. If I move the NAT from my router to point at a Wireguard instance running on a VM (the VM isn't running on Unraid) that works. As soon as I move it to my Unraid server, it does not. I think there's something funky going on with having 2 physical NICs.

Not having any luck getting this to work at all. I have 2 NICs. Bridging is enabled on both. I have VLANs enabled on eth1. Anyway, long story short, it seems that Wireguard isn't listening on my server. Here's the output of lsof -i -P -n | grep UDP rpcbind 2020 rpc 6u IPv4 14656 0t0 UDP *:111 rpcbind 2020 rpc 8u IPv6 14658 0t0 UDP *:111 rpc.statd 2025 rpc 5u IPv4 13692 0t0 UDP 127.0.0.1:929 rpc.statd 2025 rpc 8u IPv4 13695 0t0 UDP *:58404 rpc.statd 2025 rpc 10u IPv6 13699 0t0 UDP *:44546 ntpd 2055 ntp 16u IPv4 11914 0t0 UDP 127.0.0.1:123 ntpd 2055 ntp 17u IPv6 9942089 0t0 UDP [fe80::8423:1eff:feb5:9a7b]:123 ntpd 2055 ntp 18u IPv6 11918 0t0 UDP [::1]:123 ntpd 2055 ntp 19u IPv4 9937148 0t0 UDP 10.100.0.133:123 avahi-dae 4448 avahi 14u IPv4 21288 0t0 UDP *:5353 avahi-dae 4448 avahi 15u IPv6 21289 0t0 UDP *:5353 avahi-dae 4448 avahi 16u IPv4 21290 0t0 UDP *:46303 avahi-dae 4448 avahi 17u IPv6 21291 0t0 UDP *:49977 dhcpcd 24541 root 0u IPv4 9938170 0t0 UDP 10.100.0.133:68 dnsmasq 25171 nobody 3u IPv4 9944874 0t0 UDP *:67 dnsmasq 25171 nobody 5u IPv4 9944877 0t0 UDP 192.168.122.1:53 nmbd 25531 root 17u IPv4 9942622 0t0 UDP *:137 nmbd 25531 root 18u IPv4 9942623 0t0 UDP *:138 nmbd 25531 root 19u IPv4 9942639 0t0 UDP 10.100.0.133:137 nmbd 25531 root 20u IPv4 9942640 0t0 UDP 10.100.0.255:137 nmbd 25531 root 21u IPv4 9942641 0t0 UDP 10.100.0.133:138 nmbd 25531 root 22u IPv4 9942642 0t0 UDP 10.100.0.255:138 nmbd 25531 root 23u IPv4 9942643 0t0 UDP 192.168.122.1:137 nmbd 25531 root 24u IPv4 9942644 0t0 UDP 192.168.122.255:137 nmbd 25531 root 25u IPv4 9942645 0t0 UDP 192.168.122.1:138 nmbd 25531 root 26u IPv4 9942646 0t0 UDP 192.168.122.255:138 nmbd 25531 root 28u IPv4 9968888 0t0 UDP 172.17.0.1:137 nmbd 25531 root 29u IPv4 9968889 0t0 UDP 172.17.255.255:137 nmbd 25531 root 30u IPv4 9968890 0t0 UDP 172.17.0.1:138 nmbd 25531 root 31u IPv4 9968891 0t0 UDP 172.17.255.255:138 wsdd 25538 root 3u IPv6 9939632 0t0 UDP *:3702 It seems UDP 51820 isn't listening at all.