jherrinjr

So far things are working so much better than before, it looks like I was drawing more power than my power supply could handle. Thank you @JorgeB for your help!!

Sooooo....... I think I have figured it out. I swapped out the power supply and it seems to be working now. It seems like it was a power supply issue. Before it would fail right off the bat, its been syncing for about 90 minutes and no errors so far.

Here are the logs, I restarted the server and then restarted the array and got the same errors. Thank you @JorgeB for taking a look into these for me. syslog.txt

I swapped the drive to another bay and the same issue is happening to the same disk. There is one sata cable per bay so by swapping it I have moved it to a different sata cable. I am working on pulling logs but running into the same issue as before where they wont load and if I try to download it downloads an empty log file.

Here is that smart report HUH721212ALE601_8CK73M2F-20240927-1131.txt

Ok, I’ll try that when I get home. Side note, It’s in a 5 drive hot swap bay. And earlier I swapped it with disk 4 which is in bay slot 5 (different backplane port and different hba cable but same hba) and the issue stayed on disk 1.

I went ahead and rebooted immediately I checked the logs page and it was able to open but none of the errors were there. Also I couldn't open previous. So I put all of the drives into place and started the array. It reformatted disk one and started the parity sync. Immediately Disk 1 started recording thousands of errors. so i paused the parity sync and took the screenshot and tried to open system log, but again system log stuck at the Unraid loading logo. But the download button worked and here is that log. 130mb.... syslog.txt

System log under tools wont load anymore, it just sits on the unraid logo loading screen so I went to /boot/logs and found these folders and this file. prospect-diagnostics-20240208-2030.zip prospect-diagnostics-20240423-2022.zip syslog-previous Syslog-previous looked like the closest but its only from two september 22 to september 24.... syslog-previous

Do I need to sanitize them or can I just download from unraid and post?

Story time! I have a server with 4 data drives and 1 parity drive. The data is a remote copy and a secondary plex server mostly. Recently after a move Disk 1 showed disabled with read errors. I ran smart test and everything was fine. I did other testing that I dont really remember and eventually erased the drive and re-added it. It was sluggish repairing so I replaced the HBA, which led to new sata cables and then new computer. (its a dell small form factor so i just swapped it with the same model). Everything rebuilds and is working great for about 2-3 weeks. Then boom disabled with read errors again. I check smart status and its totally fine, no read errors... Either way I have a cold spare that has gone through preclear (pre read, full write, post read - no errors) and I swap that in start the rebuild and go touch grass. I come back to disk 1 disabled read errors, which happened about 10 minutes after it started. At this point i am thinking that the backplane that I am plugging into is busted so i move the drives into different slots. Boom disk 1 disabled read errors (again after about 10 minutes), even though it is in a different slot now. Disk 1 and party are the newest and largest drives and are also the exact same make and model. So then I am thinking that the parity disk has an issue. So I take disk one and parity disk and run preclear (just full 0 write this time), that completes successfully. I then clear the config (array and pool) and start the array with a parity sync, and boom disk 1 is nothing but errors and about 10 minutes into that I get disk 1 disabled with read errors. I am running another preclear (pre-read, full write, pre read) which has been running for about an hour now with 0 errors on that disk 1. I have the logs but I think i need to sanitize them, let me know what i need to do and then I can attach them. Help me ObiWan, you are my only hope!

Are you using privatevpn with wireguard also?

So I have a pretty interesting issue if anyone wants to help me take a look at it. I am running latest version of Unraid with latest version of arch-delugevpn. I have mostly gotten privatevpn wireguard working. I can upload and download for about 5 minutes, and then it all drops to 0, and at the same time I lose all network in my house. I have tried with 2 different vpns but only used openvpn with them and it all works fine. I downloaded qbittorrent and privatevpn wireguard worked with it, but did the same thing. There also doesn't seem to be anything interesting in the logs. Any ideas what logs to check or maybe what to look for on my router? Also just saw that 6.12.3 is out, probably won't change anything but installing that now to test. Router FreshTomato 2023.3 Unraid 6.12.2 PrivateVPN Wireguard 2023-07-15 00:09:34,821 DEBG 'start-script' stdout output: [debug] Valid local IP address from tunnel acquired '10.34.118.33' 2023-07-15 00:09:34,821 DEBG 'start-script' stdout output: [debug] Valid gateway IP address from tunnel acquired '' 2023-07-15 00:09:34,821 DEBG 'start-script' stdout output: [debug] Checking we can resolve name 'www.google.com' to address... 2023-07-15 00:09:49,845 DEBG 'start-script' stdout output: [debug] Having issues resolving name 'www.google.com' [debug] Retrying in 5 secs... 2023-07-15 00:09:49,846 DEBG 'start-script' stdout output: [debug] 11 retries left 2023-07-15 00:10:00,373 DEBG 'watchdog-script' stdout output: [debug] Checking we can resolve name 'www.google.com' to address... 2023-07-15 00:10:09,872 DEBG 'start-script' stdout output: [debug] Having issues resolving name 'www.google.com' [debug] Retrying in 5 secs... [debug] 10 retries left 2023-07-15 00:10:15,398 DEBG 'watchdog-script' stdout output: [debug] Having issues resolving name 'www.google.com' [debug] Retrying in 5 secs... 2023-07-15 00:10:15,398 DEBG 'watchdog-script' stdout output: [debug] 11 retries left 2023-07-15 00:10:29,897 DEBG 'start-script' stdout output: [debug] Having issues resolving name 'www.google.com' [debug] Retrying in 5 secs... [debug] 9 retries left 2023-07-15 00:10:35,423 DEBG 'watchdog-script' stdout output: [debug] Having issues resolving name 'www.google.com' [debug] Retrying in 5 secs... [debug] 10 retries left