Brian King
2006-Sep-30 03:34 UTC
western digital mybook (external usb drive, 250gb) takes 15 minutes to be recognized
i'm seeing strange behavior for a wd mybook on freebsd 6.1-RELEASE-p5,
GENERIC kernel.
- the system hangs on boot if it's attached. it stops right after it has
recognized my internal hard drives and dvd writer. perhaps it would
eventually complete the booting process, but i give up after several
minutes, unplug the usb drive and press the reset button.
- after boot, if i attach the drive i see this message on the first
terminal:
-----
umass0: Western Digital External HDD, rev 2.00/2.06, addr 2
-----
about 15 minutes later (!), i see:
-----
da0 at umass-sim0 bus 0 target 0 lun 0
da0: <WD 2500JB External 0107> Fixed Direct Access SCSI-0 device
da0: 40.000MB/s transfers
da0: 238475MB (488397168 512 byte sectors: 255H 63S/T 30401C)
-----
no other messages related to the drive are displayed on the console during
these 15 minutes.
once the da0 device is recognized, i can mount the partitions (i've got it
split into two roughly equal-sized primary partitions, one ext2fs and one
msdos), e.g.:
mount -t ext2fs /dev/da0s1/mnt/backup
here is what i see about my usb hardware with dmesg:
-----
uhci0: <VIA 83C572 USB controller> port 0xd400-0xd41f at device 16.0 on
pci0
uhci0: [GIANT-LOCKED]
usb0: <VIA 83C572 USB controller> on uhci0
usb0: USB revision 1.0
uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
uhci1: <VIA 83C572 USB controller> port 0xd000-0xd01f at device 16.1 on
pci0
uhci1: [GIANT-LOCKED]
usb1: <VIA 83C572 USB controller> on uhci1
usb1: USB revision 1.0
uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub1: 2 ports with 2 removable, self powered
uhci2: <VIA 83C572 USB controller> port 0xb800-0xb81f at device 16.2 on
pci0
uhci2: [GIANT-LOCKED]
usb2: <VIA 83C572 USB controller> on uhci2
usb2: USB revision 1.0
uhub2: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub2: 2 ports with 2 removable, self powered
ehci0: <VIA VT6202 USB 2.0 controller> mem 0xed800000-0xed8000ff at device
16.3 on pci0
ehci0: [GIANT-LOCKED]
usb3: EHCI version 1.0
usb3: companion controllers, 2 ports each: usb0 usb1 usb2
usb3: <VIA VT6202 USB 2.0 controller> on ehci0
usb3: USB revision 2.0
uhub3: VIA EHCI root hub, class 9/0, rev 2.00/1.00, addr 1
uhub3: 6 ports with 6 removable, self powered
-----
here is my /etc/usbd.conf file (i've never modified it, i guess this is the
default):
-----
# Configuration file the USB daemon.
#
# See usbd.conf(5) for the description of the format of the file.
#
# $FreeBSD: src/etc/usbd.conf,v 1.15 2004/11/28 23:16:00 iedowse Exp $
# Firmware download into the ActiveWire board. After the firmware download
is
# done the device detaches and reappears as something new and shiny
automatically.
#
device "ActiveWire board, firmware download"
vendor 0x0854
product 0x0100
release 0x0000
attach "/usr/local/bin/ezdownload -f
/usr/local/share/usb/firmware/0854.0100.0_01.hex ${DEVNAME}"
# Firmware download for Entrega Serial DB25 adapter.
#
device "Entrega Serial with UART"
product 0x8001
vendor 0x1645
release 0x0101
attach "if ! kldstat -n usio > /dev/null 2>&1 ; then
kldload usio;
fi"
attach "/usr/sbin/ezdownload -v -f
/usr/share/usb/firmware/1645.8001.0101 /dev/${DEVNAME}"
# This entry starts the ColdSync tool in daemon mode. Make sure you have an
up
# to date /usr/local/etc/palms. We override the 'listen' settings for
port
and
# type in /usr/local/etc/coldsync.conf.
device "Handspring Visor"
devname "ugen[0-9]+"
vendor 0x082d
product 0x0100
release 0x0100
attach "/usr/local/bin/coldsync -md -p /dev/${DEVNAME} -t usb"
# The fallthrough entry: Nothing is specified, nothing is done. And it
isn't
# necessary at all :-). Just for pretty printing in debugging mode.
#
device "USB device"
-----
what could be causing this delay between the attachment of the drive and
registration of the da0 device?
Roland Smith
2006-Sep-30 05:22 UTC
western digital mybook (external usb drive, 250gb) takes 15 minutes to be recognized
On Sat, Sep 30, 2006 at 12:34:10PM +0200, Brian King wrote:> i'm seeing strange behavior for a wd mybook on freebsd 6.1-RELEASE-p5, > GENERIC kernel. > > - the system hangs on boot if it's attached. it stops right after it has > recognized my internal hard drives and dvd writer. perhaps it would > eventually complete the booting process, but i give up after several > minutes, unplug the usb drive and press the reset button. > - after boot, if i attach the drive i see this message on the first > terminal: > ----- > umass0: Western Digital External HDD, rev 2.00/2.06, addr 2 > ----- > > about 15 minutes later (!), i see: > ----- > da0 at umass-sim0 bus 0 target 0 lun 0 > da0: <WD 2500JB External 0107> Fixed Direct Access SCSI-0 device > da0: 40.000MB/s transfers > da0: 238475MB (488397168 512 byte sectors: 255H 63S/T 30401C) > -----I've got an external harddrive with a WD disk. It works without problems; umass0: Prolific Technology Inc. Mass Storage Device, rev 2.00/1.00, addr 2 da0 at umass-sim0 bus 0 target 0 lun 0 da0: <WDC WD25 00JB-00REA0 20.0> Fixed Direct Access SCSI-0 device da0: 40.000MB/s transfers da0: 238475MB (488397168 512 byte sectors: 255H 63S/T 30401C) I've encrypted mine with GEOM_ELI though, and put a single filesystem on the encryped disk.> no other messages related to the drive are displayed on the console during > these 15 minutes. > > once the da0 device is recognized, i can mount the partitions (i've got it > split into two roughly equal-sized primary partitions, one ext2fs and one > msdos), e.g.: > mount -t ext2fs /dev/da0s1/mnt/backupMaybe the driver is looking for FreeBSD slices? Do you see any disk activity during this 15 minute period?> here is what i see about my usb hardware with dmesg: > ----- > uhci0: <VIA 83C572 USB controller> port 0xd400-0xd41f at device 16.0 on pci0 > uhci0: [GIANT-LOCKED] > usb0: <VIA 83C572 USB controller> on uhci0 > usb0: USB revision 1.0 > uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > uhub0: 2 ports with 2 removable, self powered > uhci1: <VIA 83C572 USB controller> port 0xd000-0xd01f at device 16.1 on pci0 > uhci1: [GIANT-LOCKED]<snip>> usb3: companion controllers, 2 ports each: usb0 usb1 usb2 > usb3: <VIA VT6202 USB 2.0 controller> on ehci0 > usb3: USB revision 2.0 > uhub3: VIA EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 > uhub3: 6 ports with 6 removable, self powered > -----Got more or less the same here. A couple of 83C572's with a VT6202 for USB 2.0.> here is my /etc/usbd.conf file (i've never modified it, i guess this is the > default): > -----Have you even enabled it? It's disabled by default. As I understand, it's deprecated in favour of devd. I can't find any devd events on my system for the drive, probably because it's handled by atapicam(4).> what could be causing this delay between the attachment of the drive and > registration of the da0 device?Looking for FreeBSD slices is one thing I can think of. Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 187 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20060930/20ed612f/attachment.pgp