tyrindor Posted July 17, 2010 Share Posted July 17, 2010 After preclearing my WD20EARS, It had a Seek_Error_Rate of 1. It was 0 before the preclear. I've never had this value increase and i'm wondering if I should send it back since I can still get it replaced for free. None of my EADS did this (And I have 11 of them), first EARS and this happens. Is it normal for EARS? Quote Link to comment
Joe L. Posted July 17, 2010 Share Posted July 17, 2010 After preclearing my WD20EARS, It had a Seek_Error_Rate of 1. It was 0 before the preclear. I've never had this value increase and i'm wondering if I should send it back since I can still get it replaced for free. None of my EADS did this (And I have 11 of them), first EARS and this happens. Is it normal for EARS? You have not read how to interpret the SMART reports, have you? The "raw" values vary from manufacturer to manufacturer and disk drive model/firmware level. Most are meaningful only to the manufacturer. Some disk manufacturers show them, others do not, they almost never have meaning to end-users like us. About the only ones consistently usable are Temperature, and Sectors re-allocated or pending re-allocation. (and even the temperature is sometimes suspect, as some drives report as temperature below ambient, and that is not possible unless the reported number must be offset to get a true temperature reading.) Unless the normalized "Worst" value is near or at the failure "threshold" value for that parameter for seek-errors, the manufacturer would consider the drive to be working as expected. Joe L. Quote Link to comment
madburg Posted February 28, 2011 Share Posted February 28, 2011 Hi Joe, Appreciate your insight on the follwoing report so I can learn what I am looking at. This is a old WD Raptor 8gb 10K drive I pre-cleared (first preclear I have ever performed). May use this as a cache drive... ========================================================================1.6 == invoked as: ./preclear_disk.sh -M 4 /dev/sdd == WDC WD800ADFS-75SLR2 WD-WMANS1500466== Disk /dev/sdd has been successfully precleared == with a starting sector of 64 == Ran 1 cycle == == Using :Read block size = 8225280 Bytes == Last Cycle's Pre Read Time : 0:20:01 (65 MB/s) == Last Cycle's Zeroing time : 0:19:37 (67 MB/s) == Last Cycle's Post Read Time : 0:41:17 (31 MB/s) == Last Cycle's Total Time : 1:22:08 == == Total Elapsed Time 1:22:08 == == Disk Start Temperature: 27C == == Current Disk Temperature: 29C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdd /tmp/smart_finish_sdd ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Seek_Error_Rate = 100 200 51 ok 0 Temperature_Celsius = 114 116 0 ok 29 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. If you need anything else from the rest of the report let me mknow. Much appreciated. Quote Link to comment
Rajahal Posted February 28, 2011 Share Posted February 28, 2011 Looks like a perfectly healthy drive to me. Nothing is near the threshold... Quote Link to comment
Joe L. Posted February 28, 2011 Share Posted February 28, 2011 The normalized seek error rate current value is 100. Before you started it was 200 (often an initialized value from the factory) Both are well over the failure threshold of 51. Only the manufacturer knows what those represent, and they don't tell anyone, other than if the value is above the affiliated failure threshold, it is not failing. Joe L. Quote Link to comment
madburg Posted February 28, 2011 Share Posted February 28, 2011 Thank you! How should I read this for my understanding, old value was 200, now 100 failure threshold is 51? Quote Link to comment
Rajahal Posted February 28, 2011 Share Posted February 28, 2011 Exactly right. If subsequent SMART tests showed that value dropping closer and closer to 51, then it might be a cause for concern. For the time being, I would trust the drive. Quote Link to comment
Joe L. Posted February 28, 2011 Share Posted February 28, 2011 Thank you! How should I read this for my understanding, old value was 200, now 100 failure threshold is 51? See http://en.wikipedia.org/wiki/S.M.A.R.T.#ATA_S.M.A.R.T._attributes Both 200 and 100 are often initial values given to parameters when the drive gets a bit of time on it. Don't try to read ANYTHING into it, as we've seen drives where the initial value is 100 and the failure threshold is 99. There is no standard. Each manufacturer makes up their own rules... The only constant is if the normalized value is greater than the affiliated failure threshold that it is not failing. It DOES NOT indicate the drive is good, as many times SMART parameters do not show anything abnormal for a a drive that is causing all kinds of errors. In the same way, a drive that is FAILING_NOW on some parameters might be perfectly fine. Good luck in understanding... nobody really does. For some it is a "marketing" thing. To help in the sales brochure. If you think this is too crude a description, just think, 99% of the disks in the world never get tested, and never get a smart report run on them, and most are used in windows PS, and they never crash.... Quote Link to comment
madburg Posted February 28, 2011 Share Posted February 28, 2011 No, thats cool, more than enough info, many thanks guys, as always! Quote Link to comment
madburg Posted March 1, 2011 Share Posted March 1, 2011 Ok here is another drive I just precleared (old 320GB Deskstar). Need to understand what re-allocated means, my understanding is that is not good, but there must be a gauge of "ok thats not to bad for an old driver" or if that is not the case say "always scrape a drive that has re-allocated sectors" for an example. Also seemed to had 3 (or 9) Errors but back when it was used for 147 days (is my understanding) this should not be an issue as they happened once all at the same time (long time ago) yes? ========================================================================1.6 == invoked as: ./preclear_disk.sh -M 4 /dev/sda == Hitachi HDT725032VLA360 VFM201R234P27N== Disk /dev/sda has been successfully precleared == with a starting sector of 64 == Ran 1 cycle == == Using :Read block size = 8225280 Bytes == Last Cycle's Pre Read Time : 1:41:48 (52 MB/s) == Last Cycle's Zeroing time : 1:45:07 (50 MB/s) == Last Cycle's Post Read Time : 3:22:42 (26 MB/s) == Last Cycle's Total Time : 6:50:52 == == Total Elapsed Time 6:50:52 == == Disk Start Temperature: 32C == == Current Disk Temperature: 33C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sda /tmp/smart_finish_sda ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 100 86 16 ok 0 Temperature_Celsius = 181 187 0 ok 33 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. 5 sectors had been re-allocated before the start of the preclear. 5 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change. ============================================================================ ============================================================================ == == S.M.A.R.T Initial Report for /dev/sda == Disk: /dev/sda 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 === Model Family: Hitachi Deskstar T7K500 Device Model: Hitachi HDT725032VLA360 Serial Number: VFM201R234P27N Firmware Version: V54OA7EA User Capacity: 320,072,933,376 bytes Device is: In smartctl database [for details use: -P show] ATA Version is: 7 ATA Standard is: ATA/ATAPI-7 T13 1532D revision 1 Local Time is: Tue Mar 1 01:42:29 2011 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: (0x00) Offline data collection activity was never started. Auto Offline Data Collection: Disabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: (5601) seconds. Offline data collection capabilities: (0x5b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. No 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: ( 94) minutes. SCT capabilities: (0x003f) 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 0x000b 086 086 016 Pre-fail Always - 524398 2 Throughput_Performance 0x0005 100 100 050 Pre-fail Offline - 0 3 Spin_Up_Time 0x0007 122 122 024 Pre-fail Always - 308 (Average 302) 4 Start_Stop_Count 0x0012 100 100 000 Old_age Always - 59 5 Reallocated_Sector_Ct 0x0033 100 100 005 Pre-fail Always - 5 7 Seek_Error_Rate 0x000b 100 100 067 Pre-fail Always - 0 8 Seek_Time_Performance 0x0005 100 100 020 Pre-fail Offline - 0 9 Power_On_Hours 0x0012 096 096 000 Old_age Always - 30714 10 Spin_Retry_Count 0x0013 100 100 060 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 58 192 Power-Off_Retract_Count 0x0032 099 099 000 Old_age Always - 1319 193 Load_Cycle_Count 0x0012 099 099 000 Old_age Always - 1319 194 Temperature_Celsius 0x0002 187 187 000 Old_age Always - 32 (Lifetime Min/Max 15/52) 196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 9 197 Current_Pending_Sector 0x0022 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0008 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x000a 200 253 000 Old_age Always - 0 SMART Error Log Version: 1 ATA Error Count: 3 CR = Command Register [HEX] FR = Features Register [HEX] SC = Sector Count Register [HEX] SN = Sector Number Register [HEX] CL = Cylinder Low Register [HEX] CH = Cylinder High Register [HEX] DH = Device/Head Register [HEX] DC = Device Command Register [HEX] ER = Error register [HEX] ST = Status register [HEX] Powered_Up_Time is measured from power on, and printed as DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes, SS=sec, and sss=millisec. It "wraps" after 49.710 days. Error 3 occurred at disk power-on lifetime: 3551 hours (147 days + 23 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 11 05 aa 1b e0 Error: UNC 17 sectors at LBA = 0x001baa05 = 1812997 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 ff 17 ff a9 1b e0 00 00:08:01.900 READ DMA EXT 25 ff 25 7f 96 1f e0 00 00:08:01.900 READ DMA EXT 25 ff 1f e0 01 60 e0 00 00:08:01.900 READ DMA EXT 25 ff 37 c8 05 02 e0 00 00:08:01.900 READ DMA EXT 25 ff 12 9d 43 01 e0 00 00:08:01.900 READ DMA EXT Error 2 occurred at disk power-on lifetime: 3551 hours (147 days + 23 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 16 00 aa 1b e0 Error: UNC 22 sectors at LBA = 0x001baa00 = 1812992 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 ff 17 ff a9 1b e0 00 00:02:18.400 READ DMA EXT 25 ff 25 7f 96 1f e0 00 00:02:18.400 READ DMA EXT 25 ff 1f e0 01 60 e0 00 00:02:18.400 READ DMA EXT 25 ff 37 c8 05 02 e0 00 00:02:18.400 READ DMA EXT 25 ff 12 9d 43 01 e0 00 00:02:18.400 READ DMA EXT Error 1 occurred at disk power-on lifetime: 3551 hours (147 days + 23 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 16 00 aa 1b e0 Error: UNC 22 sectors at LBA = 0x001baa00 = 1812992 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 ff 17 ff a9 1b e0 00 00:00:41.800 READ DMA EXT 25 ff 25 7f 96 1f e0 00 00:00:41.800 READ DMA EXT 25 ff 1f e0 01 60 e0 00 00:00:41.800 READ DMA EXT 25 ff 37 c8 05 02 e0 00 00:00:41.800 READ DMA EXT 25 ff 12 9d 43 01 e0 00 00:00:41.800 READ DMA EXT SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed without error 00% 30689 - SMART Selective self-test log data structure revision number 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Not_testing 2 0 0 Not_testing 3 0 0 Not_testing 4 0 0 Not_testing 5 0 0 Not_testing Selective self-test flags (0x0): After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay. == ============================================================================ Quote Link to comment
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.