I have replaced two drives now, one when I started getting errors, and one that I replaced with a smaller drive.

 

This are the only parity errors I have had since I built my server, and they both took place immediately after replacing the drive.

 

The 1st was about a month ago, and the second today.  When the drive rebuild was complete, it read as if it had just completed a parity check with  no errors.  As I was about to go to sleep, remembering what took place last time I figured I'd run a check just to be safe.  Immediately I got 5 errors. 

 

From they syslog:

Apr 22 01:58:06 TODD-Svr kernel: mdcmd (66): check CORRECT (unRAID engine)

Apr 22 01:58:06 TODD-Svr kernel: md: recovery thread woken up ... (unRAID engine)

Apr 22 01:58:06 TODD-Svr kernel: md: recovery thread checking parity... (unRAID engine)

Apr 22 01:58:06 TODD-Svr kernel: md: using 1152k window, over a total of 1953514552 blocks. (unRAID engine)

Apr 22 01:58:06 TODD-Svr kernel: md: parity incorrect: 18240 (Errors)

Apr 22 01:58:06 TODD-Svr kernel: md: parity incorrect: 19600 (Errors)

Apr 22 01:58:06 TODD-Svr kernel: md: parity incorrect: 19608 (Errors)

Apr 22 01:58:06 TODD-Svr kernel: md: parity incorrect: 19624 (Errors)

Apr 22 01:58:06 TODD-Svr kernel: md: parity incorrect: 19632 (Errors)

Apr 22 01:58:08 TODD-Svr emhttp: disk_temperature: ATTR_Temperature_Celsius not found (Other emhttp)

Apr 22 01:59:05 TODD-Svr emhttp: disk_temperature: ATTR_Temperature_Celsius not found (Other emhttp)

Apr 22 01:59:07 TODD-Svr emhttp: shcmd (49): /etc/rc.d/rc.samba stop | logger (Other emhttp)

Apr 22 01:59:07 TODD-Svr emhttp: shcmd (50): /etc/rc.d/rc.nfsd stop | logger (Other emhttp)

Apr 22 01:59:08 TODD-Svr emhttp: Spinning up all drives... (Other emhttp)

 

I started the parity check from the unRAID Main Screen.  Also remembering that I was told even though it reads "corrected" it doesn't really correct errors when run this way, so I stopped the check (as you will see above I actually stopped the array instead of just stopping the parity check).  Then I decided probably better to just run the full parity check and see what turns up before doing a check and correct from the unMENU screen.  So I restarted the array and the parity check, but this time no 5 errors.  Did it actually correct them this time?  If so why?

 

Just a little confused and dont want to screw something up.  I am now re-running the check and will post here in the AM if anything else turns up.  It is already further into the check than last time.  Those 5 errors came up almost immediately. 

 

Can anyone tell what they are from those lines out of the syslog?

 

Any help is appreciated, thanks.

 

System listed below in signature is accurate.

It's a disk rebuild bug. The errors are only on the parity drive correct them and all will be well.

It's a disk rebuild bug. The errors are only on the parity drive correct them and all will be well.

 

Thanks!

 

No other errors appeared. 

 

- Last time I had to run a check / repair on the unMENU screen, why did it fix them with the regular check from unRAID?

- So this is a bug in 4.7?  Is it fixed in V5?  (will be upgrading in the next week or so when I have time)

- Should I always run a check and repair after any drive replacement?

 

Always run a check-only. If its 5 or less errors then check and repair. If its more than 5 the all the disks need to examined for problems. It is fixed in the latest betas.

Always run a check-only. If its 5 or less errors then check and repair. If its more than 5 the all the disks need to examined for problems. It is fixed in the latest betas.

 

Thanks!