Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
The RAW_VALUE numbers have little to do with actual errors that have occured. It is a six-bit number (with more info) that the VALUE (normalized number). The numbers to worry about are VALUE and THRESH. When VALUE gets close to THRESH, the drive is about to fail. I found this, which might ease your mind:
Each Attribute has a six-byte raw value (RAW_VALUE) and a one-byte normalized value (VALUE). In this case, the raw value stores three temperatures: the disk's temperature in Celsius (29), plus its lifetime minimum (23) and maximum (33) values. The format of the raw data is vendor-specific and not specified by any standard. To track disk reliability, the disk's firmware converts the raw value to a normalized value ranging from 1 to 253. If this normalized value is less than or equal to the threshold (THRESH), the Attribute is said to have failed, as indicated in the WHEN_FAILED column. The column is empty because none of these Attributes has failed. The lowest (WORST) normalized value also is shown; it is the smallest value attained since SMART was enabled on the disk. The TYPE of the Attribute indicates if Attribute failure means the device has reached the end of its design life (Old_age) or it's an impending disk failure (Pre-fail). For example, disk spin-up time (ID #3) is a prefailure Attribute. If this (or any other prefail Attribute) fails, disk failure is predicted in less than 24 hours.
The names/meanings of Attributes and the interpretation of their raw values is not specified by any standard. Different manufacturers sometimes use the same Attribute ID for different purposes. For this reason, the interpretation of specific Attributes can be modified using the -v option to smartctl; please see the man page for details. For example, some disks use Attribute 9 to store the power-on time of the disk in minutes; the -v 9,minutes option to smartctl correctly modifies the Attribute's interpretation. If your disk model is in the smartmontools database, these -v options are set automatically.
Ignore the part about temperatures. The author was using cpu temp as an example of what smartctrl was reporting. You can see from this that the raw value is not reporting actual number of errors.
I assume that the normalized value has reached 100 in 280 hours. So a brand new harddisk should have a value of 253. At this rate, in about 465 hours of operation, my hard disk should reach the end of life cycle... Just 19 days of 24x7 operation... Looks impractical... Where have I gone wrong? Can I predict the failure or the life of a hard disk?
It's more likely that it 'started out as 100' which is normal, rather than 'reached 100 in 280 hours'.
If you check regularly, you will see also that the 'Hours of Operation' value wraps around too, so is not a practical indicator of the age of the drive, nor useful in trying to calculate its life expectancy.