4TB Western Digital My Book 1230 USB hard drive not working on 10.2

[Paul Mather]

On Aug 2, 2015, at 9:34 PM, Adam McDougall <mcdouga9 at egr.msu.edu> wrote:

> On 08/02/2015 21:22, Paul Mather wrote:
>> I have a 4TB external USB drive (Western Digital My Book 1230) that I am trying to use under FreeBSD/amd64 10.2 (10.2-PRERELEASE #0 r286052: Wed Jul 29 20:59:39 EDT 2015).  This system has a MSI 760GMA-P34 (FX) motherboard.
>> 
>> The drive probes unreliably when plugged in to a USB 3 port.  It reliably probes when plugged into a USB 2 port.  However, it works in neither cases.  Attempting to dd from the drive results in a "dd: /dev/da0: Invalid argument".
>> 
>> When plugged in to a USB 2 port, this is how the drive is probed:
>> 
>> ugen6.2: <Western Digital> at usbus6
>> umass0: <Western Digital My Book 1230, class 0/0, rev 2.10/10.65, addr 2> on usbus6
>> umass0:  SCSI over Bulk-Only; quirks = 0xc001
>> umass0:9:0:-1: Attached to scbus9
>> da0 at umass-sim0 bus 0 scbus9 target 0 lun 0
>> da0: <WD My Book 1230 1065> Fixed Direct Access SPC-4 SCSI device
>> da0: Serial Number 57434334453056594A4C4A4A
>> da0: 40.000MB/s transfers
>> da0: 3815415MB (976746240 4096 byte sectors: 255H 63S/T 60799C)
>> da0: quirks=0x2<NO_6_BYTE>
>> ses0 at umass-sim0 bus 0 scbus9 target 0 lun 1
>> ses0: <WD SES Device 1065> Fixed Enclosure Services SPC-4 SCSI device
>> ses0: Serial Number 57434334453056594A4C4A4A
>> ses0: 40.000MB/s transfers
>> ses0: SCSI-3 ENC Device
>> 
>> When booting with it connected to a USB 3 port, this is what is output:
>> 
>> xhci0: <XHCI (generic) USB 3.0 controller> mem 0xfeafe000-0xfeafffff irq 18 at device 0.0 on pci3
>> xhci0: 64 bytes context size, 64-bit DMA
>> usbus0 on xhci0
>> [[...]]
>> ohci0: <AMD SB7x0/SB8x0/SB9x0 USB controller> mem 0xfe7fe000-0xfe7fefff irq 16 at device 18.0 on pci0
>> usbus1 on ohci0
>> ohci1: <AMD SB7x0/SB8x0/SB9x0 USB controller> mem 0xfe7fd000-0xfe7fdfff irq 16 at device 18.1 on pci0
>> usbus2 on ohci1
>> ehci0: <AMD SB7x0/SB8x0/SB9x0 USB 2.0 controller> mem 0xfe7ff800-0xfe7ff8ff irq 17 at device 18.2 on pci0
>> usbus3: EHCI version 1.0
>> usbus3 on ehci0
>> ohci2: <AMD SB7x0/SB8x0/SB9x0 USB controller> mem 0xfe7fc000-0xfe7fcfff irq 18 at device 19.0 on pci0
>> usbus4 on ohci2
>> ohci3: <AMD SB7x0/SB8x0/SB9x0 USB controller> mem 0xfe7f7000-0xfe7f7fff irq 18 at device 19.1 on pci0
>> usbus5 on ohci3
>> ehci1: <AMD SB7x0/SB8x0/SB9x0 USB 2.0 controller> mem 0xfe7ff400-0xfe7ff4ff irq 19 at device 19.2 on pci0
>> usbus6: EHCI version 1.0
>> usbus6 on ehci1
>> [[...]]
>> ohci4: <AMD SB7x0/SB8x0/SB9x0 USB controller> mem 0xfe7f6000-0xfe7f6fff irq 18 at device 20.5 on pci0
>> usbus7 on ohci4
>> [[...]]
>> usbus0: 5.0Gbps Super Speed USB v3.0
>> usbus1: 12Mbps Full Speed USB v1.0
>> usbus2: 12Mbps Full Speed USB v1.0
>> usbus3: 480Mbps High Speed USB v2.0
>> usbus4: 12Mbps Full Speed USB v1.0
>> usbus5: 12Mbps Full Speed USB v1.0
>> usbus6: 480Mbps High Speed USB v2.0
>> usbus7: 12Mbps Full Speed USB v1.0
>> ugen7.1: <ATI> at usbus7
>> uhub0: <ATI OHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus7
>> ugen6.1: <ATI> at usbus6
>> uhub1: <ATI EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus6
>> ugen5.1: <ATI> at usbus5
>> uhub2: <ATI OHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus5
>> ugen4.1: <ATI> at usbus4
>> uhub3: <ATI OHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus4
>> ugen3.1: <ATI> at usbus3
>> uhub4: <ATI EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus3
>> ugen2.1: <ATI> at usbus2
>> uhub5: <ATI OHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus2
>> ugen1.1: <ATI> at usbus1
>> uhub6: <ATI OHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus1
>> ugen0.1: <0x1912> at usbus0
>> uhub7: <0x1912 XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0
>> uhub0: 2 ports with 2 removable, self powered
>> uhub2: 3 ports with 3 removable, self powered
>> uhub3: 3 ports with 3 removable, self powered
>> uhub5: 3 ports with 3 removable, self powered
>> uhub6: 3 ports with 3 removable, self powered
>> uhub7: 8 ports with 8 removable, self powered
>> [[...]]
>> Root mount waiting for: usbus6 usbus3 usbus0
>> Root mount waiting for: usbus6 usbus3 usbus0
>> uhub1: 6 ports with 6 removable, self powered
>> uhub4: 6 ports with 6 removable, self powered
>> ugen0.2: <vendor 0x1058> at usbus0
>> umass0: <vendor 0x1058 product 0x1230, class 0/0, rev 3.00/10.65, addr 1> on usbus0
>> umass0:  SCSI over Bulk-Only; quirks = 0x8000
>> Root mount waiting for: usbus0
>> [[...]]
>> Root mount waiting for: usbus0
>> Root mount waiting for: usbus0
>> umass0: Get Max Lun not supported (USB_ERR_TIMEOUT)
>> umass0:9:0:-1: Attached to scbus9
>> [[...]]
>> da0 at umass-sim0 bus 0 scbus9 target 0 lun 0
>> da0: <  > Fixed Direct Access SCSI device
>> da0: Serial Number WCC4E0VYJLJJ
>> da0: 400.000MB/s transfers
>> da0: 3815415MB (976746240 4096 byte sectors: 255H 63S/T 60799C)
>> da0: quirks=0x2<NO_6_BYTE>
>> 
>> 
>> This external USB drive works fine under OSX Yosemite and also when plugged in to my Raspberry Pi 2 running OSMC.
>> 
>> Is there anyone using this model of USB drive under FreeBSD/amd64 10.2?  Is it a matter of finding the correct quirk to get it working?
>> 
>> Cheers,
>> 
>> Paul.
> 
> The trouble detecting is probably related to
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196332
> 
> I have trouble with my 2T WD "My passport" but I did not create a bug
> report because I found the one above which didn't get a reply.

That PR describes a lot of the symptoms occurring with this WD My Book drive (although I haven't tried it under FreeBSD 9).  I notice there was a comment added to that PR today---maybe in response to your observation above?


> As far as "dd: /dev/da0: Invalid argument", did you supply a bs=
> argument to dd?  I noticed: "da0: 3815415MB (976746240 4096 byte
> sectors" which means it is reporting as a 4k drive and it will reject
> 512 byte IO requests like dd would use without bs=.  I ran into that
> issue when I was testing some old FC drives formatted for 520 byte
> sectors for ECC instead of 512.

Thank you for that suggestion.  I had not added "bs=" to the dd command, although it makes perfect sense to do so.

Unfortunately, that still doesn't cause the drive to work under FreeBSD 10.2 on my system.  I do get a different error: "Input/output error" instead of "Invalid argument."  It also causes the device to go away:

(da0:umass-sim0:0:0:0): READ(10). CDB: 28 00 00 00 01 00 00 00 01 00
(da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error
(da0:umass-sim0:0:0:0): Retrying command
(da0:umass-sim0:0:0:0): READ(10). CDB: 28 00 00 00 01 00 00 00 01 00
(da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error
(da0:umass-sim0:0:0:0): Retrying command
(da0:umass-sim0:0:0:0): READ(10). CDB: 28 00 00 00 01 00 00 00 01 00
(da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error
(da0:umass-sim0:0:0:0): Retrying command
(da0:umass-sim0:0:0:0): READ(10). CDB: 28 00 00 00 01 00 00 00 01 00
(da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error
(da0:umass-sim0:0:0:0): Retrying command
(da0:umass-sim0:0:0:0): READ(10). CDB: 28 00 00 00 01 00 00 00 01 00
(da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error
(da0:umass-sim0:0:0:0): Error 5, Retries exhausted
(da0:umass-sim0:0:0:0): got CAM status 0x44
(da0:umass-sim0:0:0:0): fatal error, failed to attach to device
da0 at umass-sim0 bus 0 scbus9 target 0 lun 0
da0: <WD My Book 1230 1065> s/n 57434334453056594A4C4A4A detached
(da0:umass-sim0:0:0:0): Periph destroyed


It's unfortunate that current FreeBSD does not appear to work with this drive, as it's very commonplace.  I had hoped to use it as a portable drive between my Raspberry Pi 2 OSMC system, my Mac laptop, and my FreeBSD 10-STABLE system.  It works on all but the latter. :-(

Cheers,

Paul.