Hi! I come with a problem with my HDD to be more exact. I bought a Lenovo G580: i3 ivy 3110m, gt 630m, 6 GB RAM, 1 TB Seagate HDD. The problem is with the HDD, I think: The "write error rate" attribute keeps increasing. Should this worry me? Can HDD Tune mistake the attribute with something else?
Seagate makes a program that you run under windows that will test the drive and tell you if it's a serious problem where the drive needs to be replaced or if it's a not so serious problem where the drive will probably last a while longer. Seatools for windows can be found at the seagate site, or at least it could in the past, haven't checked for it in a while...
Yep, tried that. Ran every test, including SMART, but except ''long''. All tests passed succesfully, with no error. I am still worried about this value increasing. Do you think HDD Tune is showing wrong data?
It apears that it is a Seagate Samsung (??!) HDD. I've found some results on the internet, but none have values this high for write error rate in a matter of 24 hours. Does this corrupt my data every time the error occurs?
I have analysed SMART for various other drives and I have found that a non-zero value for Error Rate attributes does not always reflect errors. My Fujitsu drive, for example, records the number of sectors read in the raw value, and the actual error rate in the normalised value. Seagate's Error Rate attributes are even more obscure.
That said, I have not had the opportunity to analyse Samsung's attributes, so I can't offer an opinion as to their meaning. In any case, the normalised value is still at 100, so this would suggest that the drive is healthy.
Each author of SMART software interprets the SMART data differently. IMHO HD Tune is not the best SMART tool, so I would ignore its warnings and interpret them for myself. I prefer HD Sentinel in this regard.
That said, I wouldn't be too concerned if that were my drive, but that's just my opinion.
In the previous example, attributes 0A and B8 are perfectly OK (normalised value = 100, raw value = 0). I believe HD Tune's warning is triggered because the Current and Threshold values are "too close".