From owner-freebsd-firewire@FreeBSD.ORG Mon Feb 9 06:32:36 2009 Return-Path: Delivered-To: freebsd-firewire@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BDC6C106564A for ; Mon, 9 Feb 2009 06:32:36 +0000 (UTC) (envelope-from freebsd@sopwith.solgatos.com) Received: from sopwith.solgatos.com (pool-173-50-231-101.ptldor.fios.verizon.net [173.50.231.101]) by mx1.freebsd.org (Postfix) with ESMTP id DC2258FC0A for ; Mon, 9 Feb 2009 06:32:35 +0000 (UTC) (envelope-from freebsd@sopwith.solgatos.com) Received: by sopwith.solgatos.com (Postfix, from userid 66) id 20214B652; Sun, 8 Feb 2009 22:14:25 -0800 (PST) Received: from localhost by sopwith.solgatos.com (8.8.8/6.24) id GAA09996; Mon, 9 Feb 2009 06:30:10 GMT Message-Id: <200902090630.GAA09996@sopwith.solgatos.com> To: freebsd-firewire@freebsd.org In-reply-to: Your message of "Sat, 07 Feb 2009 15:20:05 GMT." <200902071520.n17FK5mC047103@freefall.freebsd.org> Date: Sun, 08 Feb 2009 22:30:10 +0000 From: Dieter Subject: Re: kern/97208: [firewire] System hangs / locks up when a firewire disk is attached X-BeenThere: freebsd-firewire@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Firewire support in FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Feb 2009 06:32:37 -0000 > > Also, there do appear to be some kind of "updates" for this Maxtor > > series drive. > > > > Have you updated it with the s/w on the Maxtor website? > > The drive in question is a Maxtor OneTouch II, 300GB drive with both > usb and firewire ports on it. > I have checked Maxtor.com for the updates you mention, but the only > thing I could find were: > - os specific drivers for Windows, OS X > - updates to included backup software (again Windows and / or OS X > specific) > > If therer are firmware updates for this drive, could you plase point me > to it? I assume that "OneTouch II" is that name of a product including the external box and USB/FW bridge. You need the model of the actual SATA or PATA drive inside. You can get that using "atacontrol cap $disk_name" for a disk connected directly to a SATA or PATA controller. I haven't been able to get this info for a disk connected through a USB bridge, and firewire may have the same problem. You might have to open the box up and look at the label on the drive. You'll need the serial number as well. Somewhere under www.seagate.com there is a page that will supposedly tell you if your particular drive was run through the broken test machine or not. Seagate's web site is broken and doesn't work for me, perhaps you will have better luck. There are reports of false negatives if you use lower case, so be sure to match the case when entering model number and serial number.