Read Raw Error Rate
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 raw read error rate fix Meta Discuss the workings and policies of this site About Us
Raw Read Error Rate Western Digital
Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with raw read error rate 1 us Ask Ubuntu Questions Tags Users Badges Unanswered Ask Question _ Ask Ubuntu is a question and answer site for Ubuntu users and developers. Join them; it only takes
Raw Read Error Rate Fail
a minute: Sign up Here's how it works: Anybody can ask a question Anybody 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 raw read error rate failed suspect that my HDD was starting to fail. After a bit of hunting on the internet, I found Ubuntu's Disk 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
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting
Raw Read Error Rate Ssd
ads with us Super User Questions Tags Users Badges Unanswered Ask Question _ Super User is a
Raw Read Error Rate Western Digital Fix
question and answer site for computer enthusiasts and power users. Join them; it only takes a minute: Sign up Here's how it works: Anybody can how to fix raw read error rate samsung ask a question Anybody can answer The best answers are voted up and rise to the top High S.M.A.R.T read error rate up vote 1 down vote favorite 1 I have a Seagate ST9750420AS HDD in my laptop, which I have been http://askubuntu.com/questions/20393/how-do-i-interpret-hdd-s-m-a-r-t-results using for the last couple of years. I recently realized that the disk was noticeable slower than before, so I decided to check the SMART data. Everything seemed to be OK. A bit more than a year powered on, head flew for 11 months... and all the read errors successfully corrected; no big deals. I decided to note anyway the read error rate, which had a value of 60M (normalized 119, threshold 6, worst 99). Today (3 days after), I checked again those http://superuser.com/questions/867801/high-s-m-a-r-t-read-error-rate numbers and the read error rate value is at 215M, which seems to me like a huge increase in a little time. The normalized and worst values haven't changed anyway, so the assesment is still OK in the SMART data. Should I be worried? My data is backed up, but should I be already buying a new HDD for my laptop? hard-drive smart share|improve this question asked Jan 21 '15 at 22:09 Peque 551312 It may be simply a loose connection. Try to disconnect the HDD and install it again. –gronostaj Jan 21 '15 at 22:15 @gronostaj: The HDD is mounted with screws, but anyway I will try that. Thanks! :-) –Peque Jan 21 '15 at 22:29 1 There has to be some type of data connection. 215 million errors is not normal. Be sure you understand how S.M.A.R.T should be read it snot always obvious. –Ramhound Jan 21 '15 at 23:37 The raw value isn't very meaningful by itself, and not very reliable to predict any failures. If the normalized value is above the threshold, you're fine. Keep your backups up to date, that's all. –Pedro Werneck Feb 21 '15 at 15:43 1 215 million errors is perfectly normal and an inherent part of how modern hard drives operate. Most drives will however hide all errors from you if they can correct them - Seagate is the notable exception here. The raw value before error correction is an internal perf
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. https://lime-technology.com/wiki/index.php/Understanding_SMART_Reports 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 error rate 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 raw read error 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 Airflow_Temperature_Cel 0x0022 057 048 045 Old_age Always - 43 (Min/Max 36/43) 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 - 5 193 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 19 194 Temperature_Celsius 0x0022 043 052 000 Old_age Always - 43 (0 28 0 0) 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 260348032581703 241 Total_LBAs_Wr