flips Posted March 24, 2016 Share Posted March 24, 2016 My parity was flagged as bad when I upgraded to v6, so even though the error happened a while ago, I still replaced it. googling 187 smart error seemed to be pretty serious... I ran 5 preclear cycles all passed, still zero relocated and pending sectors. Any thoughts on this? Anyone see a reason not to put it back in to the array? As always I really appreciate the help. Start Disk: /dev/sdb smartctl 6.2 2013-07-26 r3841 [i686-linux-3.9.11p-unRAID] (local build) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Seagate Desktop HDD.15 Device Model: ST4000DM000-1CD168 Serial Number: Z3002LCJ LU WWN Device Id: 5 000c50 04f4ce53b Firmware Version: CC43 User Capacity: 4,000,787,030,016 bytes [4.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes 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: Fri Mar 18 23:13:08 2016 PDT 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: (0x00) Offline data collection activity was never started. Auto Offline Data Collection: Disabled. 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: ( 602) seconds. Offline data collection capabilities: (0x73) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. No 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: ( 532) minutes. Conveyance self-test routine recommended polling time: ( 2) minutes. SCT capabilities: (0x1085) SCT Status 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 118 099 006 Pre-fail Always - 201127656 3 Spin_Up_Time 0x0003 093 091 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 705 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 075 060 030 Pre-fail Always - 39364723 9 Power_On_Hours 0x0032 073 073 000 Old_age Always - 24065 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 45 183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0 184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 099 099 000 Old_age Always - 1 188 Command_Timeout 0x0032 100 100 000 Old_age Always - 0 0 0 189 High_Fly_Writes 0x003a 097 097 000 Old_age Always - 3 190 Airflow_Temperature_Cel 0x0022 080 058 045 Old_age Always - 20 (Min/Max 19/20) 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 - 29 193 Load_Cycle_Count 0x0032 001 001 000 Old_age Always - 369562 194 Temperature_Celsius 0x0022 020 042 000 Old_age Always - 20 (0 15 0 0 0) 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 16746h+22m+49.638s 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 50005632544 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 183453330303 SMART Error Log Version: 1 ATA Error Count: 2 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 2 occurred at disk power-on lifetime: 17358 hours (723 days + 6 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 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 00 ff ff ff ef 00 40d+13:56:26.430 READ DMA EXT 25 00 00 ff ff ff ef 00 40d+13:56:26.386 READ DMA EXT 25 00 00 ff ff ff ef 00 40d+13:56:26.384 READ DMA EXT 35 00 08 ff ff ff ef 00 40d+13:56:26.382 WRITE DMA EXT 25 00 00 ff ff ff ef 00 40d+13:56:26.381 READ DMA EXT Error 1 occurred at disk power-on lifetime: 17358 hours (723 days + 6 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 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 00 ff ff ff ef 00 40d+13:56:26.430 READ DMA EXT 25 00 00 ff ff ff ef 00 40d+13:56:26.386 READ DMA EXT 25 00 00 ff ff ff ef 00 40d+13:56:26.384 READ DMA EXT 35 00 08 ff ff ff ef 00 40d+13:56:26.382 WRITE DMA EXT 25 00 00 ff ff ff ef 00 40d+13:56:26.381 READ DMA EXT SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Aborted by host 90% 23662 - # 2 Extended offline Completed without error 00% 23660 - # 3 Short offline Completed without error 00% 23652 - # 4 Short offline Completed without error 00% 20394 - 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. Report: ========================================================================1.15b == invoked as: ./preclear_bjp.sh -c 5 -M4 -f /dev/sdb == ST4000DM000-1CD168 Z3002LCJ == Disk /dev/sdb has been successfully precleared == with a starting sector of 1 == Ran 5 cycles == == Using :Read block size = 8388608 Bytes == Last Cycle's Pre Read Time : 9:09:17 (121 MB/s) == Last Cycle's Zeroing time : 8:22:43 (132 MB/s) == Last Cycle's Post Read Time : 11:28:52 (96 MB/s) == Last Cycle's Total Time : 19:52:37 == == Total Elapsed Time 108:29:18 == == Disk Start Temperature: 20C == == Current Disk Temperature: 21C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdb /tmp/smart_finish_sdb ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 111 118 6 ok 30379400 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 Airflow_Temperature_Cel = 79 80 45 ok 21 Load_Cycle_Count = 1 1 0 near_thresh 369562 Temperature_Celsius = 21 20 0 near_thresh 21 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 5. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 5. 0 sectors were pending re-allocation after post-read in cycle 1 of 5. 0 sectors were pending re-allocation after zero of disk in cycle 2 of 5. 0 sectors were pending re-allocation after post-read in cycle 2 of 5. 0 sectors were pending re-allocation after zero of disk in cycle 3 of 5. 0 sectors were pending re-allocation after post-read in cycle 3 of 5. 0 sectors were pending re-allocation after zero of disk in cycle 4 of 5. 0 sectors were pending re-allocation after post-read in cycle 4 of 5. 0 sectors were pending re-allocation after zero of disk in cycle 5 of 5. 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. ============================================================================ Finish: Disk: /dev/sdb smartctl 6.2 2013-07-26 r3841 [i686-linux-3.9.11p-unRAID] (local build) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Seagate Desktop HDD.15 Device Model: ST4000DM000-1CD168 Serial Number: Z3002LCJ LU WWN Device Id: 5 000c50 04f4ce53b Firmware Version: CC43 User Capacity: 4,000,787,030,016 bytes [4.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes 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: Wed Mar 23 11:42:25 2016 PDT 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: (0x00) Offline data collection activity was never started. Auto Offline Data Collection: Disabled. 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: ( 602) seconds. Offline data collection capabilities: (0x73) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. No 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: ( 532) minutes. Conveyance self-test routine recommended polling time: ( 2) minutes. SCT capabilities: (0x1085) SCT Status 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 111 099 006 Pre-fail Always - 30379400 3 Spin_Up_Time 0x0003 093 091 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 705 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 075 060 030 Pre-fail Always - 40172083 9 Power_On_Hours 0x0032 073 073 000 Old_age Always - 24174 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 45 183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0 184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 099 099 000 Old_age Always - 1 188 Command_Timeout 0x0032 100 100 000 Old_age Always - 0 0 0 189 High_Fly_Writes 0x003a 097 097 000 Old_age Always - 3 190 Airflow_Temperature_Cel 0x0022 079 058 045 Old_age Always - 21 (Min/Max 19/23) 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 - 29 193 Load_Cycle_Count 0x0032 001 001 000 Old_age Always - 369562 194 Temperature_Celsius 0x0022 021 042 000 Old_age Always - 21 (0 15 0 0 0) 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 16854h+52m+12.672s 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 89075818624 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 231531069846 SMART Error Log Version: 1 ATA Error Count: 2 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 2 occurred at disk power-on lifetime: 17358 hours (723 days + 6 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 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 00 ff ff ff ef 00 40d+13:56:26.430 READ DMA EXT 25 00 00 ff ff ff ef 00 40d+13:56:26.386 READ DMA EXT 25 00 00 ff ff ff ef 00 40d+13:56:26.384 READ DMA EXT 35 00 08 ff ff ff ef 00 40d+13:56:26.382 WRITE DMA EXT 25 00 00 ff ff ff ef 00 40d+13:56:26.381 READ DMA EXT Error 1 occurred at disk power-on lifetime: 17358 hours (723 days + 6 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 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 00 ff ff ff ef 00 40d+13:56:26.430 READ DMA EXT 25 00 00 ff ff ff ef 00 40d+13:56:26.386 READ DMA EXT 25 00 00 ff ff ff ef 00 40d+13:56:26.384 READ DMA EXT 35 00 08 ff ff ff ef 00 40d+13:56:26.382 WRITE DMA EXT 25 00 00 ff ff ff ef 00 40d+13:56:26.381 READ DMA EXT SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Aborted by host 90% 23662 - # 2 Extended offline Completed without error 00% 23660 - # 3 Short offline Completed without error 00% 23652 - # 4 Short offline Completed without error 00% 20394 - 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. Quote Link to comment
John_M Posted March 24, 2016 Share Posted March 24, 2016 I would replace it, no question. This might help you decide: https://www.backblaze.com/blog/hard-drive-smart-stats/ Quote Link to comment
RobJ Posted March 24, 2016 Share Posted March 24, 2016 I'm sorry you went to all that trouble, you should have ignored it. The new SMART monitoring warns on first detection of non-zero values on certain attributes, and I would have preferred it to not warn at the first time, only on changes that occur AFTER that. It has needlessly worried users with old values like yours. If you look at the ATA error section, you'll see that that UNC (UNCorrectable) occurred at 17358 hours, almost 7000 operational hours previously, so long past, and certainly already dealt with by the drive. Your drive is fine. Quote Link to comment
flips Posted March 26, 2016 Author Share Posted March 26, 2016 Thanks guys. That blackblaze report is one of the pages I read during my research which made me concerned.. @RobJ Thinking about your comment, if I put it back in the array with the smart issue then my array will be reporting an issue? So my daily email instead of the array is good, it will say the array is bad then I will have to go in and look to make sure it is only that issue and not a new issue. Is that correct? flips Quote Link to comment
spylex Posted March 27, 2016 Share Posted March 27, 2016 I have a drive that has this reported at 50 hours, but has been running for 18000 hours... how strange, so i can ignore? Quote Link to comment
RobJ Posted March 27, 2016 Share Posted March 27, 2016 On the Dashboard where you see the orange triangle for SMART status, click on it then click on the line to acknowledge it (can't remember the exact wording, and I can't check it now). That will keep it from popping up again, unless it changes again. Quote Link to comment
spylex Posted March 27, 2016 Share Posted March 27, 2016 This is useful, thank you! Quote Link to comment
RobJ Posted March 27, 2016 Share Posted March 27, 2016 I have a drive that has this reported at 50 hours, but has been running for 18000 hours... how strange, so i can ignore? That's a big reason why we recommend Preclearing new drives, to weed out the 'infant mortality' ones, and shake out any marginal stuff. If the sector isn't reliable, we want it out of there as soon as possible. It does mean the SMART for the drive may not *look* perfect. I personally believe ALL drives have issues, marginal sectors, but their initial factory prep weeds out most and selects only the good ones, then presents what appears to be a perfect SMART report, based on their sector selection. Your first usage constitutes additional testing, and may show up additional untrustworthy sectors, but you won't have the luxury they had in starting all numbers at zero! Quote Link to comment
spylex Posted March 28, 2016 Share Posted March 28, 2016 @RobJ, agreed. I have pre-cleared all the Seagate drives twice before adding, yet that still appeared on hour 50. Admittedly, i've had 2 more develop the same issue and one of them has died (but that might be because i dropped it from 2 meters while it was offline!). Quote Link to comment
RobJ Posted March 28, 2016 Share Posted March 28, 2016 @RobJ, agreed. I have pre-cleared all the Seagate drives twice before adding, yet that still appeared on hour 50. Admittedly, i've had 2 more develop the same issue and one of them has died (but that might be because i dropped it from 2 meters while it was offline!). Yeah, poor gravity management can cause problems! Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.