JudMeherg

Hey smart people! I am on version 6.10.1. I need help figuring something out. I was able to set up a wireguard connection between two unraid servers and then get a remote SMB share mounted on my local unraid server. Where I am stuck is mapping that share as a network drive in Windows. I have plenty of other local shares mapped as network drives on my PC, but I cannot figure out the path for the remote SMB share. What am I missing? Thanks!

Just realized I should post here for help and not the LAN-to-LAN thread so here goes. I cannot get just a server to server connection to work after upgrading to 6.10.1. Below are my settings in unraid and the routers (pfsense on one end and a linksys on the other) I tried the end points as the respective duckdns addresses and as the actual IP addresses and I never got a ping back. I hope I am missing something simple. Any help would be greatly appreciated! Well I am happy to say it works now...I did not change anything in my config, but I am getting handshakes. Wish I could offer some advice to anyone else that has an issue like mine, but I got nothing.

Moved to Wireguard Quickstart thread

Oh boy. I will just replace it. Seems like the SMART action. Telegram notifications have been configured. Thanks for the help!

Thanks! Could you point out where you see those errors? In the Disk3 page the SMART error log says "no errors logged", but the SMART self-test history shows "Completed without error" on the higher hour tests (newest test?), but the lower hour test (older tests?) show "Completed: read failure". I was just looking into setting up notifications. Thanks!

I logged into my Unraid server to check for updates and found a disk disabled. I think it is a disk that has thrown a couple of errors in the past, but I am not sure. My question is, would it be best to go ahead and replace it or try to recover the drive before swapping it out? Attached is the SMART download and Diagnostics. tower-smart-20220412-1131.ziptower-diagnostics-20220412-1136.zip Uptime is 10 days and last parity check was yesterday with zero errors.