From owner-freebsd-usb@FreeBSD.ORG Wed Mar 2 11:35:24 2011 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6816C106564A for ; Wed, 2 Mar 2011 11:35:24 +0000 (UTC) (envelope-from jacek@gawrych.net) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 28B658FC08 for ; Wed, 2 Mar 2011 11:35:23 +0000 (UTC) Received: by vws16 with SMTP id 16so5862201vws.13 for ; Wed, 02 Mar 2011 03:35:23 -0800 (PST) MIME-Version: 1.0 Received: by 10.220.201.70 with SMTP id ez6mr1921345vcb.229.1299064024572; Wed, 02 Mar 2011 03:07:04 -0800 (PST) Sender: jacek@gawrych.net Received: by 10.220.192.74 with HTTP; Wed, 2 Mar 2011 03:07:04 -0800 (PST) Date: Wed, 2 Mar 2011 12:07:04 +0100 X-Google-Sender-Auth: bM15ydun8cDkPEDm9z-4aoir2X0 Message-ID: From: Jacek Gawrych To: freebsd-usb@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: WD MyBook Essential problem X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Mar 2011 11:35:24 -0000 Dear Colleagues, I've just purchased this External 1,5 TB HD: http://www.wdc.com/en/products/products.aspx?id=240 All is fine except of one thing: it is not detected during the system boot - I can "see" it only when I physically reattach it after every reboot. To make it more complicated, I did tests with my older WD MyBook 750 GB and it is detected in exactly the same conditions (same system). I really hoped that yesterday upgrade from 8.1 to 8.2-RELESE could have helped, but it didn't change anything. This is what I get after reattaching during normal system usage: # dmesg ..... ugen4.2: at usbus4 (disconnected) umass0: at uhub4, port 3, addr 2 (disconnected) (da0:umass-sim0:0:0:0): lost device (da0:umass-sim0:0:0:0): removing device entry uhid0: at uhub4, port 3, addr 2 (disconnected) ugen4.2: at usbus4 umass0: on usbus4 umass0: SCSI over Bulk-Only; quirks = 0x0000 umass0:0:0:-1: Attached to scbus0 da0 at umass-sim0 bus 0 scbus0 target 0 lun 0 da0: Fixed Direct Access SCSI-6 device da0: 40.000MB/s transfers da0: 1430767MB (2930210816 512 byte sectors: 255H 63S/T 182397C) ses0 at umass-sim0 bus 0 scbus0 target 0 lun 1 ses0: Fixed Enclosure Services SCSI-6 device ses0: 40.000MB/s transfers ses0: SCSI-3 SES Device # camcontrol devlist at scbus0 target 0 lun 0 (pass0,da0) at scbus0 target 0 lun 1 (pass1,ses0) //this is the same physical device # camcontrol rescan all Re-scan of bus 0 was successful # camcontrol reset all Reset of bus 0 returned error 0x3a ########## And this is what I get after rebooting with the HD attached: # dmesg ..... Root mount waiting for: usbus4 Root mount waiting for: usbus4 Root mount waiting for: usbus4 uhub4: 8 ports with 8 removable, self powered Root mount waiting for: usbus4 Root mount waiting for: usbus4 usb_alloc_device: set address 2 failed (USB_ERR_TIMEOUT, ignored) Root mount waiting for: usbus4 Root mount waiting for: usbus4 usbd_req_re_enumerate: addr=2, set address failed! (USB_ERR_TIMEOUT, ignored) Root mount waiting for: usbus4 Root mount waiting for: usbus4 Root mount waiting for: usbus4 Root mount waiting for: usbus4 usbd_req_re_enumerate: addr=2, set address failed! (USB_ERR_TIMEOUT, ignored) Root mount waiting for: usbus4 ugen4.2: at usbus4 (disconnected) uhub_reattach_port: could not allocate new device ..... # camcontrol devlist //nothing here # camcontrol rescan all camcontrol: CAMIOCOMMAND ioctl failed: Invalid argument # camcontrol reset all camcontrol: CAMIOCOMMAND ioctl failed: Invalid argument So now I have to reach the server physically to reattach the HD to get the output presented first (and to have it work). I tried it with SCSI_DELAY=5000 (default kernel value) as well as with 15000 ms. I tried in /etc/rc.conf: usbd_enable="YES" dbus_enable="YES" hald_enable="YES" but it didn't change anything, same as: ahci_load="YES" uhci_load="YES" ohci_load="YES" ehci_load="YES" usb_load="YES" # USB subsystem ugen_load="YES" # USB generic device, if all else fails ... uhid_load="YES" # Human Interface Devices umass_load="YES" # Mass Storage Devices in /boot/loader.conf Any idea what can be the reason? I purchased 2 such HDs for 2 separate FreeBSD systems, which doubles my problem ;) In Ubuntu there's no such issue - the HD works fine. I've spent dozens of hours on that, and still am in the same point... Thank you very much in advance for any clue. Jacek