Hello everyone.  I want to start off by saying that I am a noob when it comes to this stuff but I can follow directions well  (I was able to get unraid installed but always struggle when there are issues).  I have been running unraid since 2010.  My Parity Drive is a fairly new (less than a year) 3TB drive and disk 6 was my old parity drive.

 

Now with that said, I am seeing quite a few errors on the gui in the row of my parity drive.  Every time there is a parity check the errors seems to go up and I have been blowing it off but am now starting to get concerned.  The gui shows 8603 errors for the Parity Drive row.  There are no errors indicated on any other drive row and the parity check always indicates 0 sync errors.  I would post a screen shot but for some reason I have lost gui ability after running the parity check manually with no corrections today (Parity check usually runs monthly automatically).  I have searched the forum and unable to figure out the issue on my own so hence my post.

 

Based on feedback/instructions from other posts, I was able to obtain a syslog and I have attached that here but I have no idea how to interpret it.  I have also clicked around in UnMenu since that is the only gui accessible to me right now for some reason.  On the Smart History link it listed a bunch of graphs but had a few Red label items which are as follows:

 

JK11D1YAJ643MZ: WARNING - Reallocated_Sector_Ct has increased from 0 to 2 since 2010-12-08

JK11D1YAJ643MZ: WARNING - Reallocated_Event_Count has increased from 0 to 2 since 2010-12-08

WD-WMC1T0974371: *ERROR* - Current_Pending_Sector it is now 24 (error threshold is 5)

 

I am using Unraid RC8a.  I am not sure what else you need to know to assist me but if you direct me on how to obtain any further information I will provide it.  Thanks in advance for any help anyone provides me.  I am heading out on vacation starting tomorrow so my replies may have to be next week if I do not get any responses tonight (6/4).

syslog-2013-06-04.zip

UnMenu_Smarth_History_Errors.txt

Quick glance says your parity drive is failing, and should be replaced now. You are currently at risk of data loss if any of your other drives fails before you get a valid parity drive in place. Make sure you run a parity check after you replace the drive and build parity.

 

Ideally, you should shut down the machine now, get a new disk to use for parity, and preclear it in another machine to make sure the new drive isn't bad (happens more often than it should) and only then power up your main unraid machine with the new tested drive installed as parity.

 

If you have backups of all your data like you should, then you can be a little more lazy and just replace the parity disk when you have a chance. If you have no backups, you need to proceed very carefully to avoid data loss.

Ok so this info is for sure indicating the Parity Drive and not some other drive.  I only ask cause I saw several other posts that stated that just because the errors show on the Parity Drive row does not mean it is the actual Parity Drive so want to confirm my other drives are not the ones at risk.  Thanks for the quick reply.    Oh and I am also asking cause you said at a Quick Glance.

Ok so this info is for sure indicating the Parity Drive and not some other drive.  I only ask cause I saw several other posts that stated that just because the errors show on the Parity Drive row does not mean it is the actual Parity Drive so want to confirm my other drives are not the ones at risk.  Thanks for the quick reply.    Oh and I am also asking cause you said at a Quick Glance.

It is the SMART report that indicates that there may be a problem with the parity drive.  The important values in this case are those relating to reallocated sectors.  You have  had a couple of sectors reallocated which is not necessarily bad but does indicate past failed writes that were fixed by using replacement sectors.  However you also have a lot of 'pending' sectors which equate to read failures.  It is possible that subsequent writes might fix these issues but they are worrying as they indicate data that cannot be trusted.  unRAID error correction cannot operate correctly if you have ANY pending sectors.