Point7 Posted December 31, 2011 Share Posted December 31, 2011 I'm worried about the re-allocation sectors. me too. They seem to always be re-written into place, so I'd suspect the power supply as an additional thing to check. (poor quality power might contribute to a poor quality write of the disk) In general, I'd not trust my data on it. Joe L. That's my second Samsung HD154UI in a few weeks time that is gone bad. The first Samsung drive gave read errors (bad sectors) when restoring a Windows Home Server backup. Luckily I could restore an 3 month old image from that drive (all the other images where bad). This drive does not pass the pre-clear test when I removed it from my WHS. Now I make backups of my backup images on the WHS. Quote Link to comment
spinbot Posted January 1, 2012 Share Posted January 1, 2012 Just running this by the experts in case anything stands out as a concern, like the 2 items that say "near_thresh": root@Tower:/boot# screen ** Changed attributes in files: /tmp/smart_start_sdf /tmp/smart_finish_sdf ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 118 120 6 ok 168294896 Seek_Error_Rate = 60 100 30 ok 1063419 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 Airflow_Temperature_Cel = 72 75 45 ok 28 Temperature_Celsius = 28 25 0 ok 28 Hardware_ECC_Recovered = 37 30 0 ok 168294896 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@Tower:/boot# Quote Link to comment
Blofeld Posted January 2, 2012 Share Posted January 2, 2012 So here's the result of my WD 2TB EARS...anyone wanna take a peek and see whether it's juicy, healthy, and all-around delicious? thank! Disk: /dev/sdd smartctl 5.39.1 2010-01-28 r3054 [i486-slackware-linux-gnu] (local build) Copyright © 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Device Model: WDC WD20EARS-00MVWB0 Serial Number: WD-WCAZA6120287 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: Mon Jan 2 19:21:28 2012 CET 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: (0x80) Offline data collection activity was never started. 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: (37260) 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 200 200 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0027 253 161 021 Pre-fail Always - 1225 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 68 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 100 253 000 Old_age Always - 0 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 58 10 Spin_Retry_Count 0x0032 100 253 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 28 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 19 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 480 194 Temperature_Celsius 0x0022 125 115 000 Old_age Always - 25 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 100 253 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 100 253 000 Old_age Offline - 0 SMART Error Log Version: 1 No Errors Logged Quote Link to comment
Joe L. Posted January 2, 2012 Share Posted January 2, 2012 So here's the result of my WD 2TB EARS...anyone wanna take a peek and see whether it's juicy, healthy, and all-around delicious? thank! that is not the output of the preclear_disk.sh script. looks ok, but no idea if it was successfully cleared or not. Quote Link to comment
Blofeld Posted January 2, 2012 Share Posted January 2, 2012 So here's the result of my WD 2TB EARS...anyone wanna take a peek and see whether it's juicy, healthy, and all-around delicious? thank! that is not the output of the preclear_disk.sh script. looks ok, but no idea if it was successfully cleared or not. oops...I took what I thought was the right file (from the preclear reports folder). It was the one called preclear_finish_WD_xxx. It said on the console directly on the server that it successfully precleared, but I didn't have a telnet session open so I could paste that here (btw, how do you re-login to a running preclear session via telnet?). For what it's worth, I'll just attach the other two reports here...I hope you can see what you need to see - if not, I guess I'll have to go looking somewhere else.. preclear_start__WD-WCAZA6120287_2012-01-02.txt preclear_rpt__WD-WCAZA6120287_2012-01-02.txt Quote Link to comment
Hoopster Posted January 3, 2012 Share Posted January 3, 2012 I just received two Seagate ST2000DL003 2TB drives from Amazon. I have run two preclear cycles. One has passed both preclear cycles with no SMART failures; One has failed on both preclear cycles with a SMART seek_error_rate failure. Raw_Read_Error_Rate looks very high as well. The drive that "passed" also had high values for these parameters although not nearly as high as these. Of five drives I have precleared, this is the only one to show a failure and I have never seen a failure in any desktop drive so I am not sure how reliable the SMART reports are. What say ye; should I return this to Amazon? I assume this is a legitimate indication of a bad drive as the seek_error_rate values seems incredibly high. Here is the SMART report generated at the end of the preclear with some information redacted: SMART status Info for /dev/sdc smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) Copyright © 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Device Model: ST2000DL003-9VT166 Serial Number: 5YD6HZP5 Firmware Version: CC3C 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: ATA-8-ACS revision 4 Local Time is: Sun Jan 1 11:39:35 2012 MST 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: FAILED! Drive failure expected in less than 24 hours. SAVE ALL DATA. See vendor-specific Attribute list for failed Attributes. 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: ( 623) 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: (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 100 006 Pre-fail Always - 105386328 3 Spin_Up_Time 0x0003 092 092 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 9 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 028 026 030 Pre-fail Always FAILING_NOW 13464724458629 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 38 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 9 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 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 068 065 045 Old_age Always - 32 (Min/Max 28/35) 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 - 7 193 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 9 194 Temperature_Celsius 0x0022 032 040 000 Old_age Always - 32 (0 22 0 0) 195 Hardware_ECC_Recovered 0x001a 037 024 000 Old_age Always - 105386328 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 - 1 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 66468913872934 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 2469991065 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 4264727547 Quote Link to comment
Blofeld Posted January 3, 2012 Share Posted January 3, 2012 ok, so, finally, I hope: I copied this from the syslog, and I think it's the right one: Jan 2 19:21:29 Tower preclear_disk-diff[1897]: ========================================================================1.13 Jan 2 19:21:29 Tower preclear_disk-diff[1897]: == invoked as: ./preclear_disk.sh -A /dev/sdd Jan 2 19:21:29 Tower preclear_disk-diff[1897]: == WDC WD20EARS-00MVWB0 WD-WCAZA6120287 Jan 2 19:21:29 Tower preclear_disk-diff[1897]: == Disk /dev/sdd has been successfully precleared Jan 2 19:21:29 Tower preclear_disk-diff[1897]: == with a starting sector of 64 Jan 2 19:21:29 Tower preclear_disk-diff[1897]: == Ran 1 cycle Jan 2 19:21:29 Tower preclear_disk-diff[1897]: == Jan 2 19:21:29 Tower preclear_disk-diff[1897]: == Using :Read block size = 8225280 Bytes Jan 2 19:21:29 Tower preclear_disk-diff[1897]: == Last Cycle's Pre Read Time : 6:27:42 (85 MB/s) Jan 2 19:21:29 Tower preclear_disk-diff[1897]: == Last Cycle's Zeroing time : 6:06:21 (91 MB/s) Jan 2 19:21:29 Tower preclear_disk-diff[1897]: == Last Cycle's Post Read Time : 13:34:01 (40 MB/s) Jan 2 19:21:29 Tower preclear_disk-diff[1897]: == Last Cycle's Total Time : 26:09:12 Jan 2 19:21:29 Tower preclear_disk-diff[1897]: == Jan 2 19:21:29 Tower preclear_disk-diff[1897]: == Total Elapsed Time 26:09:12 Jan 2 19:21:29 Tower preclear_disk-diff[1897]: == Jan 2 19:21:29 Tower preclear_disk-diff[1897]: == Disk Start Temperature: 21C Jan 2 19:21:29 Tower preclear_disk-diff[1897]: == Jan 2 19:21:29 Tower preclear_disk-diff[1897]: == Current Disk Temperature: 25C, Jan 2 19:21:29 Tower preclear_disk-diff[1897]: == Jan 2 19:21:29 Tower preclear_disk-diff[1897]: ============================================================================ Jan 2 19:21:29 Tower preclear_disk-diff[1897]: ** Changed attributes in files: /tmp/smart_start_sdd /tmp/smart_finish_sdd Jan 2 19:21:29 Tower preclear_disk-diff[1897]: ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Jan 2 19:21:29 Tower preclear_disk-diff[1897]: Seek_Error_Rate = 100 200 0 ok 0 Jan 2 19:21:29 Tower preclear_disk-diff[1897]: Temperature_Celsius = 125 129 0 ok 25 Jan 2 19:21:29 Tower preclear_disk-diff[1897]: No SMART attributes are FAILING_NOW Jan 2 19:21:29 Tower preclear_disk-diff[1897]: Jan 2 19:21:29 Tower preclear_disk-diff[1897]: 0 sectors were pending re-allocation before the start of the preclear. Jan 2 19:21:29 Tower preclear_disk-diff[1897]: 0 sectors were pending re-allocation after pre-read in cycle 1 of 1. Jan 2 19:21:29 Tower preclear_disk-diff[1897]: 0 sectors were pending re-allocation after zero of disk in cycle 1 of 1. Jan 2 19:21:29 Tower preclear_disk-diff[1897]: 0 sectors are pending re-allocation at the end of the preclear, Jan 2 19:21:29 Tower preclear_disk-diff[1897]: the number of sectors pending re-allocation did not change. Jan 2 19:21:29 Tower preclear_disk-diff[1897]: 0 sectors had been re-allocated before the start of the preclear. Jan 2 19:21:29 Tower preclear_disk-diff[1897]: 0 sectors are re-allocated at the end of the preclear, Jan 2 19:21:29 Tower preclear_disk-diff[1897]: the number of sectors re-allocated did not change. Jan 2 19:21:29 Tower preclear_disk-diff[1897]: ============================================================================ Jan 2 19:21:29 Tower preclear_disk-diff[1897]: ============================================================================ Jan 2 19:21:29 Tower preclear_disk-diff[1897]: == Jan 2 19:21:29 Tower preclear_disk-diff[1897]: == S.M.A.R.T Initial Report for /dev/sdd Jan 2 19:21:29 Tower preclear_disk-diff[1897]: == Jan 2 19:21:29 Tower preclear_disk-diff[1897]: Disk: /dev/sdd Jan 2 19:21:29 Tower preclear_disk-diff[1897]: smartctl 5.39.1 2010-01-28 r3054 [i486-slackware-linux-gnu] (local build) Jan 2 19:21:29 Tower preclear_disk-diff[1897]: Copyright © 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net Jan 2 19:21:29 Tower preclear_disk-diff[1897]: Jan 2 19:21:29 Tower preclear_disk-diff[1897]: === START OF INFORMATION SECTION === Jan 2 19:21:29 Tower preclear_disk-diff[1897]: Device Model: WDC WD20EARS-00MVWB0 Jan 2 19:21:29 Tower preclear_disk-diff[1897]: Serial Number: WD-WCAZA6120287 Jan 2 19:21:29 Tower preclear_disk-diff[1897]: Firmware Version: 51.0AB51 Jan 2 19:21:29 Tower preclear_disk-diff[1897]: User Capacity: 2,000,398,934,016 bytes Jan 2 19:21:29 Tower preclear_disk-diff[1897]: Device is: Not in smartctl database [for details use: -P showall] Jan 2 19:21:29 Tower preclear_disk-diff[1897]: ATA Version is: 8 Jan 2 19:21:29 Tower preclear_disk-diff[1897]: ATA Standard is: Exact ATA specification draft version not indicated Jan 2 19:21:29 Tower preclear_disk-diff[1897]: Local Time is: Sun Jan 1 17:12:17 2012 CET Jan 2 19:21:29 Tower preclear_disk-diff[1897]: SMART support is: Available - device has SMART capability. Jan 2 19:21:29 Tower preclear_disk-diff[1897]: SMART support is: Enabled Quote Link to comment
joelones Posted January 4, 2012 Share Posted January 4, 2012 I'm still having a problem with the preclear (although, I only see one occurrence of this error so far). I'm not sure what to do anymore as I just got a replacement backplane! unraid 4.7 Norco-4020 supermicro:x8sif The preclear isn't finished bu this is what I see in the log Error: Jan 3 19:34:14 tonyunraid kernel: /usr/src/sas/trunk/mvsas_tgt/mv_sas.c 2069:port 1 ctrl sts=0x199800. (Drive related) Jan 3 19:34:14 tonyunraid kernel: /usr/src/sas/trunk/mvsas_tgt/mv_sas.c 2071:Port 1 irq sts = 0x1000000 (Drive related) Jan 3 19:34:14 tonyunraid kernel: /usr/src/sas/trunk/mvsas_tgt/mv_sas.c 2069:port 5 ctrl sts=0x199800. (Drive related) Jan 3 19:34:14 tonyunraid kernel: /usr/src/sas/trunk/mvsas_tgt/mv_sas.c 2071:Port 5 irq sts = 0x1000000 (Drive related) Jan 3 19:34:14 tonyunraid kernel: /usr/src/sas/trunk/mvsas_tgt/mv_sas.c 2069:port 1 ctrl sts=0x199800. (Drive related) Jan 3 19:34:14 tonyunraid kernel: /usr/src/sas/trunk/mvsas_tgt/mv_sas.c 2071:Port 1 irq sts = 0x1000000 (Drive related) Jan 3 19:34:14 tonyunraid kernel: ata7.00: exception Emask 0x10 SAct 0x0 SErr 0x280100 action 0x6 (Errors) Jan 3 19:34:14 tonyunraid kernel: ata7.00: BMDMA stat 0x26 (Drive related) Jan 3 19:34:14 tonyunraid kernel: ata7: SError: { UnrecovData 10B8B BadCRC } (Errors) Jan 3 19:34:14 tonyunraid kernel: ata7.00: failed command: READ DMA EXT (Minor Issues) Jan 3 19:34:14 tonyunraid kernel: ata7.00: cmd 25/00:00:08:9d:1c/00:01:3f:00:00/e0 tag 0 dma 131072 in (Drive related) Jan 3 19:34:14 tonyunraid kernel: res 51/84:f0:18:9d:1c/84:00:3f:00:00/e0 Emask 0x30 (host bus error) (Errors) Jan 3 19:34:14 tonyunraid kernel: ata7.00: status: { DRDY ERR } (Drive related) Jan 3 19:34:14 tonyunraid kernel: ata7.00: error: { ICRC ABRT } (Errors) Jan 3 19:34:14 tonyunraid kernel: ata7: hard resetting link (Minor Issues) Jan 3 19:34:15 tonyunraid kernel: ata7: SATA link up 3.0 Gbps (SStatus 123 SControl 300) (Drive related) Jan 3 19:34:15 tonyunraid kernel: ata7.00: configured for UDMA/133 (Drive related) Jan 3 19:34:15 tonyunraid kernel: ata7: EH complete (Drive related) Jan 3 20:47:55 tonyunraid sshd[2326]: syslogin_perform_logout: logout() returned an error (Errors) Jan 4 05:37:17 tonyunraid kernel: sdf: sdf1 (Drive related) Jan 4 05:37:27 tonyunraid kernel: udev: starting version 141 (System) Attached is the syslog. Any suggestions, please? syslog-2012-01-04.txt.zip Quote Link to comment
Joe L. Posted January 4, 2012 Share Posted January 4, 2012 CRC errors are usually cabling or power supply related. Also, make sure you are not bundling your data cables close to power cables. Quote Link to comment
RobJ Posted January 5, 2012 Share Posted January 5, 2012 I just received two Seagate ST2000DL003 2TB drives from Amazon. I have run two preclear cycles. One has passed both preclear cycles with no SMART failures; One has failed on both preclear cycles with a SMART seek_error_rate failure. Raw_Read_Error_Rate looks very high as well. The drive that "passed" also had high values for these parameters although not nearly as high as these. Of five drives I have precleared, this is the only one to show a failure and I have never seen a failure in any desktop drive so I am not sure how reliable the SMART reports are. What say ye; should I return this to Amazon? I assume this is a legitimate indication of a bad drive as the seek_error_rate values seems incredibly high. Here is the SMART report generated at the end of the preclear with some information redacted: SMART status Info for /dev/sdc smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) Copyright © 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Device Model: ST2000DL003-9VT166 Serial Number: 5YD6HZP5 Firmware Version: CC3C 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: ATA-8-ACS revision 4 Local Time is: Sun Jan 1 11:39:35 2012 MST 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: FAILED! Drive failure expected in less than 24 hours. SAVE ALL DATA. See vendor-specific Attribute list for failed Attributes. 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: ( 623) 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: (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 100 006 Pre-fail Always - 105386328 3 Spin_Up_Time 0x0003 092 092 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 9 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 028 026 030 Pre-fail Always FAILING_NOW 13464724458629 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 38 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 9 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 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 068 065 045 Old_age Always - 32 (Min/Max 28/35) 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 - 7 193 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 9 194 Temperature_Celsius 0x0022 032 040 000 Old_age Always - 32 (0 22 0 0) 195 Hardware_ECC_Recovered 0x001a 037 024 000 Old_age Always - 105386328 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 - 1 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 66468913872934 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 2469991065 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 4264727547 A SMART report comes directly from the internals of the drive itself, so if a drive says it is failing, I would believe it! I agree that there are many inconsistencies with SMART reports, but in general - they ARE reliable if interpreted correctly. The problem is in knowing which numbers are important and which aren't, and unfortunately that changes with each drive manufacturer. Most of the very large numbers can be completely ignored, especially if they are 'raw'. Any attributes with 'Old_age' in the flag column can be considered Informational. Those marked as 'Pre-fail' are the critical ones. In your case, the Seek_Error_Rate has dropped too low. The line could be interpreted to read as: Seek_Error_Rate has dropped to the 28 percentile (from VALUE column), and previously had even dropped to the 26 percentile (from WORST column), which is lower than the 30 percentile rating (from THRESHold column) that the engineers at the drive manufacturer have deemed the minimum reliability percentile, below which this drive should be considered FAILED. Except for that one attribute, the drive looks great, including the Raw_Read_Error_Rate. Currently, it has a VALUE of 116, which is somewhat higher than 100! Again, as has been said many times before, ignore that raw value. The main raw values that ARE meaningful are Reallocated_Sector_Ct, Power_On_Hours, Power_Cycle_Count, Reported_Uncorrect, Airflow_Temperature_Cel, Load_Cycle_Count, Temperature_Celsius, Current_Pending_Sector, Offline_Uncorrectable, and UDMA_CRC_Error_Count (but possibly others too). Quote Link to comment
RobJ Posted January 5, 2012 Share Posted January 5, 2012 In your case, the Seek_Error_Rate has dropped too low. The line could be interpreted to read as: Seek_Error_Rate has dropped to the 28 percentile (from VALUE column), and previously had even dropped to the 26 percentile (from WORST column), which is lower than the 30 percentile rating (from THRESHold column) that the engineers at the drive manufacturer have deemed the minimum reliability percentile, below which this drive should be considered FAILED. Just to add a clarification, because it may be confusing to some that a drive seems to be working fine, yet the SMART report says it has FAILED. Part of the idea behind the development of the SMART system is to try to alert users to imminent failure BEFORE it is too late to save data. When a drive indicates a SMART failure, it is trying to warn you that there is a very high probability of complete drive failure in the very near future. The drive may or may not be fully operational at this moment, but even more catastrophic failure is very possible very soon. If there is any important data on the drive, you should attempt to relocate it as soon as possible. Quote Link to comment
RobJ Posted January 5, 2012 Share Posted January 5, 2012 Just running this by the experts in case anything stands out as a concern, like the 2 items that say "near_thresh": root@Tower:/boot# screen ** Changed attributes in files: /tmp/smart_start_sdf /tmp/smart_finish_sdf ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 118 120 6 ok 168294896 Seek_Error_Rate = 60 100 30 ok 1063419 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 Airflow_Temperature_Cel = 72 75 45 ok 28 Temperature_Celsius = 28 25 0 ok 28 Hardware_ECC_Recovered = 37 30 0 ok 168294896 No SMART attributes are FAILING_NOW Everything is completely fine. As you can see above, the VALUE number for both attributes is 100 (and did not change), which is essentially perfect. What caused the 'near_thresh' flag is that the SMART engineers have set some rather odd Threshold values of 97 and 99, which are very close to 100. Apparently what is being monitored here has to be either almost perfect or it is considered a Fail. Nothing for us to worry about here though. Quote Link to comment
Hoopster Posted January 5, 2012 Share Posted January 5, 2012 In your case, the Seek_Error_Rate has dropped too low. The line could be interpreted to read as: Seek_Error_Rate has dropped to the 28 percentile (from VALUE column), and previously had even dropped to the 26 percentile (from WORST column), which is lower than the 30 percentile rating (from THRESHold column) that the engineers at the drive manufacturer have deemed the minimum reliability percentile, below which this drive should be considered FAILED. Just to add a clarification, because it may be confusing to some that a drive seems to be working fine, yet the SMART report says it has FAILED. Part of the idea behind the development of the SMART system is to try to alert users to imminent failure BEFORE it is too late to save data. When a drive indicates a SMART failure, it is trying to warn you that there is a very high probability of complete drive failure in the very near future. The drive may or may not be fully operational at this moment, but even more catastrophic failure is very possible very soon. If there is any important data on the drive, you should attempt to relocate it as soon as possible. OK, thanks for the detailed response, I really appreciate it. Since this is a brand new drive and is already in pre-fail, I will return it for a new one. Quote Link to comment
crankbearing Posted January 10, 2012 Share Posted January 10, 2012 Just finshed the first cycle pre-clear on a new wd 3TB EZRX 6Gb sata drive with no issues. The total process on my new Asus F1A75-V Pro with the new A6-3500 APU took 36 Hours. Here is the pre-clear report if there is anything you guys notice that I do not let me know please. I am running 5b14 as well. ========================================================================1.13 == invoked as: ./preclear_disk.sh /dev/sdb == WDC WD30EZRX-00MMMB0 WD-WCAWZ1395560 == Disk /dev/sdb has been successfully precleared == with a starting sector of 1 == Ran 1 cycle == == Using :Read block size = 8225280 Bytes == Last Cycle's Pre Read Time : 9:00:00 (92 MB/s) == Last Cycle's Zeroing time : 9:05:58 (91 MB/s) == Last Cycle's Post Read Time : 18:07:33 (45 MB/s) == Last Cycle's Total Time : 36:14:32 == == Total Elapsed Time 36:14:32 == == Disk Start Temperature: 28C == == Current Disk Temperature: 36C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdb /tmp/smart_finish_sdb ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Temperature_Celsius = 116 123 0 ok 36 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. ============================================================================ Here is the preclear finish report. Disk: /dev/sdb 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: WDC WD30EZRX-00MMMB0 Serial Number: WD-WCAWZ1395560 Firmware Version: 80.00A80 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: Exact ATA specification draft version not indicated Local Time is: Mon Jan 9 22:15:00 2012 EST 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: (0x80) Offline data collection activity was never started. 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: (49980) 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 200 200 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0027 176 176 021 Pre-fail Always - 8158 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 10 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 100 253 000 Old_age Always - 0 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 35 10 Spin_Retry_Count 0x0032 100 253 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 8 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 7 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 16 194 Temperature_Celsius 0x0022 116 110 000 Old_age Always - 36 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 100 253 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 100 253 000 Old_age Offline - 0 SMART Error Log Version: 1 No Errors Logged 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. Dave Quote Link to comment
Unqualified Spectator Posted January 10, 2012 Share Posted January 10, 2012 First Preclear result. Running Beta 5.0/14. Preclear.sh is latest AFAIK (downloaded 2 days ago). (2) WD15EARS Drives - Jumpered 7/8 - Preclears ran for SDA and SDC - Drives are new, but I've had them for a year. Excepts are: SDA Jan 7 17:04:17 Tower preclear_disk-diff[12218]: ========================================================================1.13 Jan 7 17:04:17 Tower preclear_disk-diff[12218]: == invoked as: ./preclear_disk.sh -A /dev/sda Jan 7 17:04:17 Tower preclear_disk-diff[12218]: == WDC WD15EARS-00MVWB0 WD-WMAZA2581122 Jan 7 17:04:17 Tower preclear_disk-diff[12218]: == Disk /dev/sda has been successfully precleared Jan 7 17:04:17 Tower preclear_disk-diff[12218]: == with a starting sector of 64 Jan 7 17:04:17 Tower preclear_disk-diff[12218]: == Ran 1 cycle Jan 7 17:04:17 Tower preclear_disk-diff[12218]: == Jan 7 17:04:17 Tower preclear_disk-diff[12218]: == Using :Read block size = 8225280 Bytes Jan 7 17:04:17 Tower preclear_disk-diff[12218]: == Last Cycle's Pre Read Time : 4:45:08 (87 MB/s) Jan 7 17:04:17 Tower preclear_disk-diff[12218]: == Last Cycle's Zeroing time : 5:51:22 (71 MB/s) Jan 7 17:04:17 Tower preclear_disk-diff[12218]: == Last Cycle's Post Read Time : 9:08:13 (45 MB/s) Jan 7 17:04:17 Tower preclear_disk-diff[12218]: == Last Cycle's Total Time : 19:45:43 Jan 7 17:04:17 Tower preclear_disk-diff[12218]: == Jan 7 17:04:17 Tower preclear_disk-diff[12218]: == Total Elapsed Time 19:45:43 Jan 7 17:04:17 Tower preclear_disk-diff[12218]: == Jan 7 17:04:17 Tower preclear_disk-diff[12218]: == Disk Start Temperature: 20C Jan 7 17:04:17 Tower preclear_disk-diff[12218]: == Jan 7 17:04:17 Tower preclear_disk-diff[12218]: == Current Disk Temperature: 25C, Jan 7 17:04:17 Tower preclear_disk-diff[12218]: == Jan 7 17:04:17 Tower preclear_disk-diff[12218]: ============================================================================ Jan 7 17:04:17 Tower preclear_disk-diff[12218]: ** Changed attributes in files: /tmp/smart_start_sda /tmp/smart_finish_sda Jan 7 17:04:17 Tower preclear_disk-diff[12218]: ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Jan 7 17:04:17 Tower preclear_disk-diff[12218]: Temperature_Celsius = 125 130 0 ok 25 Jan 7 17:04:17 Tower preclear_disk-diff[12218]: No SMART attributes are FAILING_NOW Jan 7 17:04:17 Tower preclear_disk-diff[12218]: Jan 7 17:04:17 Tower preclear_disk-diff[12218]: 0 sectors were pending re-allocation before the start of the preclear. Jan 7 17:04:17 Tower preclear_disk-diff[12218]: 0 sectors were pending re-allocation after pre-read in cycle 1 of 1. Jan 7 17:04:17 Tower preclear_disk-diff[12218]: 0 sectors were pending re-allocation after zero of disk in cycle 1 of 1. Jan 7 17:04:17 Tower preclear_disk-diff[12218]: 0 sectors are pending re-allocation at the end of the preclear, Jan 7 17:04:17 Tower preclear_disk-diff[12218]: the number of sectors pending re-allocation did not change. Jan 7 17:04:17 Tower preclear_disk-diff[12218]: 0 sectors had been re-allocated before the start of the preclear. Jan 7 17:04:17 Tower preclear_disk-diff[12218]: 0 sectors are re-allocated at the end of the preclear, Jan 7 17:04:17 Tower preclear_disk-diff[12218]: the number of sectors re-allocated did not change. Jan 7 17:04:17 Tower preclear_disk-diff[12218]: ============================================================================ SDC Jan 9 02:38:10 Tower preclear_disk-diff[28147]: ========================================================================1.13 Jan 9 02:38:10 Tower preclear_disk-diff[28147]: == invoked as: ./preclear_disk.sh -A /dev/sdc Jan 9 02:38:10 Tower preclear_disk-diff[28147]: == WDC WD15EARS-00MVWB0 WD-WMAZA2644094 Jan 9 02:38:10 Tower preclear_disk-diff[28147]: == Disk /dev/sdc has been successfully precleared Jan 9 02:38:10 Tower preclear_disk-diff[28147]: == with a starting sector of 64 Jan 9 02:38:10 Tower preclear_disk-diff[28147]: == Ran 1 cycle Jan 9 02:38:10 Tower preclear_disk-diff[28147]: == Jan 9 02:38:10 Tower preclear_disk-diff[28147]: == Using :Read block size = 8225280 Bytes Jan 9 02:38:10 Tower preclear_disk-diff[28147]: == Last Cycle's Pre Read Time : 6:44:40 (61 MB/s) Jan 9 02:38:10 Tower preclear_disk-diff[28147]: == Last Cycle's Zeroing time : 7:27:40 (55 MB/s) Jan 9 02:38:10 Tower preclear_disk-diff[28147]: == Last Cycle's Post Read Time : 12:59:10 (32 MB/s) Jan 9 02:38:10 Tower preclear_disk-diff[28147]: == Last Cycle's Total Time : 27:12:30 Jan 9 02:38:10 Tower preclear_disk-diff[28147]: == Jan 9 02:38:10 Tower preclear_disk-diff[28147]: == Total Elapsed Time 27:12:30 Jan 9 02:38:10 Tower preclear_disk-diff[28147]: == Jan 9 02:38:10 Tower preclear_disk-diff[28147]: == Disk Start Temperature: 23C Jan 9 02:38:10 Tower preclear_disk-diff[28147]: == Jan 9 02:38:10 Tower preclear_disk-diff[28147]: == Current Disk Temperature: 24C, Jan 9 02:38:10 Tower preclear_disk-diff[28147]: == Jan 9 02:38:10 Tower preclear_disk-diff[28147]: ============================================================================ Jan 9 02:38:10 Tower preclear_disk-diff[28147]: ** Changed attributes in files: /tmp/smart_start_sdc /tmp/smart_finish_sdc Jan 9 02:38:10 Tower preclear_disk-diff[28147]: ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Jan 9 02:38:10 Tower preclear_disk-diff[28147]: Seek_Error_Rate = 100 200 0 ok 0 Jan 9 02:38:10 Tower preclear_disk-diff[28147]: Temperature_Celsius = 126 127 0 ok 24 Jan 9 02:38:10 Tower preclear_disk-diff[28147]: No SMART attributes are FAILING_NOW Jan 9 02:38:10 Tower preclear_disk-diff[28147]: Jan 9 02:38:10 Tower preclear_disk-diff[28147]: 0 sectors were pending re-allocation before the start of the preclear. Jan 9 02:38:10 Tower preclear_disk-diff[28147]: 0 sectors were pending re-allocation after pre-read in cycle 1 of 1. Jan 9 02:38:10 Tower preclear_disk-diff[28147]: 0 sectors were pending re-allocation after zero of disk in cycle 1 of 1. Jan 9 02:38:10 Tower preclear_disk-diff[28147]: 0 sectors are pending re-allocation at the end of the preclear, Jan 9 02:38:10 Tower preclear_disk-diff[28147]: the number of sectors pending re-allocation did not change. Jan 9 02:38:10 Tower preclear_disk-diff[28147]: 0 sectors had been re-allocated before the start of the preclear. Jan 9 02:38:10 Tower preclear_disk-diff[28147]: 0 sectors are re-allocated at the end of the preclear, Jan 9 02:38:10 Tower preclear_disk-diff[28147]: the number of sectors re-allocated did not change. Jan 9 02:38:10 Tower preclear_disk-diff[28147]: ============================================================================ Are these good results? I noticed that the SDC drive published a "SEEK ERROR RATE" line that SDA did not. The SDC drive is operating a good deal slower than SDA - is that a concern? Are these "CYCLE TIME" numbers typical for the EARS Green drives? Sorry for so many questions...I've been reading and searching for a few hours and I just didn't have any feel for "are these good baseline results" and my build is new so I am suspicious of anything out of the ordinary. I realize that I probably need to run the drives for 2-3 more passes each minimum to verify they have no issues before I integrate them into the array and they get formatted for the first time. Thanks in advance for such an incredible tool! Waay better than the "Fire it up and take our chances approach"! Quote Link to comment
crankbearing Posted January 10, 2012 Share Posted January 10, 2012 WOW what a fun night. So I installed my other two new WD 3.0TB EZRX and 2 1yr old NEW 2.0TB EARS and a new 7K2000 (RUNS HOT 40C in no time)) Hitachi and started a preclear on the works. No jumpers on any wd. These are on the boards I/O so I set to ACHI and max speed to sata 6GB/s and the 3.0TB are that. About three in the morning wife wakes me up says she heard a bang could not figure it out. One 3TB stopped reading with an I/O failure and filled my syslog with that error. The second 3TB was not spinning stopped at 50% into the pre-read. I tried spinning it up it worked for about 10 seconds and myMain indicated it had stopped again. Stopped the preclear (and it was writing zero's to the other drives already - UGH1) on all the other drives and shutdown (10 Minutes to save the syslog). I changed the sata6 cables to those two drives and rebooted board would not detect one of the 3TB and I was not taking a chance on the other. I just got them yesterday so I hope I can replace them at the store instead of with WD. Glad they were on sale for 188CDN each. I am glad this is just in testing stage. rgds, Dave Quote Link to comment
theprophe Posted January 18, 2012 Share Posted January 18, 2012 Hi, first time using preclear, i stuck in 3 drives and went to preclear, using screen through telnet,my laptop crashed and when i telneted back in i tried screen-r and got the following there are several suitable screens on: 3738.pts-4.tower (detached) 4388.pts-0.tower (detached) type "screen [-d] -r [pid.]tty.host" to resume one of them not sure what to do, its a fresh unraid, only these 3 disks are in itm and should i have 3 things shown? (i can see my 3 drives are still active) Quote Link to comment
glave Posted January 20, 2012 Share Posted January 20, 2012 I just rebooted my desktop and lost my telnet connection to the server while preclear was still running. Unmenu shows it's still running and 50% thru the post read, and I know I can't reconnect to that telnet session. Is there someway to see the results once it completes? Does it write to any log file somewhere? Quote Link to comment
wsume99 Posted January 20, 2012 Share Posted January 20, 2012 You will be able to see the raw results of the SMART tests in your syslog. All you really need to do is check to see if you have any change in the pending or reallocated sectors count. If you do then you'll need to decide if you want to run more preclears or RMA the drive. Quote Link to comment
Joe L. Posted January 26, 2012 Share Posted January 26, 2012 I just rebooted my desktop and lost my telnet connection to the server while preclear was still running. Unmenu shows it's still running and 50% thru the post read, and I know I can't reconnect to that telnet session. Is there someway to see the results once it completes? Does it write to any log file somewhere? Unless you ran it under "screen", it was terminated when you lost the telnet session. The unMENU MyMain screen only shows the progress it had when the progress file kept for that purpose was last updated. (In other words, don't expect the 50% to advance to 51%, as the file will never be updated.) Quote Link to comment
loady Posted January 30, 2012 Share Posted January 30, 2012 not sure if this is a bad sign...in short.. ========================================================================1.13 == invoked as: ./preclear_disk.sh -M 4 /dev/sdb == == Disk /dev/sdb has NOT been successfully precleared == Postread detected un-expected non-zero bytes on disk== == Ran 1 cycle == == Using :Read block size = 8225280 Bytes == Last Cycle's Pre Read Time : 6:32:11 (85 MB/s) == Last Cycle's Zeroing time : 5:43:22 (97 MB/s) == Last Cycle's Post Read Time : 14:02:46 (39 MB/s) == Last Cycle's Total Time : 26:19:30 == == Total Elapsed Time 26:19:31 == == Disk Start Temperature: 26C == == Current Disk Temperature: 25C, == ============================================================================ No SMART attributes are FAILING_NOW Quote Link to comment
Joe L. Posted January 30, 2012 Share Posted January 30, 2012 not sure if this is a bad sign...in short.. ========================================================================1.13 == invoked as: ./preclear_disk.sh -M 4 /dev/sdb == == Disk /dev/sdb has NOT been successfully precleared == Postread detected un-expected non-zero bytes on disk== == Ran 1 cycle == == Using :Read block size = 8225280 Bytes == Last Cycle's Pre Read Time : 6:32:11 (85 MB/s) == Last Cycle's Zeroing time : 5:43:22 (97 MB/s) == Last Cycle's Post Read Time : 14:02:46 (39 MB/s) == Last Cycle's Total Time : 26:19:30 == == Total Elapsed Time 26:19:31 == == Disk Start Temperature: 26C == == Current Disk Temperature: 25C, == ============================================================================ No SMART attributes are FAILING_NOW It is not a good sign. It does save you from possibly pulling out your hair in attempting to find elusive random parity errors. the preclear wrote a block of zeros. When it read them back, they were not all zeros. You can look in the syslog, but we've seen many cases where no other errors are reported. Typically, with MS-Windows, we would blame Microsoft, but in this case, it is bad hardware... The same symptoms could also be caused by bad RAM, so I'd suggest a memory test, preferably overnight before condemning the disk, and then trying it on a different port on the disk controller, is it also could be the cause. I see another preclear cycle in your future. Quote Link to comment
loady Posted January 30, 2012 Share Posted January 30, 2012 Hmmm.. i dont suspect the memory, i have done no less than 5 preclears straight on different drives and all have passed, i am going to stick in 8gb shortly anyway, whats the best way to test the memory, do i need to add a monitor and boot server and wait for option to run mem test or can i invoke it via telnet session ? Quote Link to comment
Joe L. Posted January 30, 2012 Share Posted January 30, 2012 Hmmm.. i dont suspect the memory, i have done no less than 5 preclears straight on different drives and all have passed, i am going to stick in 8gb shortly anyway, whats the best way to test the memory, do i need to add a monitor and boot server and wait for option to run mem test or can i invoke it via telnet session ? You must do it from the system console. It is a choice on the boot menu. (cannot do it from telnet) From what you said, odds are it is the disk. Quote Link to comment
madburg Posted February 1, 2012 Share Posted February 1, 2012 87 pages and counting, we all have to chip in and purchase a crown for the man by the time this reaches the 100th page. Joe you should come up with a logo for preclear by then To be incorporated into future plug-ins 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.