AW139

I added back the pool device using the identical name as before, and right away all services came back online. I didn't need to change anything else, which was great. The system log did show a number of errors on the nvme drive, but since it's been rebooted I didn't capture any of those errors to show them here. SMART test on the drive now shows nothing wrong, so I guess I just got insanely lucky. I have a backup now of the entire drive, so if it were to fail again I can restore from backup. No idea if this was a one-time problem or signs of an impending drive failure, but either way I'm very happy I didn't lose everything.

Dug through my logs, and the relevant error is: emhttpd: no mountpoint along path: /mnt/cache_docker_vms/system/docker "cache_docker_vms" was the name of the "failed" NVMePool Device. If I add a pool device with this exact name, will it reformat the drive?

unraid-diagnostics-20250228-1717.zip

Hello, A couple days I awoke to all my dockers being offline. Checked, and for whatever reason the NVMe disk that has the docker image, all my plex config data, and VMs wasn't showing up in pool devices, unsassigned devices, or under tools---system devices. I feared a drive failure. I didn't have physical access at the time, so I attempted a couple of reboots remotely to to avail. Today I had physical access again, so I pulled my server and reseated the NVNe drive. AMAZING! The devices is now showing up in unassigned devices. I can brows it with MC, and I'm currently making a backup of it on my array. The problem is that it's no longer listed under POOL DEVICES, so its not linked to anything. Docker services won't start, because it has no idea where the docker image is. How to I configure it so it's back in Pool Devices as before without having to reconfigure everything from scratch? Thanks!!!!

Just configure all your peers, and once you are finished go in and edit the file again. Any changed to peers you make after that will necessitate you re-edditing the file.

I messed around with it, and the spaces don't seem to affect it. EDIT - Got remote tunneled access to work correctly. I had misconfigured my static route on my router.

I edit the file after I completed the changes, so right now I THINK it looks all correct. Which spaces are critical? Thanks. [Interface] #WireGuard PrivateKey= REMOVED Address=10.253.0.1 ListenPort=51820 PostUp=logger -t wireguard 'Tunnel WireGuard-wg0 started' PostUp=iptables -t nat -A POSTROUTING -s 10.253.0.0/24 -o br0 -j MASQUERADE PostDown=logger -t wireguard 'Tunnel WireGuard-wg0 stopped' PostDown=iptables -t nat -D POSTROUTING -s 10.253.0.0/24 -o br0 -j MASQUERADE PostUp=ip -4 route flush table 200 PostUp=ip -4 route add default via 10.253.0.1 table 200 PostUp=ip -4 route add 192.168.1.0/24 via 192.168.1.1 table 200 PostDown=ip -4 route flush table 200 PostDown=ip -4 route add unreachable default table 200 PostDown=ip -4 route add 192.168.1.0/24 via 192.168.1.1 table 200

If you do need to edit that file, try using midnight commander by typing "mc" in the terminal window and hitting enter. Worked well for me.

Duh... thanks! I edited the .conf file with midnight commander, and that seems to solve the problem of connecting WireGuard. I am able to connect to my LAN from outside the network now. For whatever reason I still can't get WAN access on the remote peer with Wireguard active. This was not a problem at all until I updated unraid!!!

This may be a dumb question, but I'm experiencing the exact problem but I can't seem to find any wg0.conf file on Unraid. I have configured that file on Ubuntu, but I can't seem to find it anywhere on undraid. There doesn't appear to be an /etc/wireguard folder as far as I can tell. Any idea where the wireguard GUI stores these files? Thanks

This process worked for me. Just remember (unlike me!) that the claim token expires in 5 minutes. I was banging my head against the wall trying to figure out why my terminal command wasn't working.