Re: Device is not in smartctl database. Consequences and solution?

Ivan Lezhnjov Jr. wrote:
>> This is as expected because the USB ID drivedb entry is (only) used to set the -d option for the ATA pass-through protocol the USB bridge supports.
> Btw, I'm just curious.. in case with my particular drive I think a mere addition of a new DB entry that matches properly USB vendor and product IDs is mostly to associate "-d sat". But what about the actual SMART/ATA commands etc (mind you I have a very superfluous understanding so I may not make much sense lol), are they SOOO much universal that no additional configuration is required?

Yes, the SMART READ DATA command itself is universal and unchanged since 
it first appeared in ATA-3 (1997).

No, the SMART attribute data (bytes 0-361 of SMART data structure) is 
"Vendor specific" since ATA-4 (1998).

The "SMART Attribute Annex" proposal was never included in the standard:
http://sourceforge.net/apps/trac/smartmontools/wiki/Links#ATAATAPIReferences


> Can I be somehow sure that SMART Attributes are interpreted exactly like vendor designed them to be interpreted?

No, unless a documentation of the attributes or a vendor specific SMART 
tool is available.

In practice, it depends:
HDDs: Even recent HDDs apparently use the traditional attribute 
assignments. Documentation is rare.

SSDs: Attributes differ in many cases. Smartctl may not print correct 
names and raw value formats unless a drivedb entry exists. Some vendors 
of SSDs or SSD controllers provide documentation, others don't.

Thanks,
Christian


------------------------------------------------------------------------------
Sponsored by Intel(R) XDK 
Develop, test and display web and hybrid apps with a single code base.
Download it for free now!
http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk