Joe L. Posted February 4, 2010 Share Posted February 4, 2010 Hey folks, Just precleared an older Seagate 1TB drive. Tried to interpret these numbers, but I'm having trouble making heads or tails of them... < 1 Raw_Read_Error_Rate 0x000f 117 099 006 Pre-fail Always - 147540226 --- > 1 Raw_Read_Error_Rate 0x000f 108 099 006 Pre-fail Always - 16402173 59c59 < 7 Seek_Error_Rate 0x000f 060 056 030 Pre-fail Always - 231985297980 --- > 7 Seek_Error_Rate 0x000f 060 056 030 Pre-fail Always - 236280364147 65,67c65,67 < 189 High_Fly_Writes 0x003a 099 099 000 Old_age Always - 1 < 190 Airflow_Temperature_Cel 0x0022 075 053 045 Old_age Always - 25 (Lifetime Min/Max 23/25) < 195 Hardware_ECC_Recovered 0x001a 039 019 000 Old_age Always --- > 189 High_Fly_Writes 0x003a 098 098 000 Old_age Always - 2 > 190 Airflow_Temperature_Cel 0x0022 075 053 045 Old_age Always - 25 (Lifetime Min/Max 23/26) > 195 Hardware_ECC_Recovered 0x001a 050 019 000 Old_age Always Thanks for any advice! these numbers represent the differences between the SMART report before the pre-clear cycle and after. The disk could have a parameter that is FAILING before, and equally FAILING after, and if the parameters involved did not change their counts, would not show in the "diff" report. with that in mind, it is highly unlikely, and still be able to clear a drive, but it could happen. as far as the various numbers, you need to only worry about a few parameters... those representing sectors marked for re-allocation, and those already re-allocated. Other than those two, unless a parameter shows "FAILED" or "FAILING_NOW" where the "-" on your printout of the "diff" exists, you are OK. The current "normalized" read error rate is 108, prior to the preclear, it was 117. The worst ever measured over the lifetime of the drive was "99" The failure threshold is "006" If the normalized read error rate goes BELOW "006" then the drive is considered to be failing. All drives have internal read errors. They are all designed to re-read on an error. As long as the normalized error rate is above the threshold, you are fine. Nobody except the manufacturer knows how to interpret the "raw" values in the right-most column (and they don't tell anybody) The same goes for your "seek error rate" The threshold is "030" the current value (both pre and post) is "060" and the worst value ever "056." the raw values are again only meaningful to the manufacturer. The "high fly writes" seem to have incremented by 1 in the raw value... again, the normalized value of "099" is nowhere near the failure threshold of "000" About the only parameter that has a raw value that is understandable is the temperature. Apparently, during the pre-clear process the drive reached a new "max" temperature of 26C. Enjoy your new drive... I know the pre-clear script needs to be better in explaining the output, but when I wrote it I figured the difference were most interesting. Turns out most are not very useful at all unless you detect a rapid trend towards the "normalized" failure threshold. Joe L. Quote Link to comment
abeta Posted February 14, 2010 Share Posted February 14, 2010 Based on the previous post, it would sound like this diff is ok then? Feb 14 05:26:19 Tower preclear_disk-diff[6184]: S.M.A.R.T. error count differences detected after pre-clear Feb 14 05:26:19 Tower preclear_disk-diff[6184]: note, some 'raw' values may change, but not be an indication of a problem Feb 14 05:26:19 Tower preclear_disk-diff[6184]: 54c54 Feb 14 05:26:19 Tower preclear_disk-diff[6184]: < 1 Raw_Read_Error_Rate 0x000f 111 099 006 Pre-fail Always - 40394155 Feb 14 05:26:19 Tower preclear_disk-diff[6184]: --- Feb 14 05:26:19 Tower preclear_disk-diff[6184]: > 1 Raw_Read_Error_Rate 0x000f 119 099 006 Pre-fail Always - 206494492 Feb 14 05:26:19 Tower preclear_disk-diff[6184]: 58c58 Feb 14 05:26:19 Tower preclear_disk-diff[6184]: < 7 Seek_Error_Rate 0x000f 062 060 030 Pre-fail Always - 1670756 Feb 14 05:26:19 Tower preclear_disk-diff[6184]: --- Feb 14 05:26:19 Tower preclear_disk-diff[6184]: > 7 Seek_Error_Rate 0x000f 062 060 030 Pre-fail Always - 1760524 Feb 14 05:26:19 Tower preclear_disk-diff[6184]: 64,66c64,66 Feb 14 05:26:19 Tower preclear_disk-diff[6184]: < 189 High_Fly_Writes 0x003a 001 001 000 Old_age Always - 423 Feb 14 05:26:19 Tower preclear_disk-diff[6184]: < 190 Airflow_Temperature_Cel 0x0022 067 050 045 Old_age Always - 33 (Lifetime Min/Max 31/34) Feb 14 05:26:19 Tower preclear_disk-diff[6184]: < 195 Hardware_ECC_Recovered 0x001a 051 025 000 Old_age Always Feb 14 05:26:19 Tower preclear_disk-diff[6184]: --- Feb 14 05:26:19 Tower preclear_disk-diff[6184]: > 189 High_Fly_Writes 0x003a 001 001 000 Old_age Always - 457 Feb 14 05:26:19 Tower preclear_disk-diff[6184]: > 190 Airflow_Temperature_Cel 0x0022 062 050 045 Old_age Always - 38 (Lifetime Min/Max 31/39) Feb 14 05:26:19 Tower preclear_disk-diff[6184]: > 195 Hardware_ECC_Recovered 0x001a 056 025 000 Old_age Always Feb 14 05:26:19 Tower preclear_disk-diff[6184]: ============================================================================ Feb 14 05:26:19 Tower preclear_disk-diff[6184]: Quote Link to comment
Joe L. Posted February 14, 2010 Share Posted February 14, 2010 Based on the previous post, it would sound like this diff is ok then? Feb 14 05:26:19 Tower preclear_disk-diff[6184]: S.M.A.R.T. error count differences detected after pre-clear Feb 14 05:26:19 Tower preclear_disk-diff[6184]: note, some 'raw' values may change, but not be an indication of a problem Feb 14 05:26:19 Tower preclear_disk-diff[6184]: 54c54 Feb 14 05:26:19 Tower preclear_disk-diff[6184]: < 1 Raw_Read_Error_Rate 0x000f 111 099 006 Pre-fail Always - 40394155 Feb 14 05:26:19 Tower preclear_disk-diff[6184]: --- Feb 14 05:26:19 Tower preclear_disk-diff[6184]: > 1 Raw_Read_Error_Rate 0x000f 119 099 006 Pre-fail Always - 206494492 Feb 14 05:26:19 Tower preclear_disk-diff[6184]: 58c58 Feb 14 05:26:19 Tower preclear_disk-diff[6184]: < 7 Seek_Error_Rate 0x000f 062 060 030 Pre-fail Always - 1670756 Feb 14 05:26:19 Tower preclear_disk-diff[6184]: --- Feb 14 05:26:19 Tower preclear_disk-diff[6184]: > 7 Seek_Error_Rate 0x000f 062 060 030 Pre-fail Always - 1760524 Feb 14 05:26:19 Tower preclear_disk-diff[6184]: 64,66c64,66 Feb 14 05:26:19 Tower preclear_disk-diff[6184]: < 189 High_Fly_Writes 0x003a 001 001 000 Old_age Always - 423 Feb 14 05:26:19 Tower preclear_disk-diff[6184]: < 190 Airflow_Temperature_Cel 0x0022 067 050 045 Old_age Always - 33 (Lifetime Min/Max 31/34) Feb 14 05:26:19 Tower preclear_disk-diff[6184]: < 195 Hardware_ECC_Recovered 0x001a 051 025 000 Old_age Always Feb 14 05:26:19 Tower preclear_disk-diff[6184]: --- Feb 14 05:26:19 Tower preclear_disk-diff[6184]: > 189 High_Fly_Writes 0x003a 001 001 000 Old_age Always - 457 Feb 14 05:26:19 Tower preclear_disk-diff[6184]: > 190 Airflow_Temperature_Cel 0x0022 062 050 045 Old_age Always - 38 (Lifetime Min/Max 31/39) Feb 14 05:26:19 Tower preclear_disk-diff[6184]: > 195 Hardware_ECC_Recovered 0x001a 056 025 000 Old_age Always Feb 14 05:26:19 Tower preclear_disk-diff[6184]: ============================================================================ Feb 14 05:26:19 Tower preclear_disk-diff[6184]: Exactly. But you should look at the full smart report to be absolutely certain. They were logged in your syslog. Enjoy your new disk drive. Quote Link to comment
abeta Posted February 14, 2010 Share Posted February 14, 2010 Just for my education. Am I looking for the same things in the full report here or something else? Feb 14 05:26:19 Tower preclear_disk-finish[6171]: smartctl version 5.38 [i486-slackware-linux-gnu] Copyright (C) 2002-8 Bruce Allen Feb 14 05:26:19 Tower preclear_disk-finish[6171]: Home page is http://smartmontools.sourceforge.net/ Feb 14 05:26:19 Tower preclear_disk-finish[6171]: Feb 14 05:26:19 Tower preclear_disk-finish[6171]: === START OF INFORMATION SECTION === Feb 14 05:26:19 Tower preclear_disk-finish[6171]: Device Model: ST31500341AS Feb 14 05:26:19 Tower preclear_disk-finish[6171]: Serial Number: 9VS07SZG Feb 14 05:26:19 Tower preclear_disk-finish[6171]: Firmware Version: SD1B Feb 14 05:26:19 Tower preclear_disk-finish[6171]: User Capacity: 1,500,301,910,016 bytes Feb 14 05:26:19 Tower preclear_disk-finish[6171]: Device is: Not in smartctl database [for details use: -P showall] Feb 14 05:26:19 Tower preclear_disk-finish[6171]: ATA Version is: 8 Feb 14 05:26:19 Tower preclear_disk-finish[6171]: ATA Standard is: ATA-8-ACS revision 4 Feb 14 05:26:19 Tower preclear_disk-finish[6171]: Local Time is: Sun Feb 14 05:26:19 2010 GMT+5 Feb 14 05:26:19 Tower preclear_disk-finish[6171]: SMART support is: Available - device has SMART capability. Feb 14 05:26:19 Tower preclear_disk-finish[6171]: SMART support is: Enabled Feb 14 05:26:19 Tower preclear_disk-finish[6171]: Feb 14 05:26:19 Tower preclear_disk-finish[6171]: === START OF READ SMART DATA SECTION === Feb 14 05:26:19 Tower preclear_disk-finish[6171]: SMART overall-health self-assessment test result: PASSED Feb 14 05:26:19 Tower preclear_disk-finish[6171]: Feb 14 05:26:19 Tower preclear_disk-finish[6171]: General SMART Values: Feb 14 05:26:19 Tower preclear_disk-finish[6171]: Offline data collection status: (0x82)^IOffline data collection activity Feb 14 05:26:19 Tower preclear_disk-finish[6171]: ^I^I^I^I^Iwas completed without error. Feb 14 05:26:19 Tower preclear_disk-finish[6171]: ^I^I^I^I^IAuto Offline Data Collection: Enabled. Feb 14 05:26:19 Tower preclear_disk-finish[6171]: Self-test execution status: ( 0)^IThe previous self-test routine completed Feb 14 05:26:19 Tower preclear_disk-finish[6171]: ^I^I^I^I^Iwithout error or no self-test has ever Feb 14 05:26:19 Tower preclear_disk-finish[6171]: ^I^I^I^I^Ibeen run. Feb 14 05:26:19 Tower preclear_disk-finish[6171]: Total time to complete Offline Feb 14 05:26:19 Tower preclear_disk-finish[6171]: data collection: ^I^I ( 609) seconds. Feb 14 05:26:19 Tower preclear_disk-finish[6171]: Offline data collection Feb 14 05:26:19 Tower preclear_disk-finish[6171]: capabilities: ^I^I^I (0x7b) SMART execute Offline immediate. Feb 14 05:26:19 Tower preclear_disk-finish[6171]: ^I^I^I^I^IAuto Offline data collection on/off support. Feb 14 05:26:19 Tower preclear_disk-finish[6171]: ^I^I^I^I^ISuspend Offline collection upon new Feb 14 05:26:19 Tower preclear_disk-finish[6171]: ^I^I^I^I^Icommand. Feb 14 05:26:19 Tower preclear_disk-finish[6171]: ^I^I^I^I^IOffline surface scan supported. Feb 14 05:26:19 Tower preclear_disk-finish[6171]: ^I^I^I^I^ISelf-test supported. Feb 14 05:26:19 Tower preclear_disk-finish[6171]: ^I^I^I^I^IConveyance Self-test supported. Feb 14 05:26:19 Tower preclear_disk-finish[6171]: ^I^I^I^I^ISelective Self-test supported. Feb 14 05:26:19 Tower preclear_disk-finish[6171]: SMART capabilities: (0x0003)^ISaves SMART data before entering Feb 14 05:26:19 Tower preclear_disk-finish[6171]: ^I^I^I^I^Ipower-saving mode. Feb 14 05:26:19 Tower preclear_disk-finish[6171]: ^I^I^I^I^ISupports SMART auto save timer. Feb 14 05:26:19 Tower preclear_disk-finish[6171]: Error logging capability: (0x01)^IError logging supported. Feb 14 05:26:19 Tower preclear_disk-finish[6171]: ^I^I^I^I^IGeneral Purpose Logging supported. Feb 14 05:26:19 Tower preclear_disk-finish[6171]: Short self-test routine Feb 14 05:26:19 Tower preclear_disk-finish[6171]: recommended polling time: ^I ( 1) minutes. Feb 14 05:26:19 Tower preclear_disk-finish[6171]: Extended self-test routine Feb 14 05:26:19 Tower preclear_disk-finish[6171]: recommended polling time: ^I ( 255) minutes. Feb 14 05:26:19 Tower preclear_disk-finish[6171]: Conveyance self-test routine Feb 14 05:26:19 Tower preclear_disk-finish[6171]: recommended polling time: ^I ( 2) minutes. Feb 14 05:26:19 Tower preclear_disk-finish[6171]: SCT capabilities: ^I (0x103b)^ISCT Status supported. Feb 14 05:26:19 Tower preclear_disk-finish[6171]: ^I^I^I^I^ISCT Feature Control supported. Feb 14 05:26:19 Tower preclear_disk-finish[6171]: ^I^I^I^I^ISCT Data Table supported. Feb 14 05:26:19 Tower preclear_disk-finish[6171]: Feb 14 05:26:19 Tower preclear_disk-finish[6171]: SMART Attributes Data Structure revision number: 10 Feb 14 05:26:19 Tower preclear_disk-finish[6171]: Vendor Specific SMART Attributes with Thresholds: Feb 14 05:26:19 Tower preclear_disk-finish[6171]: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE Feb 14 05:26:19 Tower preclear_disk-finish[6171]: 1 Raw_Read_Error_Rate 0x000f 119 099 006 Pre-fail Always - 206494492 Feb 14 05:26:19 Tower preclear_disk-finish[6171]: 3 Spin_Up_Time 0x0003 093 092 000 Pre-fail Always - 0 Feb 14 05:26:19 Tower preclear_disk-finish[6171]: 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 54 Feb 14 05:26:19 Tower preclear_disk-finish[6171]: 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 19 Feb 14 05:26:19 Tower preclear_disk-finish[6171]: 7 Seek_Error_Rate 0x000f 062 060 030 Pre-fail Always - 1760524 Feb 14 05:26:19 Tower preclear_disk-finish[6171]: 9 Power_On_Hours 0x0032 088 088 000 Old_age Always - 10572 Feb 14 05:26:19 Tower preclear_disk-finish[6171]: 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 Feb 14 05:26:19 Tower preclear_disk-finish[6171]: 12 Power_Cycle_Count 0x0032 100 037 020 Old_age Always - 107 Feb 14 05:26:19 Tower preclear_disk-finish[6171]: 184 Unknown_Attribute 0x0032 100 100 099 Old_age Always - 0 Feb 14 05:26:19 Tower preclear_disk-finish[6171]: 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 Feb 14 05:26:19 Tower preclear_disk-finish[6171]: 188 Unknown_Attribute 0x0032 100 098 000 Old_age Always - 30065229831 Feb 14 05:26:19 Tower preclear_disk-finish[6171]: 189 High_Fly_Writes 0x003a 001 001 000 Old_age Always - 457 Feb 14 05:26:19 Tower preclear_disk-finish[6171]: 190 Airflow_Temperature_Cel 0x0022 062 050 045 Old_age Always - 38 (Lifetime Min/Max 31/39) Feb 14 05:26:19 Tower preclear_disk-finish[6171]: 195 Hardware_ECC_Recovered 0x001a 056 025 000 Old_age Always - 206494492 Feb 14 05:26:19 Tower preclear_disk-finish[6171]: 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 Feb 14 05:26:19 Tower preclear_disk-finish[6171]: 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 Feb 14 05:26:19 Tower preclear_disk-finish[6171]: 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 Feb 14 05:26:19 Tower preclear_disk-finish[6171]: Feb 14 05:26:19 Tower preclear_disk-finish[6171]: SMART Error Log Version: 1 Feb 14 05:26:19 Tower preclear_disk-finish[6171]: No Errors Logged Feb 14 05:26:19 Tower preclear_disk-finish[6171]: Feb 14 05:26:19 Tower preclear_disk-finish[6171]: SMART Self-test log structure revision number 1 Feb 14 05:26:19 Tower preclear_disk-finish[6171]: Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error Feb 14 05:26:19 Tower preclear_disk-finish[6171]: # 1 Short offline Completed without error 00% 10553 - Feb 14 05:26:19 Tower preclear_disk-finish[6171]: # 2 Short offline Completed without error 00% 10456 - Feb 14 05:26:19 Tower preclear_disk-finish[6171]: Feb 14 05:26:19 Tower preclear_disk-finish[6171]: SMART Selective self-test log data structure revision number 1 Feb 14 05:26:19 Tower preclear_disk-finish[6171]: SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS Feb 14 05:26:19 Tower preclear_disk-finish[6171]: 1 0 0 Not_testing Feb 14 05:26:19 Tower preclear_disk-finish[6171]: 2 0 0 Not_testing Feb 14 05:26:19 Tower preclear_disk-finish[6171]: 3 0 0 Not_testing Feb 14 05:26:19 Tower preclear_disk-finish[6171]: 4 0 0 Not_testing Feb 14 05:26:19 Tower preclear_disk-finish[6171]: 5 0 0 Not_testing Feb 14 05:26:19 Tower preclear_disk-finish[6171]: Selective self-test flags (0x0): Feb 14 05:26:19 Tower preclear_disk-finish[6171]: After scanning selected spans, do NOT read-scan remainder of disk. Feb 14 05:26:19 Tower preclear_disk-finish[6171]: If Selective self-test is pending on power-up, resume after 0 minute delay. Feb 14 05:26:19 Tower preclear_disk-finish[6171]: Feb 14 05:26:19 Tower preclear_disk-diff[6184]: Quote Link to comment
Joe L. Posted February 14, 2010 Share Posted February 14, 2010 Just for my education. Am I looking for the same things in the full report here or something else? Feb 14 05:26:19 Tower preclear_disk-finish[6171]: smartctl version 5.38 [i486-slackware-linux-gnu] Copyright (C) 2002-8 Bruce Allen Feb 14 05:26:19 Tower preclear_disk-finish[6171]: Home page is http://smartmontools.sourceforge.net/ Feb 14 05:26:19 Tower preclear_disk-finish[6171]: Feb 14 05:26:19 Tower preclear_disk-finish[6171]: === START OF INFORMATION SECTION === Feb 14 05:26:19 Tower preclear_disk-finish[6171]: Device Model: ST31500341AS Feb 14 05:26:19 Tower preclear_disk-finish[6171]: Serial Number: 9VS07SZG Feb 14 05:26:19 Tower preclear_disk-finish[6171]: Firmware Version: SD1B Feb 14 05:26:19 Tower preclear_disk-finish[6171]: User Capacity: 1,500,301,910,016 bytes Feb 14 05:26:19 Tower preclear_disk-finish[6171]: Device is: Not in smartctl database [for details use: -P showall] Feb 14 05:26:19 Tower preclear_disk-finish[6171]: ATA Version is: 8 Feb 14 05:26:19 Tower preclear_disk-finish[6171]: ATA Standard is: ATA-8-ACS revision 4 Feb 14 05:26:19 Tower preclear_disk-finish[6171]: Local Time is: Sun Feb 14 05:26:19 2010 GMT+5 Feb 14 05:26:19 Tower preclear_disk-finish[6171]: SMART support is: Available - device has SMART capability. Feb 14 05:26:19 Tower preclear_disk-finish[6171]: SMART support is: Enabled Feb 14 05:26:19 Tower preclear_disk-finish[6171]: Feb 14 05:26:19 Tower preclear_disk-finish[6171]: === START OF READ SMART DATA SECTION === Feb 14 05:26:19 Tower preclear_disk-finish[6171]: SMART overall-health self-assessment test result: PASSED Feb 14 05:26:19 Tower preclear_disk-finish[6171]: Feb 14 05:26:19 Tower preclear_disk-finish[6171]: General SMART Values: Feb 14 05:26:19 Tower preclear_disk-finish[6171]: Offline data collection status: (0x82)^IOffline data collection activity Feb 14 05:26:19 Tower preclear_disk-finish[6171]: ^I^I^I^I^Iwas completed without error. Feb 14 05:26:19 Tower preclear_disk-finish[6171]: ^I^I^I^I^IAuto Offline Data Collection: Enabled. Feb 14 05:26:19 Tower preclear_disk-finish[6171]: Self-test execution status: ( 0)^IThe previous self-test routine completed Feb 14 05:26:19 Tower preclear_disk-finish[6171]: ^I^I^I^I^Iwithout error or no self-test has ever Feb 14 05:26:19 Tower preclear_disk-finish[6171]: ^I^I^I^I^Ibeen run. Feb 14 05:26:19 Tower preclear_disk-finish[6171]: Total time to complete Offline Feb 14 05:26:19 Tower preclear_disk-finish[6171]: data collection: ^I^I ( 609) seconds. Feb 14 05:26:19 Tower preclear_disk-finish[6171]: Offline data collection Feb 14 05:26:19 Tower preclear_disk-finish[6171]: capabilities: ^I^I^I (0x7b) SMART execute Offline immediate. Feb 14 05:26:19 Tower preclear_disk-finish[6171]: ^I^I^I^I^IAuto Offline data collection on/off support. Feb 14 05:26:19 Tower preclear_disk-finish[6171]: ^I^I^I^I^ISuspend Offline collection upon new Feb 14 05:26:19 Tower preclear_disk-finish[6171]: ^I^I^I^I^Icommand. Feb 14 05:26:19 Tower preclear_disk-finish[6171]: ^I^I^I^I^IOffline surface scan supported. Feb 14 05:26:19 Tower preclear_disk-finish[6171]: ^I^I^I^I^ISelf-test supported. Feb 14 05:26:19 Tower preclear_disk-finish[6171]: ^I^I^I^I^IConveyance Self-test supported. Feb 14 05:26:19 Tower preclear_disk-finish[6171]: ^I^I^I^I^ISelective Self-test supported. Feb 14 05:26:19 Tower preclear_disk-finish[6171]: SMART capabilities: (0x0003)^ISaves SMART data before entering Feb 14 05:26:19 Tower preclear_disk-finish[6171]: ^I^I^I^I^Ipower-saving mode. Feb 14 05:26:19 Tower preclear_disk-finish[6171]: ^I^I^I^I^ISupports SMART auto save timer. Feb 14 05:26:19 Tower preclear_disk-finish[6171]: Error logging capability: (0x01)^IError logging supported. Feb 14 05:26:19 Tower preclear_disk-finish[6171]: ^I^I^I^I^IGeneral Purpose Logging supported. Feb 14 05:26:19 Tower preclear_disk-finish[6171]: Short self-test routine Feb 14 05:26:19 Tower preclear_disk-finish[6171]: recommended polling time: ^I ( 1) minutes. Feb 14 05:26:19 Tower preclear_disk-finish[6171]: Extended self-test routine Feb 14 05:26:19 Tower preclear_disk-finish[6171]: recommended polling time: ^I ( 255) minutes. Feb 14 05:26:19 Tower preclear_disk-finish[6171]: Conveyance self-test routine Feb 14 05:26:19 Tower preclear_disk-finish[6171]: recommended polling time: ^I ( 2) minutes. Feb 14 05:26:19 Tower preclear_disk-finish[6171]: SCT capabilities: ^I (0x103b)^ISCT Status supported. Feb 14 05:26:19 Tower preclear_disk-finish[6171]: ^I^I^I^I^ISCT Feature Control supported. Feb 14 05:26:19 Tower preclear_disk-finish[6171]: ^I^I^I^I^ISCT Data Table supported. Feb 14 05:26:19 Tower preclear_disk-finish[6171]: Feb 14 05:26:19 Tower preclear_disk-finish[6171]: SMART Attributes Data Structure revision number: 10 Feb 14 05:26:19 Tower preclear_disk-finish[6171]: Vendor Specific SMART Attributes with Thresholds: Feb 14 05:26:19 Tower preclear_disk-finish[6171]: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE Feb 14 05:26:19 Tower preclear_disk-finish[6171]: 1 Raw_Read_Error_Rate 0x000f 119 099 006 Pre-fail Always - 206494492 Feb 14 05:26:19 Tower preclear_disk-finish[6171]: 3 Spin_Up_Time 0x0003 093 092 000 Pre-fail Always - 0 Feb 14 05:26:19 Tower preclear_disk-finish[6171]: 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 54 Feb 14 05:26:19 Tower preclear_disk-finish[6171]: 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 19 Feb 14 05:26:19 Tower preclear_disk-finish[6171]: 7 Seek_Error_Rate 0x000f 062 060 030 Pre-fail Always - 1760524 Feb 14 05:26:19 Tower preclear_disk-finish[6171]: 9 Power_On_Hours 0x0032 088 088 000 Old_age Always - 10572 Feb 14 05:26:19 Tower preclear_disk-finish[6171]: 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 Feb 14 05:26:19 Tower preclear_disk-finish[6171]: 12 Power_Cycle_Count 0x0032 100 037 020 Old_age Always - 107 Feb 14 05:26:19 Tower preclear_disk-finish[6171]: 184 Unknown_Attribute 0x0032 100 100 099 Old_age Always - 0 Feb 14 05:26:19 Tower preclear_disk-finish[6171]: 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 Feb 14 05:26:19 Tower preclear_disk-finish[6171]: 188 Unknown_Attribute 0x0032 100 098 000 Old_age Always - 30065229831 Feb 14 05:26:19 Tower preclear_disk-finish[6171]: 189 High_Fly_Writes 0x003a 001 001 000 Old_age Always - 457 Feb 14 05:26:19 Tower preclear_disk-finish[6171]: 190 Airflow_Temperature_Cel 0x0022 062 050 045 Old_age Always - 38 (Lifetime Min/Max 31/39) Feb 14 05:26:19 Tower preclear_disk-finish[6171]: 195 Hardware_ECC_Recovered 0x001a 056 025 000 Old_age Always - 206494492 Feb 14 05:26:19 Tower preclear_disk-finish[6171]: 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 Feb 14 05:26:19 Tower preclear_disk-finish[6171]: 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 Feb 14 05:26:19 Tower preclear_disk-finish[6171]: 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 Feb 14 05:26:19 Tower preclear_disk-finish[6171]: Feb 14 05:26:19 Tower preclear_disk-finish[6171]: SMART Error Log Version: 1 Feb 14 05:26:19 Tower preclear_disk-finish[6171]: No Errors Logged Feb 14 05:26:19 Tower preclear_disk-finish[6171]: Feb 14 05:26:19 Tower preclear_disk-finish[6171]: SMART Self-test log structure revision number 1 Feb 14 05:26:19 Tower preclear_disk-finish[6171]: Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error Feb 14 05:26:19 Tower preclear_disk-finish[6171]: # 1 Short offline Completed without error 00% 10553 - Feb 14 05:26:19 Tower preclear_disk-finish[6171]: # 2 Short offline Completed without error 00% 10456 - Feb 14 05:26:19 Tower preclear_disk-finish[6171]: Feb 14 05:26:19 Tower preclear_disk-finish[6171]: SMART Selective self-test log data structure revision number 1 Feb 14 05:26:19 Tower preclear_disk-finish[6171]: SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS Feb 14 05:26:19 Tower preclear_disk-finish[6171]: 1 0 0 Not_testing Feb 14 05:26:19 Tower preclear_disk-finish[6171]: 2 0 0 Not_testing Feb 14 05:26:19 Tower preclear_disk-finish[6171]: 3 0 0 Not_testing Feb 14 05:26:19 Tower preclear_disk-finish[6171]: 4 0 0 Not_testing Feb 14 05:26:19 Tower preclear_disk-finish[6171]: 5 0 0 Not_testing Feb 14 05:26:19 Tower preclear_disk-finish[6171]: Selective self-test flags (0x0): Feb 14 05:26:19 Tower preclear_disk-finish[6171]: After scanning selected spans, do NOT read-scan remainder of disk. Feb 14 05:26:19 Tower preclear_disk-finish[6171]: If Selective self-test is pending on power-up, resume after 0 minute delay. Feb 14 05:26:19 Tower preclear_disk-finish[6171]: Feb 14 05:26:19 Tower preclear_disk-diff[6184]: You would look for failing attributes that were unchanged between the pre and post reports (and would therefore not show in the diff). You drive looks fine. Quote Link to comment
abeta Posted February 14, 2010 Share Posted February 14, 2010 Silly question...but doesn't diff show me all of the changes so that if it isn't included in the diff it wouldn't have changed or failed? Quote Link to comment
Joe L. Posted February 14, 2010 Share Posted February 14, 2010 Silly question...but doesn't diff show me all of the changes so that if it isn't included in the diff it wouldn't have changed or failed? Yes, a diff would show you all the changes... But let's say the "raw" value of a given did not change (or is blank as with so many attributes), and let's say the CURRENT, WORST, or THRESHOLD did not change. Let's also say the CURRENT value for that attribute has reached the THRESHOLD. The "Failing" column for that attribute in the "pre" report would say "FAILING_NOW" and it would "FAILING_NOW" in the "post" report, therefor the line for that attribute would not show in the "diff" The odds of this happening and the disk still be able to be cleared are slim, but it could happen. Joe L. Quote Link to comment
abeta Posted February 14, 2010 Share Posted February 14, 2010 Ah I see. Thanks for the explanation. That scenario didn't occur to me Quote Link to comment
pfp Posted March 4, 2010 Share Posted March 4, 2010 Just finished preclar on my third drive and got the results shown below. Can someone please help me understand what this means? Thank you Mar 4 06:28:00 Tower preclear_disk-diff[11659]: ============================================================================ Mar 4 06:28:00 Tower preclear_disk-diff[11659]: == Mar 4 06:28:00 Tower preclear_disk-diff[11659]: == Disk /dev/sda has been successfully precleared Mar 4 06:28:00 Tower preclear_disk-diff[11659]: == Mar 4 06:28:00 Tower preclear_disk-diff[11659]: == Ran 1 preclear-disk cycle Mar 4 06:28:00 Tower preclear_disk-diff[11659]: == Mar 4 06:28:00 Tower preclear_disk-diff[11659]: == Using :Read block size = 8225280 Bytes Mar 4 06:28:00 Tower preclear_disk-diff[11659]: == Last Cycle's Pre Read Time : 4:55:40 (84 MB/s) Mar 4 06:28:00 Tower preclear_disk-diff[11659]: == Last Cycle's Zeroing time : 4:23:27 (94 MB/s) Mar 4 06:28:00 Tower preclear_disk-diff[11659]: == Last Cycle's Post Read Time : 10:40:14 (39 MB/s) Mar 4 06:28:00 Tower preclear_disk-diff[11659]: == Last Cycle's Total Time : 20:00:29 Mar 4 06:28:00 Tower preclear_disk-diff[11659]: == Mar 4 06:28:00 Tower preclear_disk-diff[11659]: == Total Elapsed Time 20:00:29 Mar 4 06:28:00 Tower preclear_disk-diff[11659]: == Mar 4 06:28:00 Tower preclear_disk-diff[11659]: == Disk Start Temperature: 31C Mar 4 06:28:00 Tower preclear_disk-diff[11659]: == Mar 4 06:28:00 Tower preclear_disk-diff[11659]: == Current Disk Temperature: -->44<--C, Mar 4 06:28:00 Tower preclear_disk-diff[11659]: == Mar 4 06:28:00 Tower preclear_disk-diff[11659]: ============================================================================ Mar 4 06:28:00 Tower preclear_disk-diff[11659]: S.M.A.R.T. error count differences detected after pre-clear Mar 4 06:28:00 Tower preclear_disk-diff[11659]: note, some 'raw' values may change, but not be an indication of a problem Mar 4 06:28:00 Tower preclear_disk-diff[11659]: 55c55 Mar 4 06:28:00 Tower preclear_disk-diff[11659]: < 1 Raw_Read_Error_Rate 0x000f 118 099 006 Pre-fail Always - 178703071 Mar 4 06:28:00 Tower preclear_disk-diff[11659]: --- Mar 4 06:28:00 Tower preclear_disk-diff[11659]: > 1 Raw_Read_Error_Rate 0x000f 117 099 006 Pre-fail Always - 124958869 Mar 4 06:28:00 Tower preclear_disk-diff[11659]: 59c59 Mar 4 06:28:00 Tower preclear_disk-diff[11659]: < 7 Seek_Error_Rate 0x000f 075 060 030 Pre-fail Always - 33935548 Mar 4 06:28:00 Tower preclear_disk-diff[11659]: --- Mar 4 06:28:00 Tower preclear_disk-diff[11659]: > 7 Seek_Error_Rate 0x000f 075 060 030 Pre-fail Always - 34046022 Mar 4 06:28:00 Tower preclear_disk-diff[11659]: 65,67c65,67 Mar 4 06:28:00 Tower preclear_disk-diff[11659]: < 189 High_Fly_Writes 0x003a 095 095 000 Old_age Always - 5 Mar 4 06:28:00 Tower preclear_disk-diff[11659]: < 190 Airflow_Temperature_Cel 0x0022 069 041 045 Old_age Always In_the_past 31 (15 15 31 27) Mar 4 06:28:00 Tower preclear_disk-diff[11659]: < 195 Hardware_ECC_Recovered 0x001a 055 026 000 Old_age Always Mar 4 06:28:00 Tower preclear_disk-diff[11659]: --- Mar 4 06:28:00 Tower preclear_disk-diff[11659]: > 189 High_Fly_Writes 0x003a 093 093 000 Old_age Always - 7 Mar 4 06:28:00 Tower preclear_disk-diff[11659]: > 190 Airflow_Temperature_Cel 0x0022 056 041 045 Old_age Always In_the_past 44 (15 15 47 27) Mar 4 06:28:00 Tower preclear_disk-diff[11659]: > 195 Hardware_ECC_Recovered 0x001a 062 026 000 Old_age Always Mar 4 06:28:00 Tower preclear_disk-diff[11659]: 71,73c71,73 Mar 4 06:28:00 Tower preclear_disk-diff[11659]: < 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 109160888798470 Mar 4 06:28:00 Tower preclear_disk-diff[11659]: < 241 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 3069302802 Mar 4 06:28:00 Tower preclear_disk-diff[11659]: < 242 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 4199941684 Mar 4 06:28:00 Tower preclear_disk-diff[11659]: --- Mar 4 06:28:00 Tower preclear_disk-diff[11659]: > 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 269152715541786 Mar 4 06:28:00 Tower preclear_disk-diff[11659]: > 241 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 1787972651 Mar 4 06:28:00 Tower preclear_disk-diff[11659]: > 242 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 978331663 Mar 4 06:28:00 Tower preclear_disk-diff[11659]: ============================================================================ Mar 4 06:28:00 Tower preclear_disk-diff[11659]: Quote Link to comment
Joe L. Posted March 4, 2010 Share Posted March 4, 2010 Just finished preclar on my third drive and got the results shown below. Can someone please help me understand what this means? Thank you Mar 4 06:28:00 Tower preclear_disk-diff[11659]: ============================================================================ Mar 4 06:28:00 Tower preclear_disk-diff[11659]: == Mar 4 06:28:00 Tower preclear_disk-diff[11659]: == Disk /dev/sda has been successfully precleared Mar 4 06:28:00 Tower preclear_disk-diff[11659]: == Mar 4 06:28:00 Tower preclear_disk-diff[11659]: == Ran 1 preclear-disk cycle Mar 4 06:28:00 Tower preclear_disk-diff[11659]: == Mar 4 06:28:00 Tower preclear_disk-diff[11659]: == Using :Read block size = 8225280 Bytes Mar 4 06:28:00 Tower preclear_disk-diff[11659]: == Last Cycle's Pre Read Time : 4:55:40 (84 MB/s) Mar 4 06:28:00 Tower preclear_disk-diff[11659]: == Last Cycle's Zeroing time : 4:23:27 (94 MB/s) Mar 4 06:28:00 Tower preclear_disk-diff[11659]: == Last Cycle's Post Read Time : 10:40:14 (39 MB/s) Mar 4 06:28:00 Tower preclear_disk-diff[11659]: == Last Cycle's Total Time : 20:00:29 Mar 4 06:28:00 Tower preclear_disk-diff[11659]: == Mar 4 06:28:00 Tower preclear_disk-diff[11659]: == Total Elapsed Time 20:00:29 Mar 4 06:28:00 Tower preclear_disk-diff[11659]: == Mar 4 06:28:00 Tower preclear_disk-diff[11659]: == Disk Start Temperature: 31C Mar 4 06:28:00 Tower preclear_disk-diff[11659]: == Mar 4 06:28:00 Tower preclear_disk-diff[11659]: == Current Disk Temperature: -->44<--C, Mar 4 06:28:00 Tower preclear_disk-diff[11659]: == Mar 4 06:28:00 Tower preclear_disk-diff[11659]: ============================================================================ Mar 4 06:28:00 Tower preclear_disk-diff[11659]: S.M.A.R.T. error count differences detected after pre-clear Mar 4 06:28:00 Tower preclear_disk-diff[11659]: note, some 'raw' values may change, but not be an indication of a problem Mar 4 06:28:00 Tower preclear_disk-diff[11659]: 55c55 Mar 4 06:28:00 Tower preclear_disk-diff[11659]: < 1 Raw_Read_Error_Rate 0x000f 118 099 006 Pre-fail Always - 178703071 Mar 4 06:28:00 Tower preclear_disk-diff[11659]: --- Mar 4 06:28:00 Tower preclear_disk-diff[11659]: > 1 Raw_Read_Error_Rate 0x000f 117 099 006 Pre-fail Always - 124958869 Mar 4 06:28:00 Tower preclear_disk-diff[11659]: 59c59 Mar 4 06:28:00 Tower preclear_disk-diff[11659]: < 7 Seek_Error_Rate 0x000f 075 060 030 Pre-fail Always - 33935548 Mar 4 06:28:00 Tower preclear_disk-diff[11659]: --- Mar 4 06:28:00 Tower preclear_disk-diff[11659]: > 7 Seek_Error_Rate 0x000f 075 060 030 Pre-fail Always - 34046022 Mar 4 06:28:00 Tower preclear_disk-diff[11659]: 65,67c65,67 Mar 4 06:28:00 Tower preclear_disk-diff[11659]: < 189 High_Fly_Writes 0x003a 095 095 000 Old_age Always - 5 Mar 4 06:28:00 Tower preclear_disk-diff[11659]: < 190 Airflow_Temperature_Cel 0x0022 069 041 045 Old_age Always In_the_past 31 (15 15 31 27) Mar 4 06:28:00 Tower preclear_disk-diff[11659]: < 195 Hardware_ECC_Recovered 0x001a 055 026 000 Old_age Always Mar 4 06:28:00 Tower preclear_disk-diff[11659]: --- Mar 4 06:28:00 Tower preclear_disk-diff[11659]: > 189 High_Fly_Writes 0x003a 093 093 000 Old_age Always - 7 Mar 4 06:28:00 Tower preclear_disk-diff[11659]: > 190 Airflow_Temperature_Cel 0x0022 056 041 045 Old_age Always In_the_past 44 (15 15 47 27) Mar 4 06:28:00 Tower preclear_disk-diff[11659]: > 195 Hardware_ECC_Recovered 0x001a 062 026 000 Old_age Always Mar 4 06:28:00 Tower preclear_disk-diff[11659]: 71,73c71,73 Mar 4 06:28:00 Tower preclear_disk-diff[11659]: < 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 109160888798470 Mar 4 06:28:00 Tower preclear_disk-diff[11659]: < 241 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 3069302802 Mar 4 06:28:00 Tower preclear_disk-diff[11659]: < 242 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 4199941684 Mar 4 06:28:00 Tower preclear_disk-diff[11659]: --- Mar 4 06:28:00 Tower preclear_disk-diff[11659]: > 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 269152715541786 Mar 4 06:28:00 Tower preclear_disk-diff[11659]: > 241 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 1787972651 Mar 4 06:28:00 Tower preclear_disk-diff[11659]: > 242 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 978331663 Mar 4 06:28:00 Tower preclear_disk-diff[11659]: ============================================================================ Mar 4 06:28:00 Tower preclear_disk-diff[11659]: It means your disk is running very hot 44C. Most people try to keep them below 40C. Other than that, see here: http://lime-technology.com/forum/index.php?topic=4068.msg36786#msg36786 Quote Link to comment
Rastarize Posted March 20, 2010 Share Posted March 20, 2010 I'm a total newbie here and I just precleared a 2TB WDEADS Green Drive. These are the results I got following the preclear, any insight? It looks as though I may be missing some info? I dunno what this means, it's all Swahili to me! S.M.A.R.T. error count differences detected after pre-clear note, some 'raw' values may change, but not be an indication of a problem 54c54 < 1 Raw_Read_Error_Rate 0x002f 100 253 051 Pre-fail Always - 0 --- > 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0 63c63 < 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 25 --- > 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 26 ============================================================================ Quote Link to comment
Joe L. Posted March 20, 2010 Share Posted March 20, 2010 Read back about 6 posts or so. You are looking at a diff between the smart report before the preclear and after. http://lime-technology.com/forum/index.php?topic=4068.msg48756#msg48756 Your disk is fine. Joe L. Quote Link to comment
MrLeek Posted April 7, 2010 Share Posted April 7, 2010 Just a sanity check please folks - my understanding thus far is that all is good on both drives (the reports were identical - aside from the fact that one drive took 3 hours longer to complete the script. This is the longer of the two). Both drives are WD EARS (2TB) and are both brand new: I think there's some issues with my router - it keeps dropping the wireless connection on a regular basis. Although this script was run via wired-ethernet, this might be signs of a bigger problem.... Quote Link to comment
MrLeek Posted April 7, 2010 Share Posted April 7, 2010 Thought so (phew!) - hopefully the other newbies out there can use these normal results to help understand their own results. Quote Link to comment
Joe L. Posted April 7, 2010 Share Posted April 7, 2010 The normalized values are set by many manufacturers on a brand new disk to either 253 or 200. Once the disk has some use, these change to their starting points, usually 100 or 200. All the lines with changes are just that initial set to the beginning "normalized" values once the disk have been in use for a short time. The only "raw" value that is humanly-understandable in your output is the number of times the disk heads were loaded onto the disk platters. That incremented by 1. (and that is expected, since if the disks heads had not moved from the parked position onto the disk platters, it would not have been able to read or write the disk at all.) Quote Link to comment
rgb30 Posted May 8, 2010 Share Posted May 8, 2010 Hello, I began preclearing 4 disks yesterday morning, and earlier today noticed 2 of them had basically "stalled". I stopped the 2 "stalled" sessions, 1 at 6 hours, the other around 2 hours into the process. The other 2 completed the script indicating they had not been precleared, both with this error. === = unRAID server Pre-Clear disk /dev/sdh = cycle 1 of 1 = Disk Pre-Clear-Read completed DONE = Step 1 of 10 - Copying zeros to first 2048k bytes DONE = Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE = Step 3 of 10 - Disk is now cleared from MBR onward. DONE = Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4 DONE = Step 5 of 10 - Clearing MBR code area DONE = Step 6 of 10 - Setting MBR signature bytes DONE = Step 7 of 10 - Setting partition 1 to precleared state DONE = Step 8 of 10 - Notifying kernel we changed the partitioning DONE = Step 9 of 10 - Creating the /dev/disk/by* entries DONE = Step 10 of 10 - Testing if the clear has been successful. DONE = Post-Read in progress: 66% complete. ( 1,327,560,192,000 of 2,000,398,934,016 bytes read ) Disk Temperature: 32C, Elapsed Time: 31:24:45 ./preclear_disk.sh: line 552: 1+()%(243201) : syntax error: operand expected (error token is ")%(243201) ") ============================================================================== == Disk /dev/sdh has NOT been precleared successfully == skip=50600 count=200 returned instead of 00000 skip=160800 count=200 returned instead of 00000 ============================================================================ S.M.A.R.T. error count differences detected after pre-clear note, some 'raw' values may change, but not be an indication of a problem 15,25c15,87 < Error SMART Status command failed < Please get assistance from http://smartmontools.sourceforge.net/ < Register values returned from SMART Status command are: < ST =0x40 < ERR=0x00 < NS =0x14 < SC =0xa8 < CL =0x88 < CH =0xe0 < SEL=0x40 < A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options. --- > === START OF READ SMART DATA SECTION === > SMART overall-health self-assessment test result: PASSED > > General SMART Values: > Offline data collection status: (0x84) Offline data collection activity was suspended by an interrupting command from host. 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: (40800) 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: (0x3031) 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 154 153 021 Pre-fail Always - 9283 > 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 36 > 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 > 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 > 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 - 34 > 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 18 > 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 151 > 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 200 200 000 Old_age Offline - 0 > 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 > 200 Multi_Zone_Error_Rate 0x0008 200 200 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. > ======================================================================== After powering down and back up I ran the -t command against both completed disks and show they have successfully been precleared. Should I run the script again? What about the "partition" /dev/sdh1? I would appreciate your comments...... ######################################################################## Device Model: WDC WD20EARS-00S8B1 Serial Number: WD-WCAVY2741749 Firmware Version: 80.00A80 User Capacity: 2,000,398,934,016 bytes Disk /dev/sdh: 2000.3 GB, 2000398934016 bytes 255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors Units = sectors of 1 * 512 = 512 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sdh1 63 3907029167 1953514552+ 0 Empty Partition 1 does not end on cylinder boundary. ######################################################################## ============================================================================ == == DISK /dev/sdh IS PRECLEARED == ============================================================================ root@Tower:/boot/unmenu# Quote Link to comment
Joe L. Posted May 8, 2010 Share Posted May 8, 2010 The partition is created by the pre-cleared process AND it is part of the pre-clear signature. If you remove it, the disk will not be detected as pre-cleared. You may have run out of RAM running three processes at a time . Depending on what else you were running it might get to fail as it uses pretty large buffer sizes when reading and writing the disks. In any case, it looks like it stalled in the post-read, and that is why the disk appears as pre-cleared. You can accomplish reading the entire disk (to substitute for the post-read that never finished) by running a "long" test via SMART. If it encounters sectors it cannot read it will abort without completing 100%. Type smartctl -t long /dev/sdh Wait the indicated duration, get a new smart report to see the results of the "long" test by typing smartctl -a -d ata /dev/sdh look for sectors pending re-allocation or re-allocated. Look for the "long" test completing 100% One more thing, the error you posted is interesting. The line that failed is this: skip_b=$(( 1+(`head -c4 /dev/urandom| od -An -tu4`)%($blocks) )) It apparently was evaluated as 1+()%(243201) (Note the empty parens "()" where it was expecting a number) That seems to indicate the attempt to get a random number failed when invoking head -c4 /dev/urandom| od -An -tu4 Which brings me back to my original statement, that should never fail unless there is a lack of memory and it was killed when invoked, or it was unable to start. Very interesting indeed. Joe L. Quote Link to comment
rgb30 Posted May 9, 2010 Share Posted May 9, 2010 Will do and report back......Thankx for the advice Joe..... Quote Link to comment
rgb30 Posted May 9, 2010 Share Posted May 9, 2010 Joe, here are the results from the long SMART tests. When I built the server I performed a MemTest on the 4GB installed, said no problems. I may just run 1 session of preclear and see what the results are.... root@Tower:/boot/unmenu# smartctl -t long /dev/sdh smartctl version 5.38 [i486-slackware-linux-gnu] Copyright © 2002-8 Bruce Allen Home page is http://smartmontools.sourceforge.net/ === START OF OFFLINE IMMEDIATE AND SELF-TEST SECTION === Sending command: "Execute SMART Extended self-test routine immediately in off-line mode". Drive command "Execute SMART Extended self-test routine immediately in off-line mode" successful. Testing has begun. Please wait 255 minutes for test to complete. Test will complete after Sun May 9 10:05:53 2010 Use smartctl -X to abort test. root@Tower:/boot/unmenu# root@Tower:/boot/unmenu# smartctl -a -d ata /dev/sdh smartctl version 5.38 [i486-slackware-linux-gnu] Copyright © 2002-8 Bruce Allen Home page is http://smartmontools.sourceforge.net/ === START OF INFORMATION SECTION === Device Model: WDC WD20EARS-00S8B1 Serial Number: WD-WCAVY2741749 Firmware Version: 80.00A80 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: Sun May 9 10:08:20 2010 GMT+6 SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x82) Offline data collection activity was completed without error. Auto Offline Data Collection: Enabled. Self-test execution status: ( 244) Self-test routine in progress... 40% of test remaining. Total time to complete Offline data collection: (40800) 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: (0x3031) 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 154 153 021 Pre-fail Always - 9283 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 38 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 68 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 - 36 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 19 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 186 194 Temperature_Celsius 0x0022 124 111 000 Old_age Always - 28 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 200 200 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 200 200 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. root@Tower:/boot/unmenu# Quote Link to comment
Joe L. Posted May 9, 2010 Share Posted May 9, 2010 You did not wait until the "long" test was complete... Your report request said: Testing has begun. Please wait 255 minutes for test to complete. Test will complete after Sun May 9 10:05:53 2010 and then, when you requested a status report: Self-test execution status: ( 244) Self-test routine in progress... 40% of test remaining. It is still running... (and if not, it might need to be requested as smartctl -d ata -t long /dev/sdh ) adding the "-d ata" to the command. Quote Link to comment
rgb30 Posted May 9, 2010 Share Posted May 9, 2010 Guess I took 255 minutes literally, I ran the report command 2 minutes after the "suggested" completion time. Ill make sure its finished next time. Testing has begun. Please wait 255 minutes for test to complete. Test will complete after Sun May 9 10:05:53 2010 root@Tower:/boot/unmenu# smartctl -a -d ata /dev/sdh === START OF INFORMATION SECTION === Local Time is: Sun May 9 10:08:20 2010 GMT+6 Quote Link to comment
Rajahal Posted May 26, 2010 Share Posted May 26, 2010 Just want some confirmation that the attached preclear results for 4 different drives are OK (3x 2TB WD EARS w/ jumpers, 1x 1.5TB Seagate 7200 rpm). Everything looked normal to me, but I just wanted to make sure I didn't miss anything. I had to view this syslog in Wordpad for some reason. The formatting is all kinds of messed up when I open it with Notepad. Weird. guiri_syslog_-_5-25-2010_-_preclear_3_x_2_TB_+_1_x_1.5_TB.zip Quote Link to comment
Rajahal Posted May 30, 2010 Share Posted May 30, 2010 ...and here's the preclear results of the last two disks. Everything looks normal to me, but again, I would appreciate a second set of eyes confirming this. guiri_syslog_5-30-2010_-_precleared_1.5_TB_EADS_and_last_2_TB_EARS.txt Quote Link to comment
jbuszkie Posted June 14, 2010 Author Share Posted June 14, 2010 Wow the 2T disks take a while.. Disk1 == Disk /dev/sdh has been successfully precleared == == Ran 1 preclear-disk cycle == == Using :Read block size = 8225280 Bytes == Last Cycle's Pre Read Time : 7:41:11 (72 MB/s) == Last Cycle's Zeroing time : 9:42:22 (57 MB/s) == Last Cycle's Post Read Time : 35:29:32 (15 MB/s) == Last Cycle's Total Time : 52:54:19 == == Total Elapsed Time 52:54:19 == == Disk Start Temperature: 33C == == Current Disk Temperature: 36C, == ============================================================================ S.M.A.R.T. error count differences detected after pre-clear note, some 'raw' values may change, but not be an indication of a problem 58c58 < 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 --- > > 7 Seek_Error_Rate 0x002e 100 253 000 Old_age Always - 0 63c63 < 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 83 --- > > 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 821 ============================================================================ Disk 2 Date: Sun Jun 13 22:59:32 EDT 2010 ============================================================================ == == Disk /dev/sdb has been successfully precleared == == Ran 1 preclear-disk cycle == == Using :Read block size = 8225280 Bytes == Last Cycle's Pre Read Time : 7:29:39 (74 MB/s) == Last Cycle's Zeroing time : 8:24:39 (66 MB/s) == Last Cycle's Post Read Time : 35:33:46 (15 MB/s) == Last Cycle's Total Time : 51:29:23 == == Total Elapsed Time 51:29:23 == == Disk Start Temperature: 26C == == Current Disk Temperature: 32C, == ============================================================================ S.M.A.R.T. error count differences detected after pre-clear note, some 'raw' values may change, but not be an indication of a problem 19,20c19,20 < Offline data collection status: (0x80) Offline data collection activity < was never started. --- > > Offline data collection status: (0x84) Offline data collection activity > > was suspended by an interrupting command from host. 54c54 < 1 Raw_Read_Error_Rate 0x002f 100 253 051 Pre-fail Always - 0 --- > > 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0 63c63 < 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 19 --- > > 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 760 67c67 < 199 UDMA_CRC_Error_Count 0x0032 200 253 000 Old_age Always - 0 --- > > 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 ============================================================================ I went from 72MB/s down to 15MB/s for the Post read! 52 hours!! Granted I was running two disks at once. I wonder if it would have gone faster if I had more memory. Or Maybe boosted the cpu speed. Right now I have one 1GB and running at 900MHz (under clocked to save power) It also seems like the 2 port syba 1x PCIe sata card is slightly faster than the on board (sdb was on that card). Maybe because the rest of the array is on the on board as well. Jim 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.