Just ran a Parity check last night. I have it set up to run Automatically every month. I checked and I have 0 Parity Errors it appears, but I noticed I have 31 Errors on the interface next to my Parity Drive. I could of sworn last time I ran a Parity check I had the exact same amount of errors, but of course they magically go away when you click the Clear Statistics Button. No Red ball, but its making me worry like its an early warning of things to come.

 

In my Syslog I find the following errors of course condensed just to get my point out.

Feb  1 05:13:56 Tower kernel: md: disk0 read error (Errors)

Feb  1 05:13:56 Tower kernel: handle_stripe read error: 2749598488/0, count: 1 (Errors)

Feb  1 05:13:56 Tower kernel: md: disk0 read error (Errors)

Feb  1 05:13:56 Tower kernel: handle_stripe read error: 2749598496/0, count: 1 (Errors)

Feb  1 05:13:56 Tower kernel: md: disk0 read error (Errors)

Feb  1 05:13:56 Tower kernel: handle_stripe read error: 2749598504/0, count: 1 (Errors)

Feb  1 05:13:56 Tower kernel: md: disk0 read error (Errors)

ParitySmartTest.txt

syslog-2012-02-01.txt

There are some current pending sectors on the drive.  Only 8 at this point but you are going to want to pay attention to the drive and see if that number changes.

So just ignore the the 31 errors that show up? I personally don't like any errors, but it is what it is.......

 

Yeah I noticed the 8 errors and figured thats not to bad, but I don't want it creeping up to high.

Ran what Joel L suggested in this thread and it cleared up my Pending Sector errors.

http://lime-technology.com/forum/index.php?topic=18228.msg163460#msg163460

 

I'll beat the drive up some with some write/right activity across all the drives and then perform a parity check to see if I have those stripe errors any more as well as the errors that are reported on the Interface.