• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Will this drive be fine?

Lean L

Diamond Member
I have a standard desktop drive running in a server. This is a 2TB Hitachi. I have a cron job that updates a webpage every hour with SMART information pulled from ESXi. This is the only way to do it since there is no hardware raid controller and I don't have vcenter. I use a free service to monitor that page and email me when anything changes.

Here is one of the emails I received:

Hitachi 2TB
Parameter Value Threshold Worst
---------------------------- ----- --------- -----
Health Status OK N/A N/A
Media Wearout Indicator N/A N/A N/A
Write Error Count N/A N/A N/A
- Read Error Count 100 16 100
+ Read Error Count 98 16 98
Power-on Hours 97 0 97
Power Cycle Count 100 0 100
Reallocated Sector Count 100 5 100
- Raw Read Error Rate 100 16 100
+ Raw Read Error Rate 98 16 98
Write Sectors TOT Count 200 0 200
Read Sectors TOT Count N/A N/A N/A
Initial Bad Block Count N/A N/A N/A

After that email, the raw read error gradually fixed itself within 3 hours. It is now back up to 100.

Is this a warning sign or am I completely in the clear? I thought the raw value was never supposed to climb back up after it drops?
 
Yes, there is one other drive in that chassis. This has happened twice to this particular drive.

It has quite a bit of raw hours on it but not much actual use.
 
Back
Top