I just got a notification from my server that my parity drive has 62 errors on it. 

 

I hope I caught it early enough. 

 

Should I be concerned? Am I in danger? What should be my next steps? 

 

EDIT: I last did a parity check 17 days ago. If I run one will this affect me? 

 

gibson-diagnostics-20240707-2025.zip

Edited July 8, 20241 yr by urbanracer34
add info

It's logged as a disk problem, run an extended SMART test.

6 hours ago, JorgeB said:

It's logged as a disk problem, run an extended SMART test.

How do I do that? 

Click on the disk, then self test

Running now. How long will it take? 

Edited July 8, 20241 yr by urbanracer34

40 minutes ago, urbanracer34 said:

Running now. How long will it take? 

Something like 1.5 to 2 hours per TB is typical.   Note that the progress is only updated in 10% increments.

SMART Test completed without error. 

 

What's next? 

Keep monitoring, but any more similar errors I would replace the disk.

1 minute ago, JorgeB said:

Keep monitoring, but any more similar errors I would replace the disk.

So use as normal and if it keeps erroring out, replace the drive? 

Yep

Thanks! 

 

EDIT: Is it safe to do a parity check? 

Edited July 9, 20241 yr by urbanracer34

Yes, but run a non correcting one.

23 hours ago, JorgeB said:

Yes, but run a non correcting one.

So I ran a non-correcting parity check and everything turned out fine. No errors incrementing. Is it safe to do a correcting one? 

Should be, but were there any sync errors? If there weren't there's no point, and non correcting is always safer, unless sync errors are expected.

On 7/10/2024 at 8:52 AM, JorgeB said:

Should be, but were there any sync errors? If there weren't there's no point, and non correcting is always safer, unless sync errors are expected.

 

No sync errors at all. Is it "normal" to run the parity check as non correcting? 

It's recommended, correcting parity check can in some rare cases corrupt parity if read errors are found in other disks.