September 5, 201015 yr This Drive was pulled from my old RAID5, of the 4 drives in the array one had 120 reaccolated sectors (precleared one pass with no more) and this one has 6 ATA errors: What's the thought on these errors? Is this a drive issue or an interface issue in the old array? SMART status Info for /dev/sdf smartctl version 5.38 [i486-slackware-linux-gnu] Copyright © 2002-8 Bruce Allen Home page is http://smartmontools.sourceforge.net/ === START OF INFORMATION SECTION === Device Model: ST31500341AS Serial Number: 9VS1L9N7 Firmware Version: CC1H User Capacity: 1,500,301,910,016 bytes Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 8 ATA Standard is: ATA-8-ACS revision 4 Local Time is: Sun Sep 5 08:25:48 2010 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: (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: ( 617) 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: ( 255) minutes. Conveyance self-test routine recommended polling time: ( 2) minutes. SCT capabilities: (0x103f) 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 118 099 006 Pre-fail Always - 184760553 3 Spin_Up_Time 0x0003 100 092 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 83 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 4 7 Seek_Error_Rate 0x000f 084 060 030 Pre-fail Always - 283004637 9 Power_On_Hours 0x0032 089 089 000 Old_age Always - 10119 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 72 184 Unknown_Attribute 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 094 094 000 Old_age Always - 6 188 Unknown_Attribute 0x0032 100 099 000 Old_age Always - 1 189 High_Fly_Writes 0x003a 001 001 000 Old_age Always - 144 190 Airflow_Temperature_Cel 0x0022 056 048 045 Old_age Always - 44 (Lifetime Min/Max 23/44) 194 Temperature_Celsius 0x0022 044 052 000 Old_age Always - 44 (0 23 0 0) 195 Hardware_ECC_Recovered 0x001a 046 031 000 Old_age Always - 184760553 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 - 251706558392198 241 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 1866068823 242 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 190619241 SMART Error Log Version: 1 ATA Error Count: 6 (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 6 occurred at disk power-on lifetime: 10050 hours (418 days + 18 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 9e ca 4b 04 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 01 9e ca 4b 44 00 6d+06:05:33.165 READ FPDMA QUEUED 61 00 08 ff ff ff 4f 00 6d+06:05:33.148 WRITE FPDMA QUEUED 60 00 01 9d ca 4b 44 00 6d+06:05:33.125 READ FPDMA QUEUED 60 00 08 ff ff ff 4f 00 6d+06:05:33.125 READ FPDMA QUEUED 60 00 01 9c ca 4b 44 00 6d+06:05:33.124 READ FPDMA QUEUED Error 5 occurred at disk power-on lifetime: 10050 hours (418 days + 18 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 9e ca 4b 04 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 18 88 ca 4b 44 00 6d+06:05:29.963 READ FPDMA QUEUED 61 00 08 f8 57 1f 40 00 6d+06:05:29.963 WRITE FPDMA QUEUED 60 00 08 f8 57 1f 40 00 6d+06:05:29.963 READ FPDMA QUEUED 61 00 08 08 58 1f 40 00 6d+06:05:29.962 WRITE FPDMA QUEUED 60 00 08 08 58 1f 40 00 6d+06:05:29.962 READ FPDMA QUEUED Error 4 occurred at disk power-on lifetime: 6104 hours (254 days + 8 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 9e ca 4b 04 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 01 9e ca 4b 44 00 15d+06:02:08.530 READ FPDMA QUEUED 60 00 01 9d ca 4b 44 00 15d+06:02:08.512 READ FPDMA QUEUED 60 00 01 9c ca 4b 44 00 15d+06:02:08.512 READ FPDMA QUEUED 60 00 01 9b ca 4b 44 00 15d+06:02:08.511 READ FPDMA QUEUED 60 00 01 9a ca 4b 44 00 15d+06:02:08.511 READ FPDMA QUEUED Error 3 occurred at disk power-on lifetime: 6104 hours (254 days + 8 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 9e ca 4b 04 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 70 88 ca 4b 44 00 15d+06:02:05.533 READ FPDMA QUEUED 61 00 10 ff ff ff 4f 00 15d+06:02:05.508 WRITE FPDMA QUEUED 61 00 08 ff ff ff 4f 00 15d+06:02:05.500 WRITE FPDMA QUEUED 60 00 10 ff ff ff 4f 00 15d+06:02:05.478 READ FPDMA QUEUED 60 00 08 ff ff ff 4f 00 15d+06:02:05.477 READ FPDMA QUEUED Error 2 occurred at disk power-on lifetime: 3037 hours (126 days + 13 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 9e ca 4b 04 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 61 00 80 00 fb 50 40 00 22:07:29.911 WRITE FPDMA QUEUED 61 00 48 00 fa 50 40 00 22:07:29.906 WRITE FPDMA QUEUED 60 00 01 9e ca 4b 44 00 22:07:29.892 READ FPDMA QUEUED 60 00 01 9d ca 4b 44 00 22:07:29.891 READ FPDMA QUEUED 60 00 08 c8 cc 31 48 00 22:07:29.881 READ FPDMA QUEUED SMART Self-test log structure revision number 1 No self-tests have been logged. [To run self-tests, use: smartctl -t] 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
September 5, 201015 yr This Drive was pulled from my old RAID5, of the 4 drives in the array one had 120 reaccolated sectors (precleared one pass with no more) and this one has 6 ATA errors: What's the thought on these errors? Is this a drive issue or an interface issue in the old array? No way to tell really. You have 4 re-allocated sectors on that drive. It is one of the few smart attributes that are usable by us humans. The other errors will be reported to the OS, and it will re-try to get to the data under Linux. Those will show as errors and resets in the syslog. If you did not see them during the preclear process, odds are you are ok with that drive. Keep an eye on the re-allocated sectors though, if they continue to increment upward over time you'll want to RMA the drives. Most large drives have a thousand or more spare sectors so 120 is not a killer number. I'd perform another pre-clear on it if they were detected during the pre-clearing process. (not present in the pre-clear SMART report, but present in the post-clear SMART report)
September 5, 201015 yr Drive temp is pretty high at 44C. Recommend you add cooling before doing too much with the drive. As as been said, a few (even a few hundred) reallocated sectors in not necessarily a problem. The problem is that once you have even one or two of them, there is a tendency for the count to grow and grow with use and especially with parity checks. This is a very clear sign that the drive is self-destructing and not to be trusted with data. The errors in the log are usually signs of some type of cabling problem. It is not unusual to get a flurry of them early in the life of a drive as the owner is first setting it up and a cable is not securely connected. Your errors look different than I've seen before, and are spread out over time - one at 126 "power on" days, two at 254 days, and two at 418 days. And the 2 most recent errors happened recently (about 70 "power on hours" ago). I'd still recommend replacing the SATA cable with a known good one before doing more testing with the drive. If you continue to get these log errors then I'd start to get concerned.
Archived
This topic is now archived and is closed to further replies.