Karl Pielorz wrote:
> I've just updated my copy of Smartmontools 5.40 to use the latest (from
> SVN) copy of drivedb.h (Revision 3215).
> This seemed to include some changes for the OCZ Vertex2-Pro drives we have
> (I submitted a smartctl -a output to the database list a while back).
The changes in r3209 were the result of your submission.
> Whilst this does now seem to be supported, i.e. we get:
> === START OF INFORMATION SECTION ===
> Model Family: SandForce Driven SSDs
> Device Model: OCZ VERTEX2-PRO
> Serial Number: f1b060006
> Firmware Version: 1.10
> User Capacity: 50,020,540,416 bytes
> Device is: In smartctl database [for details use: -P show]
> There still appears to be issues with two of the parameters, i.e.
> 232 Available_Reservd_Space 0x0000 000 000 010 Old_age Offline
> FAILING_NOW 16
> 233 SandForce_Internal 0x0000 000 000 000 Old_age Offline
> - 320
> 234 SandForce_Internal 0x0000 000 000 000 Old_age Offline
> - 896
> 235 SuperCap_Health 0x0033 000 000 001 Pre-fail Always
> FAILING_NOW 0
The drive returns bogus nonzero thresholds for attributes which
normalized value are apparently always zero.
> Is it valid to just 'poach' the latest drivedb.h and recompile with it, or
> are there any other files that also need to be updated?
It is even not necessary to recompile it, smartctl 5.40 reads this file
from /usr/share/smartmontools. Simply run the update script:
> drivedb.h says:
> "OCZ VERTEX2-PRO/1.10 (Bogus thresholds for attribute 232 and 235)"
> But I can't tell if that's something it's stating either "Hey, they're
> broke" or "We know they're broke so we'll ignore them".
These thresholds should be ignored but there is no -v option for
drivedb.h to select this. Adding one would break backward compatibility
of drivedb.h and therefore would require to add a new 5.40 drivedb.h
branch. IMO not worth the effort for one single drive model. I will
probably add this later.
> Will Smartmontools see those two 'FAILING' attributes and presume the drive
> is failing immediately?
Smartd prints failed attribute warnings, add "-I 232 -I 235" to
smartd.conf to prevent this.