Date: Wed, 17 Apr 2013 05:27:08 GMT From: Leif Velcro <velcroleaf@rocketmail.com> To: freebsd-gnats-submit@FreeBSD.org Subject: usb/177895: similar 1TB Western Digital "My Passports" - some load, some don't Message-ID: <201304170527.r3H5R8fG069788@red.freebsd.org> Resent-Message-ID: <201304170530.r3H5U2bE056527@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 177895 >Category: usb >Synopsis: similar 1TB Western Digital "My Passports" - some load, some don't >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-usb >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Wed Apr 17 05:30:01 UTC 2013 >Closed-Date: >Last-Modified: >Originator: Leif Velcro >Release: 9.1-RELEASE-p2 >Organization: >Environment: FreeBSD asystem.here.com 9.1-RELEASE-p2 FreeBSD 9.1-RELEASE-p2 #0: Tue Apr 9 12:16:09 EDT 2013 root@asystem.here.com:/usr/obj/usr/src/sys/asystem i386 >Description: I have several Western Digital "My Passports". They are 1TB external USB drives, all the same model (except for external color). When I connect some of them, the system is happy and says this: ugen1.2: <Western Digital> at usbus1 umass0: <MSC Bulk-Only Transport> on usbus1 umass0: SCSI over Bulk-Only; quirks = 0x0000 umass0:3:0:-1: Attached to scbus3 da0 at umass-sim0 bus 0 scbus3 target 0 lun 0 da0: <WD My Passport 0748 1019> Fixed Direct Access SCSI-6 device da0: 1.000MB/s transfers da0: 953837MB (1953458176 512 byte sectors: 255H 63S/T 121597C) ses0 at umass-sim0 bus 0 scbus3 target 0 lun 1 ses0: <WD SES Device 1019> Fixed Enclosure Services SCSI-6 device ses0: 1.000MB/s transfers ses0: SCSI-3 SES Device When I connect others, the system is sad and says this: ugen1.2: <Western Digital> at usbus1 umass0: <MSC Bulk-Only Transport> on usbus1 umass0: SCSI over Bulk-Only; quirks = 0x4001 umass0:3:0:-1: Attached to scbus3 (da0:umass-sim0:0:0:0): got CAM status 0x4 (da0:umass-sim0:0:0:0): fatal error, failed to attach to device (da0:umass-sim0:0:0:0): lost device - 0 outstanding, 4 refs (da0:umass-sim0:0:0:0): removing device entry (probe0:umass-sim0:0:0:1): INQUIRY. CDB: 12 0 0 0 24 0 (probe0:umass-sim0:0:0:1): CAM status: CCB request completed with an error (probe0:umass-sim0:0:0:1): Retrying command (probe0:umass-sim0:0:0:1): INQUIRY. CDB: 12 0 0 0 24 0 (probe0:umass-sim0:0:0:1): CAM status: CCB request completed with an error (probe0:umass-sim0:0:0:1): Retrying command (probe0:umass-sim0:0:0:1): INQUIRY. CDB: 12 0 0 0 24 0 (probe0:umass-sim0:0:0:1): CAM status: CCB request completed with an error (probe0:umass-sim0:0:0:1): Retrying command (probe0:umass-sim0:0:0:1): INQUIRY. CDB: 12 0 0 0 24 0 (probe0:umass-sim0:0:0:1): CAM status: CCB request completed with an error (probe0:umass-sim0:0:0:1): Retrying command (probe0:umass-sim0:0:0:1): INQUIRY. CDB: 12 0 0 0 24 0 (probe0:umass-sim0:0:0:1): CAM status: CCB request completed with an error (probe0:umass-sim0:0:0:1): Error 5, Retries exhausted When the system is sad, it doesn't create a proper device, so you can't access the drive, even to reformat it. All of these drives worked under multiple systems (i386 and amd64) running 7.4-RELEASE-p12. The "bad" drives continue to work fine on an old 7.4-RELEASE-p12 machine. This new behavior is consistent on two i386 servers running 9.1-RELEASE-p2. The same drives don't work in the same way on both systems. Additionally, if the unrecognized drives are attached to the server during a reboot, the system will hard freeze on shutdown. Manually pressing the power button is necessary to reboot. Are the different quirks a clue? I am willing to reformat the "bad" drives to make them more compliant with the new OS, but right now I can't access them at all. >How-To-Repeat: Plug one of the bad drives into an i386 system running 9.1-RELEASE-p2. Plug that same bad drive into an old 7.4-RELEASE-p12 and it runs fine. Plug a good drive in 9.1-RELEASE-p2 or 7.4-RELEASE-p12 systems and it doesn't have the problem. >Fix: >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201304170527.r3H5R8fG069788>