bobekdj Posted March 3, 2016 Share Posted March 3, 2016 I pre-cleared an older drive I had, I am struggling to determine what info is important to consider, and what flags mean the drive should just be thrown away. Below are the outputs from preclear script, as well as the unRAID GUI SMART testing (downloaded SMART Report). Any resources or explanation is greatly appreciated (g.com and yt.com were not help with smart info interpretation). Preclear: ================================================================== 1.15 = unRAID server Pre-Clear disk /dev/sdd = cycle 1 of 1, partition start on sector 64 = Disk Pre-Clear-Read completed DONE = Step 1 of 10 - Copying zeros to first 2048k bytes DONE = Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE = Step 3 of 10 - Disk is now cleared from MBR onward. DONE = Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4 DONE = Step 5 of 10 - Clearing MBR code area DONE = Step 6 of 10 - Setting MBR signature bytes DONE = Step 7 of 10 - Setting partition 1 to precleared state DONE = Step 8 of 10 - Notifying kernel we changed the partitioning DONE = Step 9 of 10 - Creating the /dev/disk/by* entries DONE = Step 10 of 10 - Verifying if the MBR is cleared. DONE = Disk Post-Clear-Read completed DONE Disk Temperature: 35C, Elapsed Time: 23:30:10 ========================================================================1.15 == ST2000DL003-9VT166 5YD22M1T == Disk /dev/sdd has been successfully precleared == with a starting sector of 64 ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdd /tmp/smart_finish_sdd ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 116 120 6 ok 105815952 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 Reported_Uncorrect = 1 1 0 near_thresh 145 Airflow_Temperature_Cel = 65 68 45 near_thresh 35 Temperature_Celsius = 35 32 0 ok 35 No SMART attributes are FAILING_NOW 0 sectors were pending re-allocation before the start of the preclear. 0 sectors were pending re-allocation after pre-read in cycle 1 of 1. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 1. 0 sectors are pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 0 sectors had been re-allocated before the start of the preclear. 0 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change. root@unRAID:/usr/local/emhttp# unRAID GUI: smartctl 6.2 2013-07-26 r3841 [x86_64-linux-4.1.17-unRAID] (local build) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Seagate Barracuda Green (AF) Device Model: ST2000DL003-9VT166 Serial Number: 5YD22M1T LU WWN Device Id: 5 000c50 032d1cc1f Firmware Version: CC32 User Capacity: 2,000,398,934,016 bytes [2.00 TB] Sector Size: 512 bytes logical/physical Rotation Rate: 5900 rpm Device is: In smartctl database [for details use: -P show] ATA Version is: ATA8-ACS T13/1699-D revision 4 SATA Version is: SATA 3.0, 6.0 Gb/s (current: 3.0 Gb/s) Local Time is: Thu Mar 3 08:49:53 2016 PST 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: (0x82) Offline data collection activity was completed without error. Auto Offline Data Collection: Enabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: ( 612) 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: ( 1) minutes. Extended self-test routine recommended polling time: ( 339) minutes. Conveyance self-test routine recommended polling time: ( 2) minutes. SCT capabilities: (0x30b7) SCT Status supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 116 097 006 Pre-fail Always - 105821192 3 Spin_Up_Time 0x0003 095 084 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 099 099 020 Old_age Always - 1093 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 070 060 030 Pre-fail Always - 11455524 9 Power_On_Hours 0x0032 084 084 000 Old_age Always - 14277 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 207 183 Runtime_Bad_Block 0x0032 099 099 000 Old_age Always - 1 184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 001 001 000 Old_age Always - 145 188 Command_Timeout 0x0032 100 098 000 Old_age Always - 15 189 High_Fly_Writes 0x003a 097 097 000 Old_age Always - 3 190 Airflow_Temperature_Cel 0x0022 066 057 045 Old_age Always - 34 (Min/Max 31/38) 191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 402 193 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 1114 194 Temperature_Celsius 0x0022 034 043 000 Old_age Always - 34 (0 16 0 0 0) 195 Hardware_ECC_Recovered 0x001a 020 003 000 Old_age Always - 105821192 197 Current_Pending_Sector 0x0012 100 097 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 100 097 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 10 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 195670120077502 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 2907446593 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 2917276995 SMART Error Log Version: 1 ATA Error Count: 94 (device log contains only the most recent five errors) CR = Command Register [HEX] FR = Features Register [HEX] SC = Sector Count Register [HEX] SN = Sector Number Register [HEX] CL = Cylinder Low Register [HEX] CH = Cylinder High Register [HEX] DH = Device/Head Register [HEX] DC = Device Command Register [HEX] ER = Error register [HEX] ST = Status register [HEX] Powered_Up_Time is measured from power on, and printed as DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes, SS=sec, and sss=millisec. It "wraps" after 49.710 days. Error 94 occurred at disk power-on lifetime: 14176 hours (590 days + 16 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 98 4b f2 02 Error: UNC at LBA = 0x02f24b98 = 49433496 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 00 08 98 4b f2 42 00 00:18:16.986 READ FPDMA QUEUED 27 00 00 00 00 00 e0 00 00:18:16.985 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3] ec 00 00 00 00 00 a0 00 00:18:16.985 IDENTIFY DEVICE ef 03 46 00 00 00 a0 00 00:18:16.984 SET FEATURES [set transfer mode] 27 00 00 00 00 00 e0 00 00:18:16.984 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3] Error 93 occurred at disk power-on lifetime: 14176 hours (590 days + 16 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 98 4b f2 02 Error: UNC at LBA = 0x02f24b98 = 49433496 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 00 08 00 30 f2 42 00 00:18:13.544 READ FPDMA QUEUED 60 00 08 f8 2f f2 42 00 00:18:13.521 READ FPDMA QUEUED 27 00 00 00 00 00 e0 00 00:18:13.521 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3] ec 00 00 00 00 00 a0 00 00:18:13.520 IDENTIFY DEVICE ef 03 46 00 00 00 a0 00 00:18:13.520 SET FEATURES [set transfer mode] Error 92 occurred at disk power-on lifetime: 14176 hours (590 days + 16 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 d8 2c f2 02 Error: UNC at LBA = 0x02f22cd8 = 49425624 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 00 08 d8 2c f2 42 00 00:18:10.147 READ FPDMA QUEUED 27 00 00 00 00 00 e0 00 00:18:10.147 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3] ec 00 00 00 00 00 a0 00 00:18:10.146 IDENTIFY DEVICE ef 03 46 00 00 00 a0 00 00:18:10.146 SET FEATURES [set transfer mode] 27 00 00 00 00 00 e0 00 00:18:10.146 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3] Error 91 occurred at disk power-on lifetime: 14176 hours (590 days + 16 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 d8 2c f2 02 Error: UNC at LBA = 0x02f22cd8 = 49425624 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 00 08 78 11 f2 42 00 00:18:06.708 READ FPDMA QUEUED 60 00 08 70 11 f2 42 00 00:18:06.683 READ FPDMA QUEUED 27 00 00 00 00 00 e0 00 00:18:06.682 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3] ec 00 00 00 00 00 a0 00 00:18:06.682 IDENTIFY DEVICE ef 03 46 00 00 00 a0 00 00:18:06.681 SET FEATURES [set transfer mode] Error 90 occurred at disk power-on lifetime: 14176 hours (590 days + 16 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 90 0c f2 02 Error: UNC at LBA = 0x02f20c90 = 49417360 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 00 08 90 0c f2 42 00 00:18:03.309 READ FPDMA QUEUED 27 00 00 00 00 00 e0 00 00:18:03.308 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3] ec 00 00 00 00 00 a0 00 00:18:03.308 IDENTIFY DEVICE ef 03 46 00 00 00 a0 00 00:18:03.308 SET FEATURES [set transfer mode] 27 00 00 00 00 00 e0 00 00:18:03.307 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3] SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Completed without error 00% 14266 - # 2 Short offline Completed without error 00% 14261 - # 3 Short offline Completed without error 00% 12884 - # 4 Extended offline Completed without error 00% 12126 - # 5 Short offline Completed without error 00% 11333 - # 6 Short offline Completed without error 00% 10789 - # 7 Short offline Completed without error 00% 10695 - 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. Thanks again for taking the time to look. Link to comment
Chris Pollard Posted March 3, 2016 Share Posted March 3, 2016 Reported uncorrect usually isn't a good thing. Seem to remember this one one of the stats backblaze use to replace drives. EDIT : See here https://www.backblaze.com/blog/hard-drive-smart-stats/ Link to comment
RobJ Posted March 3, 2016 Share Posted March 3, 2016 The report does indicate the drive looks OK at the moment, but some of those uncorrectables were recent, so I would recommend 1 or 2 more Preclear passes. If nothing significant changes after that, then the drive is usable, but I would continue to monitor it. Hardware_ECC_Recovered is also lower than normal, may indicate a marginal mechanical issue. Link to comment
bobekdj Posted March 3, 2016 Author Share Posted March 3, 2016 THANK YOU THIS IS A GOOD SUMMARY!! Reported uncorrect usually isn't a good thing. Seem to remember this one one of the stats backblaze use to replace drives. EDIT : See here https://www.backblaze.com/blog/hard-drive-smart-stats/ Link to comment
bobekdj Posted March 3, 2016 Author Share Posted March 3, 2016 Ok, I may try to just let it run a few days and see what happens. I am not as familiar how to detect errors, but know some of the old drives were questionable in a previous unRAID server. Was just trying to keep as many old ones as i could. Thanks for the info! The report does indicate the drive looks OK at the moment, but some of those uncorrectables were recent, so I would recommend 1 or 2 more Preclear passes. If nothing significant changes after that, then the drive is usable, but I would continue to monitor it. Hardware_ECC_Recovered is also lower than normal, may indicate a marginal mechanical issue. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.