Darkoptix

ChatGPT plan in case it helps anyone else. (Sounds reasonable to me). There it is. Jun 17 08:26:46 UNRAID emhttpd: unclean shutdown detected And: reboot system boot Wed Jun 17 08:25 That means the server experienced an unclean shutdown sometime before June 17. Given your latest parity history: 2975 -> 2980 -> 2985 -> 0 -> 5 I think we've finally got the story: You had a long-standing parity mismatch (~3000 sectors). The recent correcting check successfully fixed it (proven by the subsequent 0). Since then, only 5 parity errors have appeared. You have a documented unclean shutdown on June 17. An unclean shutdown during active writes is one of the most common reasons to get a handful of parity errors afterward. My current conclusion I no longer think you have: a failing parity drive a failing data drive a broken Adaptec controller a persistent parity corruption problem The evidence now supports: ✅ The 2980-error issue was corrected. ✅ The array is currently healthy. ✅ The 5 new errors are very plausibly from the June 17 unclean shutdown. What I'd do now Do nothing drastic. Let the current correcting parity check finish. Then: Run a non-correcting parity check next month. Watch the error count. Interpretation: 0 errors → issue resolved. 1–10 errors after another unclean shutdown → not surprising. Hundreds/thousands of errors reappear → we reopen the investigation. One thing I would still do At some point, run Memtest overnight. Not because I think it's the primary suspect anymore, but because: 64GB non-ECC RAM storage server easy preventative validation It's no longer urgent. Bottom line The most important datapoint of the entire investigation is that you got: 2985 ↓ 0 ↓ 5 That proves parity corrections are working and that the original large mismatch is gone. Right now, your array looks much healthier than it did when we started.

Ran another check just to be sure, but 5 parity errors snuck back in. You can see the history 2975 -->2980 -->2985-->0-->now 5 unraid-diagnostics-20260620-1028.zip

Well, just like that. I ask for help, and it fixes itself lol. The RESTART then instantly do both of the checks immediately after reboot is the only thing I changed. Thanks JorgeB

So now I guess I just need to run a few more Parity checks as JorgeB recommended. Seems like I am doing the same thing over as I have already done but I have not specifically done the order. Reboot Run checked Run unchecked Although I have done 2, then 3 multiple times. It is running right now with mdResyncCorr=1

Rebooted, and I am running one with the blue Checkmark toggled ON "Write corrections to parity"

I run the parity checks on a monthly basis. The errors jumped right around the same time I replaced one 24tb parity drive with a new 24tb parity drive. I have run the Parity check - Check will start Parity-Check. (Schedule) With this, --> Write corrections to parity. Checked then immediately unchecked. The result does not reduce the error count from 2900 or so back to zero as expected. I went down a rabbit hole with ChatGPT and it seems to have ruled out bad RAM. I am not sure if this will help or hurt the process of solving the problem, but here is my diagnostic journey so far... https://chatgpt.com/share/e/6a2a1e6e-5fb4-832d-b4be-8ede9843fd11 unraid-diagnostics-20260605-1935.zip Unraid diagnostics are also attached. Happy to provide any additional information. Thanks!

Thanks for the replies. I was able to "fix" it by recreating a new Tunnel. First, I added a new wg1 like you mentioned in 7.2.4. I did this before going back to 7.2.3 so was not able to verify if just going back to 7.2.3 would have fixed the original wg0 that stopped showing up. I went back to 7.2.3, and nothing broke. Then I upgraded to 7.2.4, and nothing broke. So its all working correctly now! Thanks for the commands you shared I will keep them handy for future reference!

I have a few Docker containers that I need to be behind VPN. Previously, it has worked great to set up Tunnel wg0 as shown below. I got this all set up and working great until yesterday. I was working fine in Unraid 7.2.3, and after upgrading to 7.2.4, something stopped working very recently. I did not change anything in my settings or config. Even after I restarted it is still not working as expected. I am not able to determine if this is a 7.2.4 upgrade problem because it did not stop working directly after the upgrade. The next step I usually do is add it under the network type in the Docker config, but it disappeared and no longer shows up there. I would expect it to be listed as a Network Type "wg0" under this drop-down menu but it is no longer located there. Thanks in advance for any help!! VPN setup shown here:

Haha, yeah, I know what you are saying. I guess I should say/clarify I am really new to network speeds higher than 1gb. Well dang it, my speed dropped again, so I will have to consider other NIC. I have my HSA card plugged into the graphics slot and its working so I am not going to mess with that or move it since there will probably be the same limitations.

Haha yeah, even though I have decades of computer tinkering experience, I am pretty new to Unraid and have only had an Unraid system x under a year. Happy right now that its working at 10gb even if it is a bottlenecked 10gb. Most of my network is 2.5gb so as long as its faster than any other bottlnecks I am happy. Especially since it worked in the past for 8 months it did not raise any flags. ie with the Mellanox 3, it was instantly obvious it did not work at all. Worse case I can just put an intel 2.5gig PCI NIC in there and be happy with that if this Mellanox 4 keeps stepping down in speed.

I tried Mellanox MCX312C-XCCT and the motherboard does not recognize it at all. You are correct that the current Mellanox is not supported at full speed. I saw a line in the unraid boot up script and it appears to work up to about 8 gigs which is fine since I only have 2 gig interenet. Does not appear that there are many or any options that are full 10 Gbps on 4_1 slots. Interesting

Back to the network speed problem (could not even turn my computer on much less load UNRAID for the past 5 days haha). I am going to try the following. Yesterday ordered a OEM Mellanox MCX312C-XCCT Dual Port 10GB SFP+ ConnectX-3 Net/Adapter High Profil I tried a different DAC cable (no difference) I ordered a fiber cable because supposedly, copper is not as good at allowing the Mellanox to down regulate the speed.

All the BIOS settings are here incuding the USB settings.

Yes in case I was not clear about the BIOS fix. Over the past 4 days I have tried nearly every combination of SECURE boot ON vs OFF and I swear I have even done the actual solution at least a few times in my over 150 reboots. Step #1 was actually the solution. I am not sure if the CMOS battery removal for 30 minutes, shorting the CMOS jumpers etc was necessary as I did those before the actual fix that worked. Windows 10 Features = Other OS CSM = Enabled LAN PXE Boot Option ROM = Enabled Storage Boot Option Control = Legacy Other PCI devices = UEFI I took pictures of almost all my BIOS settings; I will try to update them in case it helps anyone. To this post, the actual settings that worked