From owner-freebsd-current@FreeBSD.ORG Mon Aug 23 03:44:33 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C9F6916A4CE for ; Mon, 23 Aug 2004 03:44:33 +0000 (GMT) Received: from kestrel.alerce.com (kestrel.alerce.com [209.182.219.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7FE3A43D46 for ; Mon, 23 Aug 2004 03:44:33 +0000 (GMT) (envelope-from hartzell@kestrel.alerce.com) Received: from rosebud.alerce.com (w092.z064001164.sjc-ca.dsl.cnc.net [64.1.164.92]) (authenticated bits=128) by kestrel.alerce.com (8.12.10/8.12.10) with ESMTP id i7N3iVkk086383 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sun, 22 Aug 2004 20:44:32 -0700 (PDT) (envelope-from hartzell@kestrel.alerce.com) Received: from rosebud.alerce.com (localhost [127.0.0.1]) by rosebud.alerce.com (8.12.9p2/8.12.9) with ESMTP id i7N3j5je002123 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 22 Aug 2004 20:45:06 -0700 (PDT) (envelope-from hartzell@rosebud.alerce.com) Received: (from hartzell@localhost) by rosebud.alerce.com (8.12.9p2/8.12.9/Submit) id i7N3j5Gp002120; Sun, 22 Aug 2004 20:45:05 -0700 (PDT) (envelope-from hartzell) From: George Hartzell MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16681.26689.215660.854423@rosebud.alerce.com> Date: Sun, 22 Aug 2004 20:45:05 -0700 To: Doug White In-Reply-To: <20040822193851.K94593@carver.gumbysoft.com> References: <16679.59263.287454.325068@rosebud.alerce.com> <20040822193851.K94593@carver.gumbysoft.com> X-Mailer: VM 7.14 under 21.4 (patch 14) "Reasonable Discussion" XEmacs Lucid X-Virus-Scanned: ClamAV version 'clamd / ClamAV version 0.65', clamav-milter version '0.60p' cc: freebsd-current@freebsd.org Subject: Re: Help making sense of firewire disk enclosure dilema X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: hartzell@kestrel.alerce.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Aug 2004 03:44:33 -0000 Doug White writes: > On Sat, 21 Aug 2004, George Hartzell wrote: > > > > > I have a machine running 5.2.1-RELEASE-p6. > > > > I purchased a pair of "Vantec" USB2.0/Firewire enclosures (NST-350UF) > > for some 80-ish GB IBM Deskstar drives. > > [...] > > The second enclosure was problematic. [...] > > Have you tried 'camcontrol rescan X' where X is the appropriate SCSI bus? > (camcontrol devlist -v can help you find the right bus number.) > > I have this problem with certain USB key storage devices as well. It > depends on how long the device takes to come ready. Some are better than > others. The enclosure is smeared across the kitchen table at the moment (see below), so I can't give it's exact reaction to suggestion, but I have some representative output. In the course of mucking around, I've tried various combinations of 'fwcontrol -r' and 'camcontrol rescan all'. I'm not sure which caused which part of the dmesg output below, but it might be interesting: sbp0:0:0 request timeout(cmd orb:0x163ca634) ... agent reset sbp0:0:0 request timeout(cmd orb:0x163ca76c) ... target reset fwohci0: BUS reset fwohci0: node_id=0xc800ffc0, gen=6, CYCLEMASTER mode firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me) firewire0: bus manager 0 (me) sbp0:0:0 request timeout(cmd orb:0x163ca9dc) ... reset start fwohci0: txd err= 3 miss Ack err sbp0:0:0 sbp_reset_start failed: resp=22 firewire0: split transaction timeout dst=0xffc0 tl=0x30 state=4 sbp0:0:0 sbp_reset_start failed: resp=60 I figured out how to ask fwcontrol to tell me more about the device inside the enclosure, and discovered that it's a Prolific PL-3507. A little googling about suggests that it's a well known PITA device, e.g. http://forum.rpc1.org/viewtopic.php?t=25140&postdays=0&postorder=asc&&start=0&sid=0a359d410cfd87df72f2543365922421 So, I'm left to decide whether to muck with the firmware or just chuck it..... Are there "quirks" for firewire devices like there used to be (are?) for usb devices? g.