August 31, 201312 yr Reading over some of the topics I noticed that everyone suggested a Parity check before moving to a new build. I checked the completed progress this morning and noticed that the parity drive showed 48 errors (previous check last month was 0). Should I run another check from the web menu? Is it better (for logging purposes) to run it from the server? Does this low number even matter? Thank you for any help. Disk status Model Temp Size Free Reads Writes Errors parity WDC_WD15EARS-00Z_WD-WMAVU 40°C 1,465,138,552 3,970,590 22,500 48 disk1 WDC_WD15EARS-00Z_WD-WMAVU 37°C 1,465,138,552 493,306,768 4,205,874 22,887 0 disk2 WDC_WD15EARS-00Z_WD-WMAVU 39°C 1,465,138,552 725,636,692 3,946,287 31 0
August 31, 201312 yr Those are read errors. Post a SMART report and attach a syslog. There should never be any errors. Those errors represent from 24-96M of data on each data disk that is not protected by parity. Everyones tolerance is different but I prefer that all of my data be protected.
August 31, 201312 yr Author I ran the short test on the drive, should that suffice? === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x85) Offline data collection activity was aborted by an interrupting command from host. Auto Offline Data Collection: Enabled. Self-test execution status: ( 249) Self-test routine in progress... 90% of test remaining. Total time to complete Offline data collection: (33600) seconds. Offline data collection capabilities: (0x7b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. Conveyance Self-test supported. Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 2) minutes. Extended self-test routine recommended polling time: ( 255) minutes. Conveyance self-test routine recommended polling time: ( 5) minutes. SCT capabilities: (0x3031) SCT Status supported. SCT Feature Control supported. SCT Data Table supported. 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 200 200 051 Pre-fail Always - 154 3 Spin_Up_Time 0x0027 181 180 021 Pre-fail Always - 5933 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 272 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 9 Power_On_Hours 0x0032 071 071 000 Old_age Always - 21257 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 - 51 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 16 193 Load_Cycle_Count 0x0032 199 199 000 Old_age Always - 3226 194 Temperature_Celsius 0x0022 118 101 000 Old_age Always - 32 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 2 198 Offline_Uncorrectable 0x0030 200 200 000 Old_age Offline - 1 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age Offline - 3 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed without error 00% 14571 - # 2 Short offline Completed: read failure 10% 14536 481279079 SMART Selective self-test log data structure revision number 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Not_testing 2 0 0 Not_testing 3 0 0 Not_testing 4 0 0 Not_testing 5 0 0 Not_testing Selective self-test flags (0x0): After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay.
August 31, 201312 yr Those aren't sync errors -- they're actual read errors when accessing the parity disk. The SMART report also shows there are some pending reallocations on the disk as well. First, do a correcting parity check. The sync error count is what you want to look at -- and it's likely it won't be zero, since there are some sectors with issues on the parity drive ... but the correction will cause those sectors to be rewritten (and thus reallocated). Then do a second correcting check and confirm the sync error count is now zero -- and see if you still have any errors shown for the disk. If you still have disk errors, it's time to replace the disk.
August 31, 201312 yr Author Thanks for the help, I will be doing this now. Just to double check that I understand correctly, I am looking for the Current_Pending_Sector count to read 0, or just the Reallocated_Sector_Ct to be at THRESH 000 ?
August 31, 201312 yr You want the Current Pending Sector count to be 0. This requires that the pending sectors be rewritten. There's no simply way to do this non-destructively (unless you happen to have a copy of Spinrite) ... but if they're generating read errors, then what will happen is there will be a sync error during the parity check, and the correction will force a rewrite of that sector, which will cause the SMART logic on the drive to reallocate the sector and use a good spare. (that's what you want to happen) So if you do two correcting parity checks in a row, the result should be zero sync errors on the 2nd check, and most likely you'll no longer have pending reallocations. As I noted above, if that's not the case, I'd replace the drive -- although there IS one more thing you could do before that ... it requires that you "run at risk", but with a failing parity drive you're probably already at risk ... basically you could simply do a new config; assign your two data drives; then assign the parity drive => that would force a new parity synchronization (NOT a check) ... which will write every sector on the parity drive -- definitely forcing pending reallocations to be reallocated. If you do that, run a parity check after it's done to confirm no errors and zero sync errors. If that works okay, you're good.
Archived
This topic is now archived and is closed to further replies.