Read Error Rate Threshold
Contents |
communities company blog Stack Exchange Inbox Reputation and Badges sign up log in tour help Tour Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies smart current worst threshold of this site About Us Learn more about Stack Overflow the company Business
What Is Raw Read Error Rate
Learn more about hiring developers or posting ads with us Ask Ubuntu Questions Tags Users Badges Unanswered Ask Question _
Raw Read Error Rate Smart
Ask Ubuntu is a question and answer site for Ubuntu users and developers. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody
Raw Read Error Rate Fix
can answer The best answers are voted up and rise to the top How Do I interpret HDD S.M.A.R.T Results? up vote 40 down vote favorite 10 My laptop has recently started to become a bit unreliable, and for some reason I started to suspect that my HDD was starting to fail. After a bit of hunting on the internet, I found Ubuntu's Disk read error rate 1 Utility in the System menu and ran the long SMART diagnostics from this. However, since the documentation for Disk Utility is very poor (palimpsest?), I'm not sure how to interpret the results: For example, the Read Error Rate is over 50 million (!), yet the Assessment is rated "Good". So would someone mind explaining to me how to interpret the results of these tests (especially the Normalized, Worst, Threshold and Value numbers)? And maybe tell me what they think of the results I got for my HDD? (Thanks) hard-drive smart share|improve this question asked Jan 6 '11 at 23:46 Marty 78021015 Has the "Hardware ECC recovered" same value as "Read error rate"? My disk has 676 power cycles, was powered on 285 days, and has 193M errors. Compared to mine, your disk has way too much error, but I'm just speculating here. Anyways I just got worried myself o.O –danizmax Jan 7 '11 at 8:47 Yip - both numbers are the same! –Marty Jan 7 '11 at 16:32 add a comment| 3 Answers 3 active oldest votes up vote 32 down vote accepted You have a good descript
"Self-Monitoring, Analysis, and Reporting Technology". First developed in the 1992 by leading hard drive manufacturer, S.M.A.R.T. becomes a quasi standard to monitoring and tracking sensitive values from your drive to read error rate crystaldiskinfo prevent hard drives from fail. The plan was, if a hard drive raw read error rate fail says 'I will die soon', the motherboard tell us, so we can backup and change quick the drive. raw read error rate 1 Unfortunately this doesn't works very often. Attributes, Values, Thresholds and S.M.A.R.T. examples Attributes describes the measured value of hard drive controller operations. The values of an attribute are: current, http://askubuntu.com/questions/20393/how-do-i-interpret-hdd-s-m-a-r-t-results worst, threshold and raw. Values are normalized to a vendor specific scale. Scales could be ranged up to 100, 200 or 253. Often higher values are better than lower values. The threshold marks the value at which the hard drive could fail. The worst value is the baddest value seen for this drive at this attribute. The raw value is http://www.easis.com/smart-value-interpretation.html a vendor coded count that give, after decoding, the normal values like current, worst and threshold. S.M.A.R.T. Interpretation First some important knowledge about threshold values. If threshold is 0 the attribute has only information character. If threshold is 253 the attribute is only for testing reason. A typical attribute set could be: Attribute name: "Read Error Rate" Current: 253 Worst: 253 Threshold: 63 Raw: 0 All right , this is a nice set. Nothing happens at this attribute. Only if this attribute reach the threshold value 63, we should have to change the hard drive. Let's look on a attribute with a warning status: Attribute name: "Read Error Rate" Current: 113 Worst: 85 Threshold: 63 Raw: 1234567 The hard drive have sector read errors in the past, but work fine for now and (perhaps) work fine in the near feature. However, I would now start to make more often backups and begin to plan a hard drive change. It is difficult to make correct interpretations in general, because different vendors normalize values in different way. We can rec
S.M.A.R.T. is the abbreviation for "Self Monitoring And Reporting Technology". It is a standard interfaceprotocol and set of the disk features that allowsdisk to check its http://www.z-a-recovery.com/manual/smart.aspx status and report it to a host system. S.M.A.R.T. information consists https://lime-technology.com/wiki/index.php/Understanding_SMART_Reports of "attributes", each one describing some particular aspect of drive condition. Some attributes may be designated "life-critical", which implies that the corresponding parameters are more important than other ones. Three values are associated with each S.M.A.R.T. attribute: "Normalized value", commonly referred to as just "value". This is read error a most universal measurement, on the scale from 0 (bad) to some maximum (good) value. Maximum values are typically 100, 200 or 253. Rule of thumb is: high values are good, low values are bad. "Threshold" - the minimum normalized value limit for the attribute. If the normalized value falls below the threshold, the disk is considered defective and read error rate should be replaced under warranty. This situation is called "T.E.C." (Threshold Exceeded Condition). "Raw value" - the value of the attribute as it is tracked by the device, before any normalization takes place. Some raw numbers provide valuable insight when properly interpreted. These cases will be discussed later on. Raw values are typically listed in hexadecimal numbers. Most common S.M.A.R.T. attributes reference Note that not all of the attributes are present on all drives. Some attributes are of similar meaning (just counted differently), so only one of them will normally be monitored by the drive. Some require special sensors (e.g. temperature or G-loads monitoring). The decision about which attributes should be implemented is up to the drive vendor. Along the same lines the interpretation of raw values depends heavily on the manufacturer. Critical device status attributes Reallocated sectors count Indicates how many defective sectors were discovered on the drive and remapped using a spare sectors pool. Low values in absence of other fault indications point to the disk surface problem. Raw value indicates the e
SMART reports, therefore it should not be considered authoritative. Accuracy however is highly desired, so please feel free to correct it as needed, or suggest corrections or question its statements on the associated Talk page. Contents 1 Prologue 2 Introduction to SMART 3 SMART report structure 3.1 General information section 3.2 SMART overall health test 3.3 SMART parameters section 3.4 SMART attributes section 3.5 Error Log section 3.6 Test results section 4 Table of attributes 4.1 1 Raw_Read_Error_Rate 4.2 3 Spin_Up_Time 4.3 4 Start_Stop_Count 4.4 5 Reallocated_Sector_Ct 4.5 7 Seek_Error_Rate 4.6 9 Power_On_Hours 5 Additional info Prologue There is a lot of ignorance and misinformation out there about SMART reports, so this will be an effort to help users to a better understanding of the content of SMART reports. Consider the following SMART report extract: 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 112 099 006 Pre-fail Always - 42208416 3 Spin_Up_Time 0x0003 096 096 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 7 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 056 055 030 Pre-fail Always - 25772440425 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 72 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 7 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 Air