From owner-freebsd-questions@FreeBSD.ORG Wed Jul 28 19:30:24 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2A53516A4CF for ; Wed, 28 Jul 2004 19:30:24 +0000 (GMT) Received: from mail.cableone.net (scanmail3.cableone.net [24.116.0.123]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8AD3243D41 for ; Wed, 28 Jul 2004 19:30:23 +0000 (GMT) (envelope-from v.velox@vvelox.net) Received: from vixen42.24-119-122-191.cpe.cableone.net (unverified [24.119.122.85]) by smail3.cableone.net (SurgeMail 1.9b) with ESMTP id 28985333 for multiple; Wed, 28 Jul 2004 12:15:09 -0700 Date: Wed, 28 Jul 2004 14:30:12 -0500 From: Vulpes Velox To: samy lancher Message-Id: <20040728143012.4dc362d1@vixen42.24-119-122-191.cpe.cableone.net> In-Reply-To: <20040728164802.52346.qmail@web51703.mail.yahoo.com> References: <20040728164802.52346.qmail@web51703.mail.yahoo.com> X-Mailer: Sylpheed-Claws 0.9.12 (GTK+ 1.2.10; i386-portbld-freebsd4.10) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Server: High Performance Mail Server - http://surgemail.com cc: freebsd-questions@freebsd.org Subject: Re: ata1: resetting devices ... X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Jul 2004 19:30:24 -0000 On Wed, 28 Jul 2004 09:48:02 -0700 (PDT) samy lancher wrote: > Hello All, > > This morning I have seen the following log message on my FreeBSD 4.7 > server. > > ad2: READ command timeout tag=0 serv=0 - resetting > ata1: resetting devices .. ad2: DMA limited to UDMA33, non-ATA66 > cable or device > > done. > > I would really appreciate if someone could tell me the cause for > this message and is there something to worry about the server?. Bad drive or cable most likely. I've seen it three times. Fist it was bad cable. The other two it was bad drives. Try a new cable first and if that does not fix it, it is the drive most likely.