[smartmontools-support] Device is not in smartctl database. Consequences and solution?

Discussion:

Ivan Lezhnjov Jr.

2013-11-29 15:18:23 UTC

Hello,

what are the consequences of when a drive is not in smartctl database?

Can this database be updated somehow? Can it be updated independently or would I need to update the whole smartmontools package as well?

% smartctl -i /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.
Use smartctl -h to get a usage summary
% 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 ===
Device Model: WDC WD20NMVW-11AV3S0
Serial Number: WD-WX91E13UJK20
LU WWN Device Id: 5 0014ee 208783119
Firmware Version: 01.01A01
User Capacity: 2,000,398,934,016 bytes [2.00 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: 8
ATA Standard is: ACS-2 (revision not indicated)
Local Time is: Fri Nov 29 17:14:05 2013 EET
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

Ivan

Adam Piggott

2013-11-29 15:51:14 UTC

Permalink

Post by Ivan Lezhnjov Jr.
Hello,
what are the consequences of when a drive is not in smartctl database?
Can this database be updated somehow? Can it be updated independently or
would I need to update the whole smartmontools package as well?

See section three of the FAQ:
http://sourceforge.net/apps/trac/smartmontools/wiki/FAQ

--
Adam Piggott, Proprietor
Proactive Services (Computing)
http://proactiveservices.co.uk/

Ivan Lezhnjov Jr.

2013-11-29 18:43:19 UTC

Permalink

Post by Adam Piggott

http://sourceforge.net/apps/trac/smartmontools/wiki/FAQ

Unfortunately, it did not work:

% /usr/sbin/update-smart-drivedb -v
Download from branches/RELEASE_5_42_DRIVEDB
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 329 100 329 0 0 764 0 --:--:-- --:--:-- --:--:-- 1981
/usr/share/smartmontools/drivedb.h.error: rejected by /usr/sbin/smartctl, probably no longer compatible

Any workarounds or do I need to update smartmontools as well?

Ivan

Christian Franke

2013-11-29 21:22:57 UTC

Permalink

Post by Ivan Lezhnjov Jr.

Post by Adam Piggott

http://sourceforge.net/apps/trac/smartmontools/wiki/FAQ

% /usr/sbin/update-smart-drivedb -v
Download from branches/RELEASE_5_42_DRIVEDB
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 329 100 329 0 0 764 0 --:--:-- --:--:-- --:--:-- 1981
/usr/share/smartmontools/drivedb.h.error: rejected by /usr/sbin/smartctl, probably no longer compatible
Any workarounds or do I need to update smartmontools as well?

This does no longer work because sourceforge moved our SVN repository to
a new location.

Try "Download this file" link here:
http://sourceforge.net/p/smartmontools/code/HEAD/tree/branches/RELEASE_5_42_DRIVEDB/smartmontools/drivedb.h
and move the downloaded drivedb.h to /usr/share/smartmontools (or
another configured location, see -B option on man page).

If SVN client is installed, you could also use:
svn export
http://svn.code.sf.net/p/smartmontools/code/branches/RELEASE_5_42_DRIVEDB/smartmontools/drivedb.h

For still missing entries, you could add a local drive database entry
(usually) at /etc/smartd_drivedb.h.

Thanks,
Christian

Ivan Lezhnjov Jr.

2013-11-30 08:03:36 UTC

Permalink

Post by Ivan Lezhnjov Jr.

Post by Adam Piggott

http://sourceforge.net/apps/trac/smartmontools/wiki/FAQ

This does no longer work because sourceforge moved our SVN repository to a new location.
http://sourceforge.net/p/smartmontools/code/HEAD/tree/branches/RELEASE_5_42_DRIVEDB/smartmontools/drivedb.h
and move the downloaded drivedb.h to /usr/share/smartmontools (or another configured location, see -B option on man page).
svn export http://svn.code.sf.net/p/smartmontools/code/branches/RELEASE_5_42_DRIVEDB/smartmontools/drivedb.h
For still missing entries, you could add a local drive database entry (usually) at /etc/smartd_drivedb.h.

No luck.

localhost kernel: [547111.752845] scsi 46:0:0:0: Direct-Access WD Elements 1048 1022 PQ: 0 ANSI: 6
% 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
...
% 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.
Use smartctl -h to get a usage summary

So, after reviewing drivedb.h it looks like I need to create a new entry. I came up with this

{ "USB: WD Elements 1048; ",
"0x1058:0x1048",
"",
"",
"-d sat"
},

What is 0x1022 in parenthesis? Alternate iD? Should it ever be specified in drivedb.h?

% smartctl -i /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
% grep "1058:" /usr/share/smartmontools/drivedb.h
"0x1058:0x0701",
"0x1058:0x0702",
"0x1058:0x0704",
"0x1058:0x0705",
"0x1058:0x070a",
"0x1058:0x0730",
"0x1058:0x074[02]",
"0x1058:0x07[4a]8",
"0x1058:0x0906",
"0x1058:0x0910",
"0x1058:0x1001",
"0x1058:0x1003",
"0x1058:0x10(10|a2)",
"0x1058:0x1021",
"0x1058:0x1023",
"0x1058:0x1042",
"0x1058:0x1100",
"0x1058:0x1101",
"0x1058:0x1102",
"0x1058:0x1105",
"0x1058:0x1110",
"0x1058:0x11[34]0",

The same happens if I add new entry to /usr/share/smartmontools/drivedb.h

% lsusb
Bus 001 Device 035: ID 1058:1048 Western Digital Technologies, Inc.
Bus 001 Device 036: ID 1058:1048 Western Digital Technologies, Inc.

and

% lsusb --verbose -s 001:035
Bus 001 Device 035: ID 1058:1048 Western Digital Technologies, Inc.
bLength 18
bDescriptorType 1
bcdUSB 2.10
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x1058 Western Digital Technologies, Inc.
idProduct 0x1048
bcdDevice 10.22
iManufacturer 1 Western Digital
iProduct 2 Elements 1048

So, it looks to me like my configuration is correct. I even tried specifying bcdDevice but that didn't change anything.

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?

Lastly, where would I submit this missing drive information to include in db file that is distributed with smartmontools?

Ivan

Christian Franke

2013-11-30 18:31:11 UTC

Permalink

Post by Ivan Lezhnjov Jr.

..
For still missing entries, you could add a local drive database entry (usually) at /etc/smartd_drivedb.h.

No luck.

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.

Post by Ivan Lezhnjov Jr.

% 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.

Post by Ivan Lezhnjov Jr.

...

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.

Post by Ivan Lezhnjov Jr.
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.

Post by Ivan Lezhnjov Jr.
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.

Thanks,
Christian

Ivan Lezhnjov Jr.

2013-12-01 11:34:59 UTC

Permalink

Post by Ivan Lezhnjov Jr.

..
For still missing entries, you could add a local drive database entry (usually) at /etc/smartd_drivedb.h.

No luck.

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.

Post by Ivan Lezhnjov Jr.

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?

Post by Ivan Lezhnjov Jr.

...

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.

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.

Post by Ivan Lezhnjov Jr.
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

Ivan Lezhnjov Jr.

2013-12-07 12:41:45 UTC

Permalink

Bumping my question with the hope to get an answer :)

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.

Christian Franke

2013-12-07 14:48:38 UTC

Permalink

Post by Ivan Lezhnjov Jr.

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.

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

Post by Ivan Lezhnjov Jr.
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

Ivan Lezhnjov Jr.

2013-12-13 07:47:52 UTC

Permalink

Post by Ivan Lezhnjov Jr.

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.

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).
http://sourceforge.net/apps/trac/smartmontools/wiki/Links#ATAATAPIReferences

Good to know. Thanks Chris.

Post by Ivan Lezhnjov Jr.
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.
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.

I have just received (finally!) a reply from WD support and they've escalated my ticket that requests authoritative explanation on how to interpret SMART attributes data for WD Elements 1048 drives. Would the developers of smartmontools be interested in getting a copy of it once, and if, I obtain it? If so, where would I submit it?

Ivan