nightanole Posted May 21, 2013 Share Posted May 21, 2013 So i did my 2nd parity check after i built the box 30 days ago. I got over 6000 errors on the parity drive, but it said no correction was needed. I ran a quick smart test on all drives and they all passed. I did a smart log on my parity, and it says 440 pending sectors. Should i rma the drive? SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 193 193 051 Pre-fail Always - 21609 3 Spin_Up_Time 0x0027 140 134 021 Pre-fail Always - 9958 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 152 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 1 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 9 Power_On_Hours 0x0032 099 099 000 Old_age Always - 1071 10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 34 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 20 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 379 194 Temperature_Celsius 0x0022 119 110 000 Old_age Always - 33 196 Reallocated_Event_Count 0x0032 199 199 000 Old_age Always - 1 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 440 198 Offline_Uncorrectable 0x0030 200 200 000 Old_age Offline - 12 199 UDMA_CRC_Error_Count 0x0032 200 181 000 Old_age Always - 2239 200 Multi_Zone_Error_Rate 0x0008 198 198 000 Old_age Offline - 806 Link to comment
dgaschk Posted May 21, 2013 Share Posted May 21, 2013 None of the drive can have pending sectors in order for parity protection to work. You can try rebuilding parity and see what happens to the pending sectors value. If it remains greater than zero then RMA. Link to comment
nightanole Posted May 21, 2013 Author Share Posted May 21, 2013 Ill do another parity check (with correct errors check) tonight and see what happens. yesterday when i ran it i had no sync errors. An non of the other drives have relocated sectors nor pending sectors. I assume that is what you mean by rebuilding parity. Link to comment
garycase Posted May 21, 2013 Share Posted May 21, 2013 Rebuilding parity means to unassign parity (so the system doesn't have a parity disk); then re-assign the disk as parity so it completely rebuilds the parity disk (forcing writes to all sectors). I would change ... or at least re-seat (unplug/replug) the SATA cable to the parity drive before you reassign it ... you COULD have poorly seated cables that are causing these problems. Rebuilding parity will take a LONG time. Then -- after it completes -- do a parity check and see if there are any sync errors. If so, RMA the drive ... it not, check the SMART report and see if it looks okay (passes SMART and has no pending sectors to reallocate). Personally, I'd simply RMA the drive now ... but it IS possible your issue was cable-related, so it won't hurt to give it a thorough test as I just outlined. Link to comment
nightanole Posted May 21, 2013 Author Share Posted May 21, 2013 Last question. Define long time. Like preclear long time, or some new horrible nightmare? Link to comment
garycase Posted May 21, 2013 Share Posted May 21, 2013 Last question. Define long time. Like preclear long time, or some new horrible nightmare? Depends on the size of your drives ... but basically a bit longer than a parity check, so typically several hours (e.g. my system uses 3TB drives, and a parity check takes ~ 8hrs ... the initial calculation took a bit longer than that -- I don't recall just how much longer; but probably ~ 10 hrs). Link to comment
Joe L. Posted May 21, 2013 Share Posted May 21, 2013 Last question. Define long time. Like preclear long time, or some new horrible nightmare? Depends on the size of your drives ... but basically a bit longer than a parity check, so typically several hours (e.g. my system uses 3TB drives, and a parity check takes ~ 8hrs ... the initial calculation took a bit longer than that -- I don't recall just how much longer; but probably ~ 10 hrs). Another issue... 199 UDMA_CRC_Error_Count 0x0032 200 181 000 Old_age Always - 2239 UDMA CRC errors are usually caused by noise pickup on the SATA cable to the disk. That is usually caused by either a poorly shielded SATA cable OR one that has been neatly bundled parallel and close to other SATA cables using tie-wraps, etc. This is even worse if it has been bundled with power cables. To fix, cut the tie-wraps on the SATA cables. Then, put some distance between the cables. (or replace them with shielded versions) Do not let them all run tightly parallel to each other. Being OCD neat is the WRONG way to cable a multi-disk-server. The sectrs pending re-allcation is a separate issue. Your disk may need replacement regardless. 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 440 As mentioned, un-assign the parity disk, START THE SERVER WITH IT UN_ASSIGNED, the stop the server and re-assign it. It will be completely re-written. After it is re-written, perform a parity check to see if it csn be read back properly. then get another SMART report. There should be NO sectors pending re-allocation. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.