From owner-freebsd-stable@freebsd.org Mon Aug 3 01:34:43 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 669EF9AFDE5 for ; Mon, 3 Aug 2015 01:34:43 +0000 (UTC) (envelope-from mcdouga9@egr.msu.edu) Received: from mail.egr.msu.edu (boomhauer.egr.msu.edu [35.9.37.164]) by mx1.freebsd.org (Postfix) with ESMTP id 40B62253 for ; Mon, 3 Aug 2015 01:34:42 +0000 (UTC) (envelope-from mcdouga9@egr.msu.edu) Received: from boomhauer (localhost [127.0.0.1]) by mail.egr.msu.edu (Postfix) with ESMTP id 154E238D8E for ; Sun, 2 Aug 2015 21:34:36 -0400 (EDT) X-Virus-Scanned: amavisd-new at egr.msu.edu Received: from mail.egr.msu.edu ([127.0.0.1]) by boomhauer (boomhauer.egr.msu.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GJOnc36pAXV7 for ; Sun, 2 Aug 2015 21:34:35 -0400 (EDT) Received: from EGR authenticated sender mcdouga9 Subject: Re: 4TB Western Digital My Book 1230 USB hard drive not working on 10.2 To: freebsd-stable@freebsd.org References: <410CF5C1-2BF7-45E8-9707-12F26C4D62A1@gromit.dlib.vt.edu> From: Adam McDougall Message-ID: <55BEC52A.6080901@egr.msu.edu> Date: Sun, 2 Aug 2015 21:34:34 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.1.0 MIME-Version: 1.0 In-Reply-To: <410CF5C1-2BF7-45E8-9707-12F26C4D62A1@gromit.dlib.vt.edu> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Aug 2015 01:34:43 -0000 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: at usbus6 > umass0: 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: 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 > ses0 at umass-sim0 bus 0 scbus9 target 0 lun 1 > ses0: 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: mem 0xfeafe000-0xfeafffff irq 18 at device 0.0 on pci3 > xhci0: 64 bytes context size, 64-bit DMA > usbus0 on xhci0 > [[...]] > ohci0: mem 0xfe7fe000-0xfe7fefff irq 16 at device 18.0 on pci0 > usbus1 on ohci0 > ohci1: mem 0xfe7fd000-0xfe7fdfff irq 16 at device 18.1 on pci0 > usbus2 on ohci1 > ehci0: mem 0xfe7ff800-0xfe7ff8ff irq 17 at device 18.2 on pci0 > usbus3: EHCI version 1.0 > usbus3 on ehci0 > ohci2: mem 0xfe7fc000-0xfe7fcfff irq 18 at device 19.0 on pci0 > usbus4 on ohci2 > ohci3: mem 0xfe7f7000-0xfe7f7fff irq 18 at device 19.1 on pci0 > usbus5 on ohci3 > ehci1: mem 0xfe7ff400-0xfe7ff4ff irq 19 at device 19.2 on pci0 > usbus6: EHCI version 1.0 > usbus6 on ehci1 > [[...]] > ohci4: 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: at usbus7 > uhub0: on usbus7 > ugen6.1: at usbus6 > uhub1: on usbus6 > ugen5.1: at usbus5 > uhub2: on usbus5 > ugen4.1: at usbus4 > uhub3: on usbus4 > ugen3.1: at usbus3 > uhub4: on usbus3 > ugen2.1: at usbus2 > uhub5: on usbus2 > ugen1.1: at usbus1 > uhub6: 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: at usbus0 > umass0: 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 > > > 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. 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.