Re: Improving on the output of a USB bridge (0x1f75:0x0611 (0x006)]

Rich wrote:
> Hi all,
> So, I noticed that smartctl has learned to use -d sat between the last
> time I had updated drivedb.h and now; however, this still fails to
> successfully detect a number of parameters that work under -d sat,12:
>
> For example:
>
> === BEGIN SMART -d sat OUTPUT ===
>
> # smartctl -x -d sat /dev/sdf
> smartctl 6.4 2014-10-07 r4002 [x86_64-linux-3.16.0-4-amd64] (local build)
> Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org
>
> === START OF INFORMATION SECTION ===
> Model Family:     Seagate Barracuda 7200.10
> Device Model:     ST3500630A
> ...
> Read SMART Data failed: scsi error unsupported scsi opcode
> ...
> Read SMART Log Directory failed: scsi error unsupported scsi opcode
> ...
> === END SMART -d sat OUTPUT ===
>
> == BEGIN SMART -d sat,12 OUTPUT ===
>
> # smartctl -x -d sat,12 /dev/sdf
> smartctl 6.4 2014-10-07 r4002 [x86_64-linux-3.16.0-4-amd64] (local build)
> Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org
>
> === START OF INFORMATION SECTION ===
> Model Family:     Seagate Barracuda 7200.10
> Device Model:     ST3500630A
> ...
> General SMART Values:
> ...
> SMART Attributes Data Structure revision number: 10
> Vendor Specific SMART Attributes with Thresholds:
> ID# ATTRIBUTE_NAME          FLAGS    VALUE WORST THRESH FAIL RAW_VALUE
>    1 Raw_Read_Error_Rate     POSR--   119   097   006    -    0
> ...
> SMART Log Directory Version 1 [multi-sector log support]
> Address    Access  R/W   Size  Description
> 0x00           SL  R/O      1  Log Directory
> 0x01           SL  R/O      1  Summary SMART error log
> ...
> === END SMART -d sat,12 OUTPUT ===

Apparently -d sat only supports ATA IDENTIFY command, -d sat,12 also 
supports SMART READ commands but not SMART STATUS.


> The relevant entry seems to be:
>    // Innostor
>    { "USB: ; Innostor IS611", // USB3->SATA+PATA
>      "0x1f75:0x0611", // SMART access via PATA does not work
>      "",
>      "",
>      "-d sat"
>    },

This entry was the result from this older submission which only tested 
-d sat but with both SATA and PATA drives:
http://sourceforge.net/p/smartmontools/mailman/message/31337694/

The result from your -d sat test with this PATA drive is similar.

Changing the drivedb entry to -d sat,12 would remove 48-bit support for 
SATA drives but would add basic SMART support for PATA drives.

Could you possibly test -d sat,12 with a SATA drive connected to this 
bridge?

Thanks,
Christian


------------------------------------------------------------------------------