April 25, 201214 yr Note: using unRAID v 4.7 I had a disk get disabled/red-balled after a parity check and replaced it with another I had available (after the new one was pre-cleared in another system). My main system is back up and running with the new drive, after a re-build by unRAID, so my data is safe. Before I replaced the disabled drive, I ran a short smart test: smartctl 5.39.1 2010-01-28 r3054 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Device Model: WDC WD20EARS-00MVWB0 Serial Number: WD-WMAZA274XXXX Firmware Version: 51.0AB51 User Capacity: 2,000,398,934,016 bytes Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 8 ATA Standard is: Exact ATA specification draft version not indicated Local Time is: Fri Apr 20 15:28:03 2012 EDT SMART support is: Available - device has SMART capability. SMART support is: Enabled === 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: ( 121) The previous self-test completed having the read element of the test failed. Total time to complete Offline data collection: (36660) 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: (0x3035) 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 199 199 051 Pre-fail Always - 1554 3 Spin_Up_Time 0x0027 253 169 021 Pre-fail Always - 1908 4 Start_Stop_Count 0x0032 099 099 000 Old_age Always - 1717 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 092 092 000 Old_age Always - 6082 10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 100 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 332 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 21 193 Load_Cycle_Count 0x0032 193 193 000 Old_age Always - 23470 194 Temperature_Celsius 0x0022 123 115 000 Old_age Always - 27 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 001 000 Old_age Always - 70 198 Offline_Uncorrectable 0x0030 200 200 000 Old_age Offline - 0 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 - 58 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: read failure 90% 6082 3704627856 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. I now have the drive in my test system and ran a long smart test on it: smartctl 5.39.1 2010-01-28 r3054 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Device Model: WDC WD20EARS-00MVWB0 Serial Number: WD-WMAZA274XXXX Firmware Version: 51.0AB51 User Capacity: 2,000,398,934,016 bytes Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 8 ATA Standard is: Exact ATA specification draft version not indicated Local Time is: Tue Apr 24 17:39:38 2012 EDT SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x84) Offline data collection activity was suspended by an interrupting command from host. Auto Offline Data Collection: Enabled. Self-test execution status: ( 121) The previous self-test completed having the read element of the test failed. Total time to complete Offline data collection: (36660) 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: (0x3035) 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 199 199 051 Pre-fail Always - 1554 3 Spin_Up_Time 0x0027 253 169 021 Pre-fail Always - 1925 4 Start_Stop_Count 0x0032 099 099 000 Old_age Always - 1720 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 092 092 000 Old_age Always - 6087 10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 100 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 335 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 21 193 Load_Cycle_Count 0x0032 193 193 000 Old_age Always - 23473 194 Temperature_Celsius 0x0022 127 115 000 Old_age Always - 23 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 198 001 000 Old_age Always - 743 198 Offline_Uncorrectable 0x0030 200 200 000 Old_age Offline - 0 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 - 58 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 Extended offline Completed: read failure 90% 6082 3704627856 # 2 Short offline Completed: read failure 90% 6082 3704627856 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. I've done a lot of reading, but I'm still confused about how to interpret these reports. I suspect these lines are most concerning: This one didn't change between reports: 1 Raw_Read_Error_Rate 0x002f 199 199 051 Pre-fail Always - 1554 and this one which did: short test: 197 Current_Pending_Sector 0x0032 200 001 000 Old_age Always - 70 long test: 197 Current_Pending_Sector 0x0032 198 001 000 Old_age Always - 743 and then there is this one, which I'm not sure about: 200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age Offline - 58 I had been tracking the MZER raw number which was going up over time, but now I've read that the raw number doesn't matter and to look at the VALUE and WORST which haven't changed. I've read that the current pending sectors will get re-mapped (if possible) on a subsequent write, but does the VALUE and WORST of 198 001 on Current_Pending_Sector indicate this disk is toast? My plan was to run a pre-clear cycle on the disk and then check it with WD diagnostics to determine if it should be RMA'd? Is that the best course to take? TIA
April 25, 201214 yr Note: using unRAID v 4.7 I had a disk get disabled/red-balled after a parity check and replaced it with another I had available (after the new one was pre-cleared in another system). My main system is back up and running with the new drive, after a re-build by unRAID, so my data is safe. That is good. I've done a lot of reading, but I'm still confused about how to interpret these reports. I suspect these lines are most concerning: This one didn't change between reports: 1 Raw_Read_Error_Rate 0x002f 199 199 051 Pre-fail Always - 1554 Most raw values are meaningless to most except the manufacturer. and this one which did: short test: 197 Current_Pending_Sector 0x0032 200 001 000 Old_age Always - 70 long test: 197 Current_Pending_Sector 0x0032 198 001 000 Old_age Always - 743 That RAW value does have meaning. There now are over 700 un-readable sectors. This is a clear sign the disk is rapidly failing. and then there is this one, which I'm not sure about: 200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age Offline - 58 I had been tracking the MZER raw number which was going up over time, but now I've read that the raw number doesn't matter and to look at the VALUE and WORST which haven't changed. That one is not as significant. As you can see the normalized value has not changed, so the manufacturer does not consider it significant. I've read that the current pending sectors will get re-mapped (if possible) on a subsequent write, but does the VALUE and WORST of 198 001 on Current_Pending_Sector indicate this disk is toast? correct... There are over 700 sectors that are waiting to be re-allocated. It is rapidly failing. My plan was to run a pre-clear cycle on the disk and then check it with WD diagnostics to determine if it should be RMA'd? Is that the best course to take? TIA pre-clear it, check with WD Diagnostics, then RMA it, then check the replacement with WD Diagnostics. (I would not bother with any "determination" as it needs replacement... there is no doubt.) Joe L.
April 25, 201214 yr Author pre-clear it, check with WD Diagnostics, then RMA it, then check the replacement with WD Diagnostics. (I would not bother with any "determination" as it needs replacement... there is no doubt.) Joe L. OK, thanks, I've started the pre-clear cycle.
Archived
This topic is now archived and is closed to further replies.