Opened 6 years ago

Closed 6 years ago

#327 closed enhancement (wontfix)

StarTech USB SATDOCK2REU3 (Prolific PL2775 chipset) support?

Reported by: stephendowdy Owned by: somebody
Priority: major Milestone:
Component: drivedb Version: 6.2
Keywords: Cc:

Description

StarTech? USB SATDOCK2REU3 uses the Prolific PL2775 chipset. I am aware of the following:

(http://sourceforge.net/wiki)
(http://sourceforge.net/wiki/USB)
(http://sourceforge.net/p/smartmontools/mailman/message/29528679/)

So, understand the issue with Prolific in general from a support standpoint, but am just formally registering my desire that this chipset get support (or to ask if a decent alternative supportable solution is recommended). I bought this device in order to do tests of questionable drives, and perform erases (and maybe duplicate in standalone mode) from my Debian Wheezy Linux workstation.


Default behavior:

zia:~# /usr/local/smartmontools-6.2/sbin/smartctl -H /dev/sdg
smartctl 6.2 2013-07-26 r3841 [x86_64-linux-3.2.0-4-amd64] (local build)
Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org


/dev/sdg: Unknown USB bridge [0x067b:0x2775 (0x100)]


Can at least get a bit of SCSI INQUIRY info, but interestingly, the Vendor+Product fields are getting mangled.
First case, vendor should be "WDC", Product should be "WD1003FBYX-01Y7B2"
second case, vendor should be "Hitachi" (or HDS?), product should be "HDS725050KLA360".
But, that's not from 'smartctl', it's that way from 'sgutils', too:

zia:StarTech_SATDOCK2REU3# sg_inq /dev/sdg | grep ident

Vendor identification: WDC WD10
Product identification: 03FBYX-01Y7B2

zia:StarTech_SATDOCK2REU3# /usr/local/smartmontools-6.2/sbin/smartctl -d sat,auto -T permissive -a /dev/sdg
smartctl 6.2 2013-07-26 r3841 [x86_64-linux-3.2.0-4-amd64] (local build)
Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org

/dev/sdg [SCSI]: Device open changed type from 'sat,auto' to 'scsi'

START OF INFORMATION SECTION

Vendor: WDC WD10
Product: 03FBYX-01Y7B2
Revision: 01.0
User Capacity: 1,000,204,886,016 bytes [1.00 TB]
Logical block size: 512 bytes
scsiModePageOffset: response length too short, resp_len=4 offset=4 bd_len=0
scsiModePageOffset: response length too short, resp_len=4 offset=4 bd_len=0

Terminate command early due to bad response to IEC mode page

START OF READ SMART DATA SECTION

Error Counter logging not supported

scsiModePageOffset: response length too short, resp_len=4 offset=4 bd_len=0
Device does not support Self Test logging

(other (second) device on SATDOCK:)

START OF INFORMATION SECTION

Vendor: HDS72505
Product: 0KLA360
Revision: K2AO
User Capacity: 500,107,862,016 bytes [500 GB]
Logical block size: 512 bytes

am attaching the 'lsusb' and 'smartctl -rioctl,9999' output

thanks,
--stephen

Attachments (2)

ioctl-report.log (5.0 KB) - added by stephendowdy 6 years ago.
/usr/local/smartmontools-6.2/sbin/smartctl -r ioctl,9999 -d sat,auto -T permissive -a /dev/sdg > ioctl-report.log
lsusb.log (2.0 KB) - added by stephendowdy 6 years ago.
lsusb -v -d 067b:2775

Download all attachments as: .zip

Change History (5)

Changed 6 years ago by stephendowdy

Attachment: ioctl-report.log added

/usr/local/smartmontools-6.2/sbin/smartctl -r ioctl,9999 -d sat,auto -T permissive -a /dev/sdg > ioctl-report.log

Changed 6 years ago by stephendowdy

Attachment: lsusb.log added

lsusb -v -d 067b:2775

comment:1 Changed 6 years ago by Christian Franke

Component: smartctldrivedb
Keywords: usb startech satdock prolific pl2775 removed

Option "-d sat,auto" does not detect SAT capable USB Bridges because normally these do not return a SAT compatible SCSI INQUIRY result ("ATA ").

Some Prolific USB bridges support a variant of the JMicron vendor specific protocol, see smartctl man page.

Please try:

  smartctl -d usbjmicron,0 ...
  smartctl -d usbjmicron,p ...
  smartctl -d sat,12 ...
  smartctl -d sat ...

(Make sure to use attachments for sample outputs).

If none of the above works, there is no known pass-through command for this USB bridge.

comment:2 in reply to:  1 Changed 6 years ago by stephendowdy

Replying to chrfranke:

Option "-d sat,auto" does not detect SAT capable USB Bridges because normally these do not return a SAT compatible SCSI INQUIRY result ("ATA ").

Some Prolific USB bridges support a variant of the JMicron vendor specific protocol, see smartctl man page.

Please try:

  smartctl -d usbjmicron,0 ...
  smartctl -d usbjmicron,p ...
  smartctl -d sat,12 ...
  smartctl -d sat ...

(Make sure to use attachments for sample outputs).

If none of the above works, there is no known pass-through command for this USB bridge.

All '-d' device type variants return:

    Read Device Identity failed: scsi error unsupported scsi opcode
# lsscsi | grep WDC
[7:0:0:1]    disk    WDC WD10 03FBYX-01Y7B2    01.0  /dev/sdc
# for dt in usbjmicron,0 usbjmicron,p sat,12 sat; do echo "[${dt}]"; smartctl -d ${dt} -A /dev/sdc | tail -n +4 | tr -s '\n'; done
[usbjmicron,0]
Read Device Identity failed: scsi error unsupported scsi opcode
A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.
[usbjmicron,p]
Read Device Identity failed: scsi error unsupported scsi opcode
A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.
[sat,12]
Read Device Identity failed: scsi error unsupported scsi opcode
A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.
[sat]
Read Device Identity failed: scsi error unsupported scsi opcode
A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.

So, i guess this device is just not going to be usable for the function i'd hoped :-(

Thanks,
--stephen

comment:3 Changed 6 years ago by Christian Franke

Resolution: wontfix
Status: newclosed

This USB bridge does not implement the ATA pass-through SCSI commands supported by other Prolific USB bridges. It may implement another vendor-specific command. Adding this to smartmontools would require documentation from the vendor.

Please reopen this ticket if you could provide such info or if any other smartctl -d options (usbcypress, usbsunplus) work.

Note: See TracTickets for help on using tickets.