Bug 169954 - [umass] [patch] Western Digital My Passport : (da1:umass-sim1:1:0:0): fatal error, failed to attach to device
Summary: [umass] [patch] Western Digital My Passport : (da1:umass-sim1:1:0:0): fatal e...
Status: Open
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: 9.0-RELEASE
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-bugs mailing list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-07-18 00:00 UTC by Jerome Lebel
Modified: 2018-01-03 05:16 UTC (History)
0 users

See Also:


Attachments
smime.p7s (6.00 KB, application/x-pkcs7-signature)
2012-11-22 20:11 UTC, johan
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jerome Lebel 2012-07-18 00:00:22 UTC
Each time I plug my new western digital drive My Passport (USB 3) on my D2700DC motherboard (USB2), I get this error message :

ugen4.5: <Western Digital> at usbus4
umass1: <MSC Bulk-Only Transport> on usbus4
umass1:  SCSI over Bulk-Only; quirks = 0x4001
umass1:9:1:-1: Attached to scbus9
(da1:umass-sim1:1:0:0): got CAM status 0x4
(da1:umass-sim1:1:0:0): fatal error, failed to attach to device
(da1:umass-sim1:1:0:0): lost device - 0 outstanding
(da1:umass-sim1:1:0:0): removing device entry
freebsd-test16# uname -a
FreeBSD freebsd-test16 9.0-RELEASE-p3 FreeBSD 9.0-RELEASE-p3 #0: Tue Jun 12 02:52:29 UTC 2012     root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC  amd64

Let me know if I can add more information.

How-To-Repeat: Boot a freebsd 9.0-RELEASE-p3
Plug a western digital My Passport USB 3 1TB
Comment 1 staff 2012-07-18 16:50:07 UTC
The model number is : wdbbep001bbk
Comment 2 ctineo 2012-11-05 14:37:40 UTC
Same problem here with WD My Passport 2TB USB 3.0 (connected to USB 2.0 port) - it works fine when connected to a windows or mac machine but once plugged into a freebsd box (using 9.1 rc3) - it gives the following messages and the drive is not made available to the os for gpart or other...

Nov  5 15:18:11 ABCH025 kernel: ugen1.2: <Western Digital> at usbus1
Nov  5 15:18:11 ABCH025 kernel: umass0: <MSC Bulk-Only Transport> on usbus1
Nov  5 15:18:11 ABCH025 kernel: umass0:  SCSI over Bulk-Only; quirks = 0x4001
Nov  5 15:18:11 ABCH025 kernel: umass0:7:0:-1: Attached to scbus7
Nov  5 15:18:19 ABCH025 kernel: (da0:umass-sim0:0:0:0): got CAM status 0x4
Nov  5 15:18:19 ABCH025 kernel: (da0:umass-sim0:0:0:0): fatal error, failed to attach to device
Nov  5 15:18:19 ABCH025 kernel: (da0:umass-sim0:0:0:0): lost device - 0 outstanding, 4 refs
Nov  5 15:18:19 ABCH025 kernel: (da0:umass-sim0:0:0:0): removing device entry
Nov  5 15:18:20 ABCH025 kernel: (probe0:umass-sim0:0:0:1): INQUIRY. CDB: 12 0 0 0 24 0 
Nov  5 15:18:20 ABCH025 kernel: (probe0:umass-sim0:0:0:1): CAM status: CCB request completed with an error
Nov  5 15:18:20 ABCH025 kernel: (probe0:umass-sim0:0:0:1): Retrying command
Nov  5 15:18:20 ABCH025 kernel: (probe0:umass-sim0:0:0:1): INQUIRY. CDB: 12 0 0 0 24 0 
Nov  5 15:18:20 ABCH025 kernel: (probe0:umass-sim0:0:0:1): CAM status: CCB request completed with an error
Nov  5 15:18:20 ABCH025 kernel: (probe0:umass-sim0:0:0:1): Retrying command
Nov  5 15:18:21 ABCH025 kernel: (probe0:umass-sim0:0:0:1): INQUIRY. CDB: 12 0 0 0 24 0 
Nov  5 15:18:21 ABCH025 kernel: (probe0:umass-sim0:0:0:1): CAM status: CCB request completed with an error
Nov  5 15:18:21 ABCH025 kernel: (probe0:umass-sim0:0:0:1): Retrying command
Nov  5 15:18:21 ABCH025 kernel: (probe0:umass-sim0:0:0:1): INQUIRY. CDB: 12 0 0 0 24 0 
Nov  5 15:18:21 ABCH025 kernel: (probe0:umass-sim0:0:0:1): CAM status: CCB request completed with an error
Nov  5 15:18:21 ABCH025 kernel: (probe0:umass-sim0:0:0:1): Retrying command
Nov  5 15:18:22 ABCH025 kernel: (probe0:umass-sim0:0:0:1): INQUIRY. CDB: 12 0 0 0 24 0 
Nov  5 15:18:22 ABCH025 kernel: (probe0:umass-sim0:0:0:1): CAM status: CCB request completed with an error
Nov  5 15:18:22 ABCH025 kernel: (probe0:umass-sim0:0:0:1): Error 5, Retries exhausted

root@ABCH025:/ # uname -a
FreeBSD ABCH025 9.1-RC3 FreeBSD 9.1-RC3 #0 r242324: Tue Oct 30 00:58:57 UTC 2012     root@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC  amd64



Cédric Tineo
Digital Light SA
tel: +41 22 548 19 21
mobile: +41 79 579 19 41
skype: cedrictineo
web: http://www.digital-light.ch
Comment 3 ctineo 2012-11-05 15:30:04 UTC
We are ready to donate and ship one of those WD 2TB 2,5" usb3 drives to someone needing access to it to create a fix !

Cédric Tineo
Comment 4 johan 2012-11-23 08:00:40 UTC
Sorry for the terrible smime attachments... I didn't realize Evolution
signed everything by default if you have a S/MIME cert.
Comment 5 David Thiel freebsd_committer 2012-12-20 23:22:15 UTC
Iâd speculate that the âMYPASSWORDâ entry is just a typo for MYPASSPORT, 
so that line should probably just be changed instead of adding a second 
quirk.
Comment 6 johan 2012-12-29 16:24:59 UTC
No I don't think so, MyPassword seems to be a password
protected/encrypted version of MyPassport. Anyway, it has a different
product ID (MYPASSWORD=0x0704, MYPASSPORT=0x0748) so simply changing the
name won't be sufficient.
Comment 7 Anish Mistry 2013-02-02 18:21:53 UTC
This quirk works.  You can accomplish the same thing manually:
usbconfig -d 5.4 add_quirk UQ_MSC_FORCE_SHORT_INQ
usbconfig -d 5.4 reset

"5.4" should be the device location of your drive.

-- 
Anish Mistry
Comment 8 hannes 2013-04-22 08:35:02 UTC
The patch works for me fine. I'd appreciate this patch to be applied to
HEAD.

Cheers,

Hannes
Comment 9 hannes 2013-04-22 09:06:06 UTC
Actually, using the patch I have to manually send a reset to the usb
device before it shows up, otherwise I get the error reported initially.

Hannes
Comment 10 Dan Lukes 2013-07-06 20:28:39 UTC
Duplicate of kern/178771

Quirk UQ_MSC_FORCE_SHORT_INQ doesn't help for device 0x0748
quirk UQ_MSC_NO_SYNC_CACHE solve the problem with such device.

Dan
Comment 11 Eitan Adler freebsd_committer freebsd_triage 2017-12-31 08:00:26 UTC
For bugs matching the following criteria:

Status: In Progress Changed: (is less than) 2014-06-01

Reset to default assignee and clear in-progress tags.

Mail being skipped