August 2, 20232 yr Hello, I got an email alert about disk read errors that popped up during a Parity check. Shows 336 errors on one disk. I'm not sure what this means exactly and if I should replace this disk. (Disk 1) I know this question comes up a lot but I don't really see a thread with a solution / conclusion. Thanks for the guidance I just ran an Extended SMART test on the disk and am attaching my Diagnostics. Edited August 16, 20232 yr by adminmat
August 3, 20232 yr Author If anyone has a guide on how to diagnose this issue I'd appreciate. Is this in the unRAID manual? Is this a cable issue? Is there a way to tell if the data is corrupted?
August 3, 20232 yr Community Expert It's logged as a disk problem, run an extended SMART test on disk1.
August 3, 20232 yr Author On 8/3/2023 at 5:45 AM, JorgeB said: It's logged as a disk problem, run an extended SMART test on disk1. I ran the Extended SMART test before I posted this thread. Here is the report. Thanks. Edited August 16, 20232 yr by adminmat
August 3, 20232 yr Community Expert Solution Test passed so disk is OK for now, replace/swap cables to rule that out and run another check.
August 3, 20232 yr Author 3 hours ago, JorgeB said: Test passed so disk is OK for now, replace/swap cables to rule that out and run another check. Ok so I'll change the cables and check everything physically. Then run another Extended test? Should I reboot?
August 3, 20232 yr Community Expert 20 minutes ago, adminmat said: Then run another Extended test? Run a parity check instead. 20 minutes ago, adminmat said: Should I reboot? You should power off before changing the cables.
August 8, 20232 yr Author On 8/3/2023 at 12:10 PM, JorgeB said: Run a parity check instead. You should power off before changing the cables. Swapped the SATA cable. Ran a parity check that completed with no errors. I should be good for a while then, right? I was opening and closing a cabinet the server sits on during the last parity check. That jostling could have caused it?
August 8, 20232 yr 1 hour ago, adminmat said: I was opening and closing a cabinet the server sits on during the last parity check. That jostling could have caused it? https://www.techpowerup.com/80711/dont-yell-at-your-hard-drives-sun-engineer
August 8, 20232 yr Author 7 minutes ago, JonathanM said: https://www.techpowerup.com/80711/dont-yell-at-your-hard-drives-sun-engineer Problem solved. I will speak softly and positively to my HDDs from now on 😆
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.