ESXi Smart info: how to read

[Lean L]

So I have setup a primitive way to read smart info from my harddrive from ESXi. The data it presents is not very comprehensive however.


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
Power-on Hours 100 0 100
Power Cycle Count 100 0 100
Reallocated Sector Count 100 5 100
Raw Read Error Rate 100 16 100
Drive Temperature 193 0 193
Driver Rated Max Temperature N/A N/A N/A
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


Is it okay to assume that I should just watch for the 100 values? Will the N/A values change at all for any reason?

 

[imagoon]

http://kb.vmware.com/selfservice/mi...nguage=en_US&cmd=displayKC&externalId=2040405

As they mention, values vary from the manufacturer. Look at what the manufacturer states. Threshold is read from the drive.

 

[Lean L]

Thanks. That means that the values are ambiguous but it should actually reflect the proper changes should a sector be remapped or anything. I found a solution to monitor the drive now.

I wrote a script that pulls the smart info from esxi via ssh then saves it as a txt file that is served by apache. The next step was simply to find a service that would monitor the changes for me. The answer was followthatpage. I made a mock change to my smart reading to test it.

The page http://smart.xxxxxx.net has changed since the previous check.
Options: using line filter.



------ changes ------
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 99 16 100
Power-on Hours 100 0 100
Power Cycle Count 100 0 100
Reallocated Sector Count 100 5 100
Raw Read Error Rate 100 16 100
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

------------------- End of page report -----------------------

 

[imagoon]

Not a bad solution but remember that changes like that to ESXi makes it "unsupportable" if you ever need to put a ticket in.

 

[Lean L]

Not a bad solution but remember that changes like that to ESXi makes it "unsupportable" if you ever need to put a ticket in.

Thanks. This is the free version for my home environment anyways. I don't have support at all.

This pull is also from a VM instead of directly from esxi so there are no changes to esxi besides the additional user permission.

Makes me feel a bit better to be able to monitor this since I have no redundancy. I know... terrible practice but I didn't want to complicate the build when I started... now I'm in pretty deep.