External USB drive kernel problems

[up at 3.am]

On Tue, 21 Nov 2006, illoai at gmail.com wrote:

> On 11/21/06, up at 3.am <up at 3.am> wrote:
> >
> > (Please reply directly to me, as I am not subscribed)
> >
> > I just bought a VIA external USB enclosure with a Hitachi 200GB ATA drive
> > to use for disk-based backups.  I put it on my test box here, which I just
> > upgraded to 6.2-Prerelease.  All drivers required by the handbook for this
> > application are still in the kernel:
> >
> > device scbus
> > device da
> > device pass
> > device uhci
> > device ohci
> > device usb
> > device umass
> > device ehci
> >
> > However, it will not even finish booting with the USB drive plugged in.
> > It gets hung up on "Waiting 5 seconds for SCSI devices to settle".  If I
> > unplug the drive, it immediately finishes booting ok.  If I then plug it
> > back in, I get this:
> >
> > Nov 21 12:17:23 amanda kernel: umass0: VIA Technologies Inc. USB 2.0 IDE
> > Bridge, rev 2.00/0.03, addr 2
> > Nov 21 12:19:33 amanda kernel: da0 at umass-sim0 bus 0 target 0 lun 0
> > Nov 21 12:19:33 amanda kernel: da0: <Hitachi HDT725032VLA V54O> Fixed
> > Direct Access SCSI-2 device
> > Nov 21 12:19:33 amanda kernel: da0: 40.000MB/s transfers
> > Nov 21 12:19:33 amanda kernel: da0: 305245MB (625142448 512 byte sectors:
> > 255H 63S/T 38913C)
> > Nov 21 12:19:33 amanda kernel: umass0: Invalid CSW: tag 9 should be 10
> > Nov 21 12:19:33 amanda kernel: (da0:umass-sim0:0:0:0): Synchronize cache
> > failed, status == 0x10, scsi status == 0x0
> >
> > Nov 21 12:24:58 amanda kernel: Opened disk da0 -> 5
> >
> > If I try to then run sysinstall to run fdisk, it will not allow the fdisk
> > configuration to be written to it.
> >
> > TIA for any advice, ideas, fixes, etc.
>
> Maybe something as simple as building your kernel with
> options         SCSI_DELAY=10001
> or even larger.  Slow busses and some older hardware
> do not like small values here.

well, it's very new hardware on both ends (USB2).  Doesn't that SCSI delay
only affect SCSI bus probing during boot, or would it affect it if I
plugged it in after it boots?

> Second, sysinstall is for installing the system, and is fairly
> horrible for day&day ministering.  Better by far to learn the
> command line utilities.
>
> man fdisk
> man bsdlabel
> man newfs

I tried both ways...the sysinstall is what the handbook recommended.

> and if you are going to be sharing it between machines
> you might look into glabel.

I would definitely want that capability...thanks!

James Smallacombe		      PlantageNet, Inc. CEO and Janitor
up at 3.am							    http://3.am
=========================================================================