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

On Nov 30, 2013, at 8:31 PM, Christian Franke <[email protected]> wrote:

> Ivan Lezhnjov Jr. wrote:
>> On Nov 29, 2013, at 11:22 PM, Christian Franke <...> wrote:
>> 
>>> ..
>>> 
>>> For still missing entries, you could add a local drive database entry (usually) at /etc/smartd_drivedb.h.
>> No luck.
>> 
>> If I pass "-d sat" the drives can be opened, but apparently smartctl/smartd treats them as different devices, because this is how the drives are identified by the kernel:
>> 
>>>  localhost kernel: [547111.752845] scsi 46:0:0:0: Direct-Access     WD       Elements 1048    1022 PQ: 0 ANSI: 6
>> and this is how smartmontools sees them:
>> 
>>> % smartctl -i -d sat /dev/sdc
>>> smartctl 5.42 2011-10-20 r3458 [i686-linux-3.4.2-2-ARCH] (local build)
>>> Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net
>>> 
>>> === START OF INFORMATION SECTION ===
>>> Model Family:     Western Digital My Passport (USB, AF)
>>> Device Model:     WDC WD20NMVW-11AV3S0
>>> ...
> 
> The "Model Family" info is printed from the drivedb.h entry which matches the "Device Model" string from ATA IDENTIFY data. The USB ID has no influence.
> 
> Some WD "Elements" and "My Passport" models use the same disk models. I decided to use the latter name in drivedb.h entries.

So, essentially this can be disregarded. But it is of course misleading. I guess I would have never realized that they share the same model without someone telling me so.

> 
>> Without -d sat:
>> 
>>> % smartctl -P show /dev/sdc
>>> smartctl 5.42 2011-10-20 r3458 [i686-linux-3.4.2-2-ARCH] (local build)
>>> Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net
>>> 
>>> /dev/sdc: Unknown USB bridge [0x1058:0x1048 (0x1022)]
>>> Smartctl: please specify device type with the -d option.
> 
> 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?

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

>>> ...
>> What is 0x1022 in parenthesis? Alternate iD? Should it ever be specified in drivedb.h?
> 
> This is the USB bcdDevice info. Only needed if different versions with same USB ID require different settings.

Got it. Good to know.

> 
> 
>> Also, after reading man smartctl about -B argument,  one question remains open. Is /etc/smart_drivedb.h used by default instead of builtin database, or one in /usr, or is information used to extend the existing database?
> 
> Entries in /etc/smart_drivedb.h are checked first and therefore could also be used to override entries in /usr/share/smartmontools.
> 

Thanks. Man pages got me lost a bit with all the fancy worded statements.

> 
>> Lastly, where would I submit this missing drive information to include in db file that is distributed with smartmontools?
> 
> Use drive database mailing list, see the FAQ.

Will do.

Ivan


------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT 
organizations don't have a clear picture of how application performance 
affects their revenue. With AppDynamics, you get 100% visibility into your 
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349351&iu=/4140/ostg.clktrk