mobias1313 Posted March 3, 2013 Share Posted March 3, 2013 The drive is about two days old. Should I consider trying for an RMA or return at this point? Quote Link to comment
Automatic Posted March 3, 2013 Share Posted March 3, 2013 The drive is about two days old. Should I consider trying for an RMA or return at this point? Yes, at-least, I'd say so. I'd recommend someone else with more knowledge confirm/deny what I think, but, I'd say yes. The "WORST"/normalized value is already pretty low for a drive, let alone a brand new one. Quote Link to comment
mobias1313 Posted March 3, 2013 Share Posted March 3, 2013 I am running a second preclear on the good drive right now and if that passes I am going to run at least one preclear on the rest of the drives I picked up before I request the rma. Hopefully I just got one bad one. Thanks for pointing the reallocating sectors. I didn't notice it when I first looked at the log. I must have not been paying close enough attention. The first drive showed zero reallocated sectors so I am thinking it will probably end up being a good one. Quote Link to comment
Automatic Posted March 3, 2013 Share Posted March 3, 2013 I am running a second preclear on the good drive right now and if that passes I am going to run at least one preclear on the rest of the drives I picked up before I request the rma. Hopefully I just got one bad one. Thanks for pointing the reallocating sectors. I didn't notice it when I first looked at the log. I must have not been paying close enough attention. The first drive showed zero reallocated sectors so I am thinking it will probably end up being a good one. Hopefully it is a good one, but, obviously eventually every drive will fail, just a matter of when. Quote Link to comment
Joe L. Posted March 4, 2013 Share Posted March 4, 2013 The drive is about two days old. Should I consider trying for an RMA or return at this point? I'd say yes, absolutely. Quote Link to comment
mobias1313 Posted March 4, 2013 Share Posted March 4, 2013 I appreciate all the help guys. I am going to try out the preclear on the other disks I bought before I try to do the return. Joe L. thanks for this script. You just saved me from losing a lot of data. Quote Link to comment
shooga Posted March 4, 2013 Share Posted March 4, 2013 Noticed these errors in my log during preclear. Does this indicate a controller problem? Edit: Realizing that this is actually my cache drive, not one being precleared. Also realizing that I used a cable on the cache drive that may not be compatible with SATAII or SATAIII (it came with a SATAI controller). Could this be the issue? Mar 3 19:09:00 Bunker kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Mar 3 19:09:00 Bunker kernel: ata4.00: failed command: WRITE DMA EXT Mar 3 19:09:00 Bunker kernel: ata4.00: cmd 35/00:00:d0:4c:09/00:04:45:00:00/e0 tag 0 dma 524288 out Mar 3 19:09:00 Bunker kernel: res 40/00:00:01:4f:c2/00:00:45:00:00/10 Emask 0x4 (timeout) Mar 3 19:09:00 Bunker kernel: ata4.00: status: { DRDY } Mar 3 19:09:00 Bunker kernel: ata4: hard resetting link Mar 3 19:09:05 Bunker kernel: ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Mar 3 19:09:05 Bunker kernel: ata4.00: configured for UDMA/100 Mar 3 19:09:05 Bunker kernel: ata4: EH complete Mar 3 19:10:18 Bunker kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Mar 3 19:10:18 Bunker kernel: ata4.00: failed command: WRITE DMA EXT Mar 3 19:10:18 Bunker kernel: ata4.00: cmd 35/00:00:d0:b4:0a/00:04:45:00:00/e0 tag 0 dma 524288 out Mar 3 19:10:18 Bunker kernel: res 40/00:00:01:4f:c2/00:00:45:00:00/10 Emask 0x4 (timeout) Mar 3 19:10:18 Bunker kernel: ata4.00: status: { DRDY } Mar 3 19:10:18 Bunker kernel: ata4: hard resetting link Mar 3 19:10:23 Bunker kernel: ata4: link is slow to respond, please be patient (ready=-19) Mar 3 19:10:24 Bunker kernel: ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Mar 3 19:10:24 Bunker kernel: ata4.00: configured for UDMA/100 Mar 3 19:10:24 Bunker kernel: ata4: EH complete Mar 3 19:11:08 Bunker kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Mar 3 19:11:08 Bunker kernel: ata4.00: failed command: WRITE DMA EXT Mar 3 19:11:08 Bunker kernel: ata4.00: cmd 35/00:00:48:ca:0b/00:04:45:00:00/e0 tag 0 dma 524288 out Mar 3 19:11:08 Bunker kernel: res 40/00:00:01:4f:c2/00:00:45:00:00/10 Emask 0x4 (timeout) Mar 3 19:11:08 Bunker kernel: ata4.00: status: { DRDY } Mar 3 19:11:08 Bunker kernel: ata4: hard resetting link Mar 3 19:11:13 Bunker kernel: ata4: link is slow to respond, please be patient (ready=-19) Mar 3 19:11:18 Bunker kernel: ata4: COMRESET failed (errno=-16) Mar 3 19:11:18 Bunker kernel: ata4: hard resetting link Mar 3 19:11:23 Bunker kernel: ata4: link is slow to respond, please be patient (ready=-19) Mar 3 19:11:28 Bunker kernel: ata4: COMRESET failed (errno=-16) Mar 3 19:11:28 Bunker kernel: ata4: hard resetting link Mar 3 19:11:30 Bunker kernel: ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Mar 3 19:11:30 Bunker kernel: ata4.00: configured for UDMA/100 Mar 3 19:11:30 Bunker kernel: ata4: EH complete Mar 3 19:12:01 Bunker kernel: ata4.00: limiting speed to UDMA/66:PIO4 Mar 3 19:12:01 Bunker kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Mar 3 19:12:01 Bunker kernel: ata4.00: failed command: WRITE DMA EXT Mar 3 19:12:01 Bunker kernel: ata4.00: cmd 35/00:00:48:e2:0b/00:04:45:00:00/e0 tag 0 dma 524288 out Mar 3 19:12:01 Bunker kernel: res 40/00:00:01:4f:c2/00:00:45:00:00/10 Emask 0x4 (timeout) Mar 3 19:12:01 Bunker kernel: ata4.00: status: { DRDY } Mar 3 19:12:01 Bunker kernel: ata4: hard resetting link Mar 3 19:12:06 Bunker kernel: ata4: link is slow to respond, please be patient (ready=-19) Mar 3 19:12:11 Bunker kernel: ata4: COMRESET failed (errno=-16) Mar 3 19:12:11 Bunker kernel: ata4: hard resetting link Mar 3 19:12:16 Bunker kernel: ata4: link is slow to respond, please be patient (ready=-19) Mar 3 19:12:21 Bunker kernel: ata4: COMRESET failed (errno=-16) Mar 3 19:12:21 Bunker kernel: ata4: hard resetting link Mar 3 19:12:26 Bunker kernel: ata4: link is slow to respond, please be patient (ready=-19) Mar 3 19:12:56 Bunker kernel: ata4: COMRESET failed (errno=-16) Mar 3 19:12:56 Bunker kernel: ata4: hard resetting link Mar 3 19:13:00 Bunker kernel: ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Mar 3 19:13:02 Bunker kernel: ata4.00: configured for UDMA/66 Mar 3 19:13:02 Bunker kernel: ata4: EH complete Quote Link to comment
Just Me Posted March 4, 2013 Share Posted March 4, 2013 I've similar errors in my log: Mar 3 16:03:23 NAS kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen (Errors) Mar 3 16:03:23 NAS kernel: ata4.00: failed command: SMART (Minor Issues) Mar 3 16:03:23 NAS kernel: ata4.00: cmd b0/d1:01:01:4f:c2/00:00:00:00:00/00 tag 0 pio 512 in (Drive related) Mar 3 16:03:23 NAS kernel: res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) (Errors) Mar 3 16:03:23 NAS kernel: ata4.00: status: { DRDY } (Drive related) Mar 3 16:03:23 NAS kernel: ata4: hard resetting link (Minor Issues) Mar 3 16:03:24 NAS kernel: ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300) (Drive related) Mar 3 16:03:24 NAS kernel: ata4.00: configured for UDMA/133 (Drive related) Mar 3 16:03:24 NAS kernel: ata4: EH complete (Drive related) Mar 3 16:16:39 NAS kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen (Errors) Mar 3 16:16:39 NAS kernel: ata4.00: failed command: SMART (Minor Issues) Mar 3 16:16:39 NAS kernel: ata4.00: cmd b0/d1:01:01:4f:c2/00:00:00:00:00/00 tag 0 pio 512 in (Drive related) Mar 3 16:16:39 NAS kernel: res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) (Errors) Mar 3 16:16:39 NAS kernel: ata4.00: status: { DRDY } (Drive related) Mar 3 16:16:39 NAS kernel: ata4: hard resetting link (Minor Issues) Mar 3 16:16:40 NAS kernel: ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300) (Drive related) Mar 3 16:16:40 NAS kernel: ata4.00: configured for UDMA/133 (Drive related) Mar 3 16:16:40 NAS kernel: ata4: EH complete (Drive related) Mar 3 16:19:32 NAS kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen (Errors) Mar 3 16:19:32 NAS kernel: ata4.00: failed command: SMART (Minor Issues) Mar 3 16:19:32 NAS kernel: ata4.00: cmd b0/d1:01:01:4f:c2/00:00:00:00:00/00 tag 0 pio 512 in (Drive related) Mar 3 16:19:32 NAS kernel: res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) (Errors) Mar 3 16:19:32 NAS kernel: ata4.00: status: { DRDY } (Drive related) Mar 3 16:19:32 NAS kernel: ata4: hard resetting link (Minor Issues) Mar 3 16:19:33 NAS kernel: ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300) (Drive related) Mar 3 16:19:33 NAS kernel: ata4.00: configured for UDMA/133 (Drive related) Mar 3 16:19:33 NAS kernel: ata4: EH complete (Drive related) Mar 3 16:26:14 NAS kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen (Errors) Mar 3 16:26:14 NAS kernel: ata4.00: failed command: SMART (Minor Issues) Mar 3 16:26:14 NAS kernel: ata4.00: cmd b0/d1:01:01:4f:c2/00:00:00:00:00/00 tag 0 pio 512 in (Drive related) Mar 3 16:26:14 NAS kernel: res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) (Errors) Mar 3 16:26:14 NAS kernel: ata4.00: status: { DRDY } (Drive related) Mar 3 16:26:14 NAS kernel: ata4: hard resetting link (Minor Issues) Mar 3 16:26:15 NAS kernel: ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300) (Drive related) Mar 3 16:26:15 NAS kernel: ata4.00: configured for UDMA/133 (Drive related) Mar 3 16:26:15 NAS kernel: ata4: EH complete (Drive related) Mar 3 19:12:57 NAS kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen (Errors) Mar 3 19:12:57 NAS kernel: ata4.00: failed command: SMART (Minor Issues) Mar 3 19:12:57 NAS kernel: ata4.00: cmd b0/d0:01:00:4f:c2/00:00:00:00:00/00 tag 0 pio 512 in (Drive related) Mar 3 19:12:57 NAS kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) (Errors) Mar 3 19:12:57 NAS kernel: ata4.00: status: { DRDY } (Drive related) Mar 3 19:12:57 NAS kernel: ata4: hard resetting link (Minor Issues) Mar 3 19:12:58 NAS kernel: ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300) (Drive related) Mar 3 19:12:58 NAS kernel: ata4.00: configured for UDMA/133 (Drive related) Mar 3 19:12:58 NAS kernel: ata4: EH complete (Drive related) Quote Link to comment
Automatic Posted March 4, 2013 Share Posted March 4, 2013 Interesting in that the end-to-end error says FAILING_NOW, but the overall smart status is PASSED. I would RMA the drive on just that. Buggy firmware. Yu can ignore any warnings from the preclear script about fdisk and gpt partitions on drives over 2.2TB. The GPT partitions are expected, and fdisk is only being used to read the MBR, not partition the disk, so it is safe. Joe L. Well I just finished the preclear (I had to restart it half way through so it took longer than I wanted):- ========================================================================1.13 == invoked as: ./preclear_disk.sh -c 3 -A /dev/sdi == ST3000DM001-1CH166 Z1F0Z1XZ == Disk /dev/sdi has been successfully precleared == with a starting sector of 1 == Ran 3 cycles == == Using :Read block size = 8225280 Bytes == Last Cycle's Pre Read Time : 6:12:37 (134 MB/s) == Last Cycle's Zeroing time : 5:23:07 (154 MB/s) == Last Cycle's Post Read Time : 13:44:00 (60 MB/s) == Last Cycle's Total Time : 19:08:06 == == Total Elapsed Time 63:35:08 == == Disk Start Temperature: 23C == == Current Disk Temperature: 21C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdi /tmp/smart_finish_sdi ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 119 117 6 ok 214627440 Seek_Error_Rate = 63 62 30 ok 12891315746 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 99 99 99 FAILING_NOW 1 High_Fly_Writes = 98 100 0 ok 2 Airflow_Temperature_Cel = 79 77 45 ok 21 Temperature_Celsius = 21 23 0 near_thresh 21 *** Failing SMART Attributes in /tmp/smart_finish_sdi *** ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 184 End-to-End_Error 0x0032 099 099 099 Old_age Always FAILING_NOW 1 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 3. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 3. 0 sectors were pending re-allocation after post-read in cycle 1 of 3. 0 sectors were pending re-allocation after zero of disk in cycle 2 of 3. 0 sectors were pending re-allocation after post-read in cycle 2 of 3. 0 sectors were pending re-allocation after zero of disk in cycle 3 of 3. 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. ============================================================================ Disk: /dev/sdi smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Device Model: ST3000DM001-1CH166 Serial Number: Z1F0Z1XZ Firmware Version: CC43 User Capacity: 3,000,592,982,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: Fri Mar 1 18:38:01 2013 GMT 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 See vendor-specific Attribute list for marginal Attributes. 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: ( 600) 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: ( 255) minutes. Conveyance self-test routine recommended polling time: ( 2) minutes. SCT capabilities: (0x3085) 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 117 099 006 Pre-fail Always - 124495464 3 Spin_Up_Time 0x0003 091 090 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 87 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 062 055 030 Pre-fail Always - 12890524138 9 Power_On_Hours 0x0032 097 097 000 Old_age Always - 3398 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 48 183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0 184 End-to-End_Error 0x0032 099 099 099 Old_age Always FAILING_NOW 1 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 188 Command_Timeout 0x0032 100 100 000 Old_age Always - 0 189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0022 077 057 045 Old_age Always - 23 (Min/Max 21/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 - 34 193 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 907 194 Temperature_Celsius 0x0022 023 043 000 Old_age Always - 23 (0 16 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 - 768 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 280375465086154 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 34218637385 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 62236349612 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 Conveyance offline Completed without error 00% 2877 - 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. Disk: /dev/sdi smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Device Model: ST3000DM001-1CH166 Serial Number: Z1F0Z1XZ Firmware Version: CC43 User Capacity: 3,000,592,982,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: Mon Mar 4 10:13:09 2013 GMT 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 See vendor-specific Attribute list for marginal Attributes. 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: ( 600) 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: ( 255) minutes. Conveyance self-test routine recommended polling time: ( 2) minutes. SCT capabilities: (0x3085) 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 119 099 006 Pre-fail Always - 214627440 3 Spin_Up_Time 0x0003 091 090 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 87 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 063 055 030 Pre-fail Always - 12891315746 9 Power_On_Hours 0x0032 097 097 000 Old_age Always - 3462 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 48 183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0 184 End-to-End_Error 0x0032 099 099 099 Old_age Always FAILING_NOW 1 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 188 Command_Timeout 0x0032 100 100 000 Old_age Always - 0 189 High_Fly_Writes 0x003a 098 098 000 Old_age Always - 2 190 Airflow_Temperature_Cel 0x0022 079 057 045 Old_age Always - 21 (Min/Max 20/25) 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 - 34 193 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 907 194 Temperature_Celsius 0x0022 021 043 000 Old_age Always - 21 (0 16 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 - 768 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 149001005436169 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 51800237033 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 103870161290 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 Conveyance offline Completed without error 00% 2877 - 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 honestly have no idea how bad an end_to_end error is. If you think it's worth RMAing I will, I just want your opinion post preclear. Quote Link to comment
Just Me Posted March 4, 2013 Share Posted March 4, 2013 Interesting, I had the same drive and the same end-to-end error. Coincidence? Probably. Quote Link to comment
Automatic Posted March 4, 2013 Share Posted March 4, 2013 Interesting, I had the same drive and the same end-to-end error. Coincidence? Probably. Quote Link to comment
Joe L. Posted March 4, 2013 Share Posted March 4, 2013 It is not my opinion.. It is the disk's manufacturer. That attribute is FAILING_NOW. I would not trust that disk with my data. Joe L. Quote Link to comment
Automatic Posted March 4, 2013 Share Posted March 4, 2013 It is not my opinion.. It is the disk's manufacturer. That attribute is FAILING_NOW. I would not trust that disk with my data. Joe L. Okay, RMAing it. By any chance do you know how long they take to send a new drive? I'll be out of the house for a week or two starting next week, so, I might wait to return it. Quote Link to comment
BobPhoenix Posted March 4, 2013 Share Posted March 4, 2013 I just picked up some new drives the other day and was going through the preclear but seem to have hit a snag. The first disk precleared with no problems at all. The second however seems to fail for some reason at either 36% or 37% on the disk pre-read everytime I try to run it. It will just seem to stop reading and the script will no longer update. Any thoughts are greatly appreciated. I had a drive like that. As a last attempt before I RMA'd it I took the drive to a Windows PC and did a long format. After that completed with no errors I was able to run 3 preclear cycles on it like normal. SO long story short you could try writing to the drive first by using the '-n' parameter of preclear for a single cycle first. Then run however many preclear cycles you wanted to run. That is essentially what I did with a windows long format. Quote Link to comment
Automatic Posted March 4, 2013 Share Posted March 4, 2013 I just picked up some new drives the other day and was going through the preclear but seem to have hit a snag. The first disk precleared with no problems at all. The second however seems to fail for some reason at either 36% or 37% on the disk pre-read everytime I try to run it. It will just seem to stop reading and the script will no longer update. Any thoughts are greatly appreciated. I had a drive like that. As a last attempt before I RMA'd it I took the drive to a Windows PC and did a long format. After that completed with no errors I was able to run 3 preclear cycles on it like normal. SO long story short you could try writing to the drive first by using the '-n' parameter of preclear for a single cycle first. Then run however many preclear cycles you wanted to run. That is essentially what I did with a windows long format. I also have a drive like that (See here), going to try a -n format in a second (Gotta restart the server so the disk starts responding). Thanks for the tip, I'll update this post with the results in 5 minutes to 24 hours (Depending on if it's obvious it's working or not). EDIT (Not the results):- I just thought I'd mention the drive that I'm having issues with was working fine in windows just before I transferred it. EDIT (Small results):- Setup warning (With call functions);- and, holy hell, it seems to be working:- Gonna restart this preclear with screen enabled (I didn't bother to set up screen since I doubted it'd work). Thanks dude, I think you just fixed my drive (I was getting ready to send the raid controller back, as I thought it was it not supporting multiple 3TB HDDs or something). Quote Link to comment
Automatic Posted March 4, 2013 Share Posted March 4, 2013 It failed, does anyone know what this means:- ================================================================== 1.13 = unRAID server Pre-Clear disk /dev/sdj = cycle 1 of 1, partition start on sector 1 = = 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 = Elapsed Time: 0:14:15 ========================================================================1.13 == == SORRY: Disk /dev/sdj MBR could NOT be precleared == == out4= 00000 == out5= 00000 ============================================================================ 0000000 0+0 records in 0+0 records out 0 bytes (0 B) copied, 5.9654e-05 s, 0.0 kB/s root@Tower:/boot# It was run with command -n, so, how does it know it failed? It shouldn't have read anything back. EDIT:- It dropped during the test or something, when I tried to restart I got this:- root@Tower:/boot# preclear_disk.sh /dev/sdj Sorry: Device /dev/sdj is not responding to an fdisk -l /dev/sdj command. You might try power-cycling it to see if it will start responding. root@Tower:/boot# EDIT System log regarding it:- Mar 4 16:40:57 Tower kernel: sd 0:0:2:0: [sdj] READ CAPACITY(16) failed Mar 4 16:40:57 Tower kernel: sd 0:0:2:0: [sdj] Result: hostbyte=0x04 driverbyte=0x00 Mar 4 16:40:57 Tower kernel: sd 0:0:2:0: [sdj] Sense not available. Mar 4 16:40:57 Tower kernel: sd 0:0:2:0: [sdj] READ CAPACITY failed Mar 4 16:40:57 Tower kernel: sd 0:0:2:0: [sdj] Result: hostbyte=0x04 driverbyte=0x00 Mar 4 16:40:57 Tower kernel: sd 0:0:2:0: [sdj] Sense not available. Mar 4 16:40:57 Tower kernel: sd 0:0:2:0: [sdj] Asking for cache data failed Mar 4 16:40:57 Tower kernel: sd 0:0:2:0: [sdj] Assuming drive cache: write through Quote Link to comment
itimpi Posted March 4, 2013 Share Posted March 4, 2013 It is saying the MBR was not cleared, so I expect 10 failed (that WILL read back the MBR). Quote Link to comment
Automatic Posted March 4, 2013 Share Posted March 4, 2013 It is saying the MBR was not cleared, so I expect 10 failed (that WILL read back the MBR). But doesn't it wipe the MBR on step 4 & 5? Why is it still corrupt(?)? Quote Link to comment
itimpi Posted March 4, 2013 Share Posted March 4, 2013 It is saying the MBR was not cleared, so I expect 10 failed (that WILL read back the MBR). But doesn't it wipe the MBR on step 4 & 5? Why is it still corrupt(?)? No idea - I assume that the write or read of the MBR did not work as expected. Maybe Joe L. will see this thread and have further insights. Quote Link to comment
Joe L. Posted March 4, 2013 Share Posted March 4, 2013 It is saying the MBR was not cleared, so I expect 10 failed (that WILL read back the MBR). But doesn't it wipe the MBR on step 4 & 5? Why is it still corrupt(?)? It is still corrupt because the bytes tested as "out4" and "out5" were not supposed to contain zeros. (At that point in time out4 should have been 00170, and out5 should have been 00085.) Those two bytes should have been written in step 6. If, as you say, the disk stopped responding at all, and does not even respond to an fdisk -l command, that would explain it. (The disk could have died, or a cable to it may have come loose, or it is loose in a drive tray, or the power to it is insufficient and it locked up refusing to respond until power cycled, or the disk controller locked up, or a disk it is paired with locked up the pair of drives on the controller.) Joe L. Quote Link to comment
Automatic Posted March 4, 2013 Share Posted March 4, 2013 It is saying the MBR was not cleared, so I expect 10 failed (that WILL read back the MBR). But doesn't it wipe the MBR on step 4 & 5? Why is it still corrupt(?)? No idea - I assume that the write or read of the MBR did not work as expected. Maybe Joe L. will see this thread and have further insights. Found this:- http://castyour.net/how-write-zeros-all-sectors-drive-under-linux Not too sure though if the MBR counts as a sector (Well, it does, it's sector 0. Just not sure if it's ask "accessible" as the other sectors), I hope it does. Wiping it with that to see if it works:- If this also fails, I guess I'll have to go through the annoying process of flopping disks around to get it into a windows build and back again. @Joe, it seems to fail the second you try to read from it, apparently (From reading threads off this forum) it's a sort of (Not always, but high enough for a few people to make threads about it) common issue when you transfer a disk from windows to unraid. EDIT:- shred: /dev/sdj: pass 1/1 (000000)...64GiB/2.8TiB 2% shred: /dev/sdj: pass 1/1 (000000)...65GiB/2.8TiB 2% shred: /dev/sdj: error writing at offset 70646452224: No space left on device I feel as though I screwed something up. I think I'll just download DBAN to another flash drive and unplug all HDDs except this one, I really don't want to bother unscrewing this drive from the drive cage, takes me a good thirty minutes to screw it back in. EDIT:- K, hopefully this works. Quote Link to comment
BobPhoenix Posted March 4, 2013 Share Posted March 4, 2013 If your solution doesn't work and if windows can do a long format then you could try that but I don't think you will get it to format in windows if your solution doesn't clear it. You could also try badblocks or SpinRite and see if they can recover the drive but I doubt it is a disk surface problem (what they are good for) and more an electronics/cabling/power problem like Joe L said. I'm betting that even though it was working in windows before either the drive is defective now or you have a cable/power problem. Quote Link to comment
Automatic Posted March 5, 2013 Share Posted March 5, 2013 If your solution doesn't work and if windows can do a long format then you could try that but I don't think you will get it to format in windows if your solution doesn't clear it. You could also try badblocks or SpinRite and see if they can recover the drive but I doubt it is a disk surface problem (what they are good for) and more an electronics/cabling/power problem like Joe L said. I'm betting that even though it was working in windows before either the drive is defective now or you have a cable/power problem. I've tried with two different sata cables, using both direct connection to MOBO & a raid card. As for the power cable, I will admit I didn't change that, although, I did take it out and put it back in. DBAN also failed, so, currently doing it in windows (Read the thread I linked above):- I think I'll probably be going to bed soon, so, I'll have to continue the rest of the process tomorrow morn. Quote Link to comment
shooga Posted March 5, 2013 Share Posted March 5, 2013 This is an old drive and I see a couple attributes that are near the threshold. Should it be retired? Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: SMART Attributes Data Structure revision number: 10 Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: Vendor Specific SMART Attributes with Thresholds: Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: 1 Raw_Read_Error_Rate 0x000f 117 099 006 Pre-fail Always - 137310847 Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: 3 Spin_Up_Time 0x0003 096 095 000 Pre-fail Always - 0 Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 98 Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0 Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: 7 Seek_Error_Rate 0x000f 075 060 030 Pre-fail Always - 34750361 Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: 9 Power_On_Hours 0x0032 071 071 000 Old_age Always - 26180 Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 48 Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: 184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0 Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: 188 Command_Timeout 0x0032 100 100 000 Old_age Always - 0 Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: 189 High_Fly_Writes 0x003a 056 056 000 Old_age Always - 44 Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: 190 Airflow_Temperature_Cel 0x0022 070 059 045 Old_age Always - 30 (Min/Max 22/33) Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: 194 Temperature_Celsius 0x0022 030 041 000 Old_age Always - 30 (0 19 0 0) Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: 195 Hardware_ECC_Recovered 0x001a 053 048 000 Old_age Always - 137310847 Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 2 Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: SMART Error Log Version: 1 Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: No Errors Logged Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: SMART Self-test log structure revision number 1 Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: No self-tests have been logged. [To run self-tests, use: smartctl -t] Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: SMART Selective self-test log data structure revision number 1 Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: 1 0 0 Not_testing Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: 2 0 0 Not_testing Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: 3 0 0 Not_testing Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: 4 0 0 Not_testing Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: 5 0 0 Not_testing Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: Selective self-test flags (0x0): Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: After scanning selected spans, do NOT read-scan remainder of disk. Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: If Selective self-test is pending on power-up, resume after 0 minute delay. Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: == Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: ============================================================================ Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: Mar 4 16:27:45 Bunker last message repeated 2 times Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: ============================================================================ Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: == Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: == S.M.A.R.T Final Report for /dev/sda Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: == Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: Disk: /dev/sda Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: === START OF INFORMATION SECTION === Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: Model Family: Seagate Pipeline HD 5900.2 family Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: Device Model: ST31000322CS Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: Serial Number: 9VX0JHEY Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: Firmware Version: SC13 Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: User Capacity: 1,000,204,886,016 bytes Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: Device is: In smartctl database [for details use: -P show] Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: ATA Version is: 8 Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: ATA Standard is: ATA-8-ACS revision 4 Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: Local Time is: Mon Mar 4 16:27:43 2013 PST Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: SMART support is: Available - device has SMART capability. Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: SMART support is: Enabled Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: === START OF READ SMART DATA SECTION === Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: SMART overall-health self-assessment test result: PASSED Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: General SMART Values: Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: Offline data collection status: (0x00)^IOffline data collection activity Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: ^I^I^I^I^Iwas never started. Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: ^I^I^I^I^IAuto Offline Data Collection: Disabled. Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: Self-test execution status: ( 0)^IThe previous self-test routine completed Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: ^I^I^I^I^Iwithout error or no self-test has ever Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: ^I^I^I^I^Ibeen run. Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: Total time to complete Offline Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: data collection: ^I^I ( 633) seconds. Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: Offline data collection Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: capabilities: ^I^I^I (0x73) SMART execute Offline immediate. Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: ^I^I^I^I^IAuto Offline data collection on/off support. Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: ^I^I^I^I^ISuspend Offline collection upon new Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: ^I^I^I^I^Icommand. Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: ^I^I^I^I^INo Offline surface scan supported. Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: ^I^I^I^I^ISelf-test supported. Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: ^I^I^I^I^IConveyance Self-test supported. Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: ^I^I^I^I^ISelective Self-test supported. Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: SMART capabilities: (0x0003)^ISaves SMART data before entering Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: ^I^I^I^I^Ipower-saving mode. Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: ^I^I^I^I^ISupports SMART auto save timer. Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: Error logging capability: (0x01)^IError logging supported. Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: ^I^I^I^I^IGeneral Purpose Logging supported. Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: Short self-test routine Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: recommended polling time: ^I ( 1) minutes. Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: Extended self-test routine Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: recommended polling time: ^I ( 215) minutes. Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: Conveyance self-test routine Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: recommended polling time: ^I ( 2) minutes. Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: SCT capabilities: ^I (0x103b)^ISCT Status supported. Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: ^I^I^I^I^ISCT Error Recovery Control supported. Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: ^I^I^I^I^ISCT Feature Control supported. Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: ^I^I^I^I^ISCT Data Table supported. Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: SMART Attributes Data Structure revision number: 10 Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: Vendor Specific SMART Attributes with Thresholds: Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: 1 Raw_Read_Error_Rate 0x000f 109 099 006 Pre-fail Always - 24025869 Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: 3 Spin_Up_Time 0x0003 096 095 000 Pre-fail Always - 0 Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 98 Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0 Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: 7 Seek_Error_Rate 0x000f 075 060 030 Pre-fail Always - 34834273 Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: 9 Power_On_Hours 0x0032 071 071 000 Old_age Always - 26233 Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 48 Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: 184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0 Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: 188 Command_Timeout 0x0032 100 100 000 Old_age Always - 0 Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: 189 High_Fly_Writes 0x003a 056 056 000 Old_age Always - 44 Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: 190 Airflow_Temperature_Cel 0x0022 068 059 045 Old_age Always - 32 (Min/Max 22/33) Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: 194 Temperature_Celsius 0x0022 032 041 000 Old_age Always - 32 (0 19 0 0) Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: 195 Hardware_ECC_Recovered 0x001a 053 048 000 Old_age Always - 24025869 Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 2 Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: SMART Error Log Version: 1 Mar 4 16:27:45 Bunker preclear_disk-diff[8976]: No Errors Logged Quote Link to comment
Joe L. Posted March 5, 2013 Share Posted March 5, 2013 This is an old drive and I see a couple attributes that are near the threshold. Should it be retired? Probably not. Which specific attributes have you concerned? Joe L. 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.