Opened 9 years ago

Closed 9 years ago

#609 closed enhancement (fixed)

Unknown USB bridge 0bf6 :1001 USB 3.0 dock HDMU3 by Addonics Technologies, Inc.

Reported by: dockdock Owned by: Christian Franke
Priority: major Milestone: Release 6.5
Component: drivedb Version:
Keywords: Cc: emmanuel.manchester314@…

Description (last modified by Alex Samorukov)

Hello,

Could you please add support for this HDMU3 device USB bridge [0x0bf6:0x1001 (0x100)]
​http://www.addonics.com/datasheets/files/HDMU3.pdf

# smartctl --all  /dev/sdf
smartctl 6.4 2014-10-07 r4002 [x86_64-linux-3.16.0-4-amd64]
Copyright (C) 2002-14, Bruce Allen, Christian Franke, 

/dev/sdf: Unknown USB bridge [0x0bf6:0x1001 (0x100)]

This seems an unsupported external usb 3.0 dock (for 3.5 and 2.5'' HD)
 0bf6:1001 USB 3.0 dock by Addonics Technologies, Inc. 

I am running it on a PC with USB 2.0 only capability

Sep 12 19:16:19 localhost kernel: [46598.700030] usb 3-1: new high-speed USB device number 18 using ehci-pci
Sep 12 19:16:20 localhost kernel: [46598.838669] usb 3-1: New USB device found, idVendor=0bf6, idProduct=1001
Sep 12 19:16:20 localhost kernel: [46598.838674] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Sep 12 19:16:20 localhost kernel: [46598.838677] usb 3-1: Product: HDMU3
Sep 12 19:16:20 localhost kernel: [46598.838679] usb 3-1: Manufacturer: Addonics Technologies, Inc.
Sep 12 19:16:20 localhost kernel: [46598.838682] usb 3-1: SerialNumber: HDMU3000000015
Sep 12 19:16:20 localhost kernel: [46598.838962] usb-storage 3-1:1.0: USB Mass Storage device detected
Sep 12 19:16:20 localhost kernel: [46598.839072] scsi12 : usb-storage 3-1:1.0
Sep 12 19:16:20 localhost mtp-probe: checking bus 3, device 18: "/sys/devices/pci0000:00/0000:00:1a.7/usb3/3-1"
Sep 12 19:16:20 localhost mtp-probe: bus: 3, device: 18 was not an MTP device

Thanks

lsusb -vv

Bus 003 Device 018: ID 0bf6:1001 Addonics Technologies, Inc. 
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.10
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0        64
  idVendor           0x0bf6 Addonics Technologies, Inc.
  idProduct          0x1001 
  bcdDevice            1.00
  iManufacturer           1 Addonics Technologies, Inc.
  iProduct                2 HDMU3
  iSerial                 3 removed
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           32
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0xc0
      Self Powered
    MaxPower              100mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass         8 Mass Storage
      bInterfaceSubClass      6 SCSI
      bInterfaceProtocol     80 Bulk-Only
      iInterface              0 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x01  EP 1 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x82  EP 2 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0

Change History (22)

comment:1 by dockdock, 9 years ago 

# smartctl --all -d sat -T permissive /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

Read Device Identity failed: scsi error unsupported scsi opcode

=== START OF INFORMATION SECTION ===
Device Model:     [No Information Found]
Serial Number:    [No Information Found]
Firmware Version: [No Information Found]
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   [No Information Found]
Local Time is:    Sun Sep 13 08:22:57 2015 CEST
SMART support is: Ambiguous - ATA IDENTIFY DEVICE words 82-83 don't show if SMART supported.
SMART support is: Ambiguous - ATA IDENTIFY DEVICE words 85-87 don't show if SMART is enabled.
A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.
Last edited 9 years ago by Alex Samorukov (previous) (diff)

comment:2 by dockdock, 9 years ago

No luck with any of these options

# smartctl --all -d sat,12 -T permissive /dev/sdf
# smartctl --all -d sat,16 -T permissive /dev/sdf

 smartctl --all -d sat -T verypermissive /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

Read Device Identity failed: scsi error unsupported scsi opcode

=== START OF INFORMATION SECTION ===
Device Model:     [No Information Found]
Serial Number:    [No Information Found]
Firmware Version: [No Information Found]
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   [No Information Found]
Local Time is:    Sun Sep 13 08:31:25 2015 CEST
SMART support is: Ambiguous - ATA IDENTIFY DEVICE words 82-83 don't show if SMART supported.
SMART support is: Ambiguous - ATA IDENTIFY DEVICE words 85-87 don't show if SMART is enabled.
                  Checking to be sure by trying SMART RETURN STATUS command.
SMART support is: Unknown - Try option -s with argument 'on' to enable it.
Read SMART Data failed: scsi error unsupported scsi opcode

=== START OF READ SMART DATA SECTION ===
SMART Status command failed: scsi error unsupported scsi opcode
SMART overall-health self-assessment test result: UNKNOWN!
SMART Status, Attributes and Thresholds cannot be read.

Read SMART Error Log failed: scsi error unsupported scsi opcode

Read SMART Self-test Log failed: scsi error unsupported scsi opcode

Selective Self-tests/Logging not supported
Last edited 9 years ago by Alex Samorukov (previous) (diff)

comment:3 by Alex Samorukov, 9 years ago

Description: modified (diff)

comment:4 by Alex Samorukov, 9 years ago

Are you aware of any proprietary tool (or specification) to show smart information on this device? It seems that SAT protocol is not supported to the chip.

comment:5 by dockdock, 9 years ago

Cc: emmanuel.manchester314@… added

Hi, thanks,

Sorry I do not understand the question.
I should have said sata HD can be seen and accessed ok.
This a docking station, I cannot access the chip for information
without using linux tools (I am under linux only).
Will nevertheless dig the cdrom that came with the dock
to look for specs, and proprietary tool.
Maybe I understand your question now.

# fdisk -l /dev/sdf
Disk /dev/sdf: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
blabla partitions list

I can mount the partitions of the sata 3.5 WD green inside the dock
and I get 

# hdparm -I /dev/sdf

/dev/sdf:
SG_IO: bad/missing sense data, sb[]:  70 00 05 00 00 00 00 0a 00 00 00 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

ATA device, with non-removable media
        Model Number:       ����'���'����@'����x'���Ͱ'�
        Serial Number:      �����'���ʠ'���
        Firmware Revision:  ���0'�
Standards:
        Used: unknown (minor revision code 0x0427) 
        Supported: 14 11 10 9 8 7 5 
        Likely used: 14
Configuration:
        Logical         max     current
        cylinders       0       59904
        heads           0       65535
        sectors/track   510     52824
        --
        CHS current addressable sectors: 3925869607
        Logical/Physical Sector size:           512 bytes
        device size with M = 1024*1024:     1916928 MBytes
        device size with M = 1000*1000:     2010045 MBytes (2010 GB)
        cache/buffer size  = unknown
Capabilities:
        IORDY(may be)(can be disabled)
        Queue depth: 32
        Standby timer values: spec'd by Vendor
        R/W multiple sector transfer: Max = 255 Current = 255
        Recommended acoustic management value: 234, current value: 0
        DMA: not supported
        PIO: pio0 pio1 pio2 pio6 
             Cycle time: no flow control=65535ns  IORDY flow control=52992ns
           *    reserved 69[0]
           *    reserved 69[1]
           *    reserved 69[2]
           *    WRITE BUFFER DMA command
Security: 
        Master password revision code = 53328
        not     supported
        not     enabled
        not     locked
                frozen
        not     expired: security count
        not     supported: enhanced erase
Logical Unit WWN Device Identifier: removed
        NAA             : d
        IEEE OUI        : 130042
        Unique ID       : removed
Integrity word not set (found 0x0000, expected 0xc7a5)
Last edited 9 years ago by dockdock (previous) (diff)

comment:6 by dockdock, 9 years ago

I bought this sept 2015

only one tool on cdrom :
BX-D3002U3_um_Prolific_Backup_Windows_02-12-2011 .exe

and 1 manual pdf for the exe, entitled :
Prolific USB to SATA Bridge Controller
Backup Software User’s Manual
For Windows XP/Vista/7
For Software version 3.9.2.00 (6/28/2011)

Nothing technical : The most tech part is :
<<You can easily open the Prolific Backup software by double-clicking on the
Prolific PL2X7X OneButton icon found on the system tray of your taskbar. You
can also click Start-Programs-Prolific Storage-PLBackup to quick launch ...>>

Last edited 9 years ago by dockdock (previous) (diff)

comment:7 by dockdock, 9 years ago

lsusb -vvv

Bus 001 Device 003: ID 0bf6:1001 Addonics Technologies, Inc. 
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.10
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0        64
  idVendor           0x0bf6 Addonics Technologies, Inc.
  idProduct          0x1001 
  bcdDevice            1.00
  iManufacturer           1 Addonics Technologies, Inc.
  iProduct                2 HDMU3
  iSerial                 3 HDMU3 blabla
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           32
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0xc0
      Self Powered
    MaxPower              100mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass         8 Mass Storage
      bInterfaceSubClass      6 SCSI
      bInterfaceProtocol     80 Bulk-Only
      iInterface              0 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x01  EP 1 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x82  EP 2 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
Binary Object Store Descriptor:
  bLength                 5
  bDescriptorType        15
  wTotalLength           22
  bNumDeviceCaps          2
  USB 2.0 Extension Device Capability:
    bLength                 7
    bDescriptorType        16
    bDevCapabilityType      2
    bmAttributes   0x00000002
      Link Power Management (LPM) Supported
  SuperSpeed USB Device Capability:
    bLength                10
    bDescriptorType        16
    bDevCapabilityType      3
    bmAttributes         0x00
    wSpeedsSupported   0x000e
      Device can operate at Full Speed (12Mbps)
      Device can operate at High Speed (480Mbps)
      Device can operate at SuperSpeed (5Gbps)
    bFunctionalitySupport   1
      Lowest fully-functional device speed is Full Speed (12Mbps)
    bU1DevExitLat          10 micro seconds
    bU2DevExitLat        2047 micro seconds
Device Status:     0x0001
  Self Powered
Last edited 9 years ago by dockdock (previous) (diff)

comment:8 by dockdock, 9 years ago

Specs from ​http://www.addonics.com/products/hdmu3.php

Writing mode : Sector to Sector
Typical transfer rate ~ 65 MB/sec
Two drives slot to accomodate 3.5" or 2.5" SATA HDD/SSD
Clone button
Backup button
Eject buttons for each drive slot
USB 3.0 type B female connector
Four LEDs to display % completion during the duplication process
Activity LED for each Drive
Power ON/OFF switch and status LED
Low power consumption: < 250 mA at 5V (excluding hard drives)
110/240V power adapter
Operating environment: 0 - 50 degree C, 15% - 90% RH
Storage environment: (- 20) - (65) degree C, 0% - 95% RH non-condensing

comment:9 by dockdock, 9 years ago

Are you aware of any proprietary tool (or specification)
to show smart information on this device?

No I am not, and I am not technically clued up enough for that

It seems that SAT protocol is not supported to the chip.

At least the smart part is not

This does not pass through either

# idle3ctl -g103 /dev/sdf
 HDIO_DRIVE_CMD(identify) failed: Invalid argument

I have contacted customer support by pointing to this thread and
asking to help /provide support.
So please ask questiosn here to them (please make clear if
question is for me (user) or them (manufacturer)
(I will post questions back on the customer support site if needed)

Last edited 9 years ago by dockdock (previous) (diff)

comment:10 by dockdock, 9 years ago

USB ID was missing from
​http://www.linux-usb.org/usb.ids
I submitted a patch

comment:11 by Alex Samorukov, 9 years ago

It is not possible to add support for this chip without specification from vendor (or with reverse engineering vendor tool, if it exists).

Version 0, edited 9 years ago by Alex Samorukov (next)

comment:12 by dockdock, 9 years ago

Ok, thanks, I will let you know what the vendor says.
Is there a way to tell with linux tools which chip is inside the USB bridge ?

in reply to:  12 comment:13 by Alex Samorukov, 9 years ago

Replying to dockdock:

Ok, thanks, I will let you know what the vendor says.
Is there a way to tell with linux tools which chip is inside the USB bridge ?

Probably only by VID/PID from lsusb.

comment:14 by dockdock, 9 years ago

Thanks.
lsusb -vvv already posted.
No news from vendor so far.
I will post whenever I have something new,
I registered with the thread so I will keep an eye on it.

comment:15 by dockdock, 9 years ago

here is the answer from tech support :
(I replied and asked for the exact model)

We don't know if the HDMU3 support passing through smart command.
The bridge inside is from JMicron.

comment:16 by Alex Samorukov, 9 years ago

Resolution: → wontfix
Status: new → closed
Version: 6.4

Unsupported controller without specification. Feel free to re-open this ticket if you will find a way to get s.m.a.r.t. data from the drive.

in reply to:  15 comment:17 by Christian Franke, 9 years ago

Replying to dockdock:

here is the answer from tech support :
...

The bridge inside is from JMicron.

Please try:

smartctl -d usbjmicron -x /dev/sdf

If it works try also with 48-bit support enabled:

smartctl -d usbjmicron,x -x /dev/sdf

If at least the first command works, reopen this ticket and attach smartctl output.

comment:18 by dockdock, 9 years ago

Should I reopen the thread ? (By the way the HD is smart capable, no doubt of that,
the previous dock that died was smart pass-through capable)

# smartctl -d usbjmicron -x /dev/sdf

smartctl 6.4 2014-10-07 r4002 [x86_64-linux-3.16.0-4-amd64] (local build)

Smartctl open device: /dev/sdf [USB JMicron] failed: scsi error unsupported scsi opcode

# smartctl -d usbjmicron,x -x -T verypermissive /dev/sdf

smartctl 6.4 2014-10-07 r4002 [x86_64-linux-3.16.0-4-amd64] (local build)
Smartctl open device: /dev/sdf [USB JMicron] failed: scsi error unsupported scsi opcode

It is a two-bay docks (same results with 0 or 1 AFAIK)
# smartctl -d usbjmicron,x,0 -x -T verypermissive /dev/sdf

smartctl 6.4 2014-10-07 r4002 [x86_64-linux-3.16.0-4-amd64] (local build)

Read Device Identity failed: scsi error unsupported scsi opcode

=== START OF INFORMATION SECTION ===
Device Model:     ��X�
Serial Number:    �
Firmware Version: ��V`
Form Factor:      Unknown (0x2e98)
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   Unknown(0x6c68), ATA8-ACS T13/1699-D revision 6
Local Time is:    Tue Sep 22 20:44:44 2015 CEST
SMART support is: Ambiguous - ATA IDENTIFY DEVICE words 82-83 don't show if SMART supported.
SMART support is: Ambiguous - ATA IDENTIFY DEVICE words 85-87 don't show if SMART is enabled.
                  Checking to be sure by trying SMART RETURN STATUS command.
SMART support is: Unknown - Try option -s with argument 'on' to enable it.AAM feature is:   Unavailable
APM feature is:   Unavailable
Rd look-ahead is: Unavailable
Write cache is:   Unavailable
ATA Security is:  Unavailable
Wt Cache Reorder: Unavailable

Read SMART Data failed: scsi error unsupported scsi opcode
Truncated lines after
Last edited 9 years ago by dockdock (previous) (diff)

comment:19 by Christian Franke, 9 years ago

Component: all → drivedb
Milestone: → Release 6.5

Could only be added as unsupported to drivedb.h.

comment:20 by Christian Franke, 9 years ago

Resolution: wontfix
Status: closed → reopened

comment:21 by Christian Franke, 9 years ago

Owner: set to Christian Franke
Status: reopened → accepted

comment:22 by Christian Franke, 9 years ago

Resolution: → fixed
Status: accepted → closed

r4132, r4133.

Note: See TracTickets for help on using tickets.