erikbak

Copy that, I will get a new drive and replace the disk. Seems like a good time to run tests on the other drives too.. Question - Is it normal for my dashboard to show all disks as healthy even if the extended smart test fails? If so what is the dashboard really showing is "healthy"? Attaching screenshot of the dashboard area I'm referring to. Thank you

so I ran an extended SMART test on my disk2, attached are the results. Is it time to replace this drive? WDC_WD40EFRX-68N32N0_WD-WCC7K5JCV9PN-20230812-1202.txt

I will do that, can you tell me how to disable spin down? Cant seem to find it in the settings anywhere. Thank you

I got an alert that one of my disks had 8 read errors. I shut off the system, rebooted it, and got a notification that said "Array turned good" and now reads 0 errors. I'm wondering if the issue was actually fixed or if I should be concerned and troubleshoot further. Any advice appreciated, diagnostics attached. Thank you all. phoenix-diagnostics-20230810-2156.zip

Beautiful, Second parity check completed with 0 errors. Attaching final diagnostics just for future reference. @Frank1940 & @JorgeB Thank you both so much for your guidance and time. Truly appreciated! Have a good one guys and keep up the great work. phoenix-diagnostics-20220127-1725.zip

Update on second set of checks so far: 1st check (correcting) found & corrected the same amount of errors as before. 2nd check (non correcting) is about halfway through right now and has found 0 errors so far. It's looking like the IDE setting on my last 2 SATA ports was the culprit. Will post final diagnostics after 2nd check is complete just for reference.

Thanks, started checks now. Will be back in a few days again. Hopefully this fixes it!

Cancelled the memtest and went into the BIOS to change the 2 ports using IDE mode into SATA. Should I run the parity checks the same as before? First parity check as a correcting check, then the second as non correcting?

Update: Been running memtest for almost 24 hours now with 0 errors. Any opinions on if I should let it keep running at this point? The next thing I'm going to try is @JorgeB's suggestion if I'm good to close the memtest at this point.

Got it. Started running the test a few hours ago, will update tomorrow with the results. Would you need diagnostics following the 24 hour memtest as well or just a screenshot of the memtest menu?

Where can I find memtest? Is it an application or plugin? I haven't done much maintenance on my server besides the initial setup and occasional docker installs, so my experience is below average to say the least. Appreciate the guidance.

Circling back with updated diagnostics. Seems to have found the same amount of errors on both checks. Any suggested next action? phoenix-diagnostics-20220123-0800.zip

I wasn't aware of this, thanks for shedding some light on the topic for me. I'll do as recommended from here on out.

Thanks for the tip, will look into this after I have this error situation sorted out.

Attached are screenshots of both settings, seems like they both are set to write corrections to parity checks. I will leave these both the way they are and run this first check (correcting check), then run an uncorrected parity check afterwards as recommended. Will follow up with the diagnostics afterwards. Thank you, see you in a few days!

I believe they have all been correcting checks as the "write corrections to parity" box has been check marked this whole time and I have no memory of ever changing this setting. Parity check history screenshot attached. Looking at the numbers, the errors seem to have started in January 2020. I'm trying to remember what settings I may have changed at that time but nothing is coming to mind. All of my data has been there and I haven't noticed any errors in actual use. I use the server for Plex most of the time, as well as a NAS where I connect to it to download and upload files from my computer through the network. Some more info that could be useful: 1x 8TB Parity drive 3x 4TB Data drives 1x 120GB Cache SSD 1x 16GB USB Boot drive The only dockers I use are Plex, DuckDNS for my Wireguard VPN and Krusader for moving some files around internally. Also the SMART report for all of my drives has consistently shown a "healthy" status, for whatever thats worth.

Just to confirm, a correcting check would be a parity check with the "write correction to parity" box check marked, correct? Just want to make sure there isn't any other setting I'm missing before starting the process.

I've set up unRAID on my PC a few years back, everything runs excellent except every time I do a parity check it comes back with a huge amount of errors. I tried swapping the SATA cables out once but the issue still persists. Is there anything else I can try? I'm not sure what else to look for in the diagnostics to point me in the right direction. Would greatly appreciate some guidance. phoenix-diagnostics-20220120-0639.zip

Hi gfjardim, I've been having the same issue as some others with a new 12tb HD trying to pre clear but keep getting "unRAID's signature on the MBR failed - Aborted" after is succeeds to writing the pre clear signature. I tried rebooting the server, the pre clear plug in is up to date as well. I have my logs linked below, could use any help! Log