From owner-freebsd-stable@FreeBSD.ORG Mon May 19 08:52:49 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C289F37B413 for ; Mon, 19 May 2003 08:52:49 -0700 (PDT) Received: from bast.unixathome.org (bast.unixathome.org [66.11.174.150]) by mx1.FreeBSD.org (Postfix) with ESMTP id 63C4843FCB for ; Mon, 19 May 2003 08:52:48 -0700 (PDT) (envelope-from dan@langille.org) Received: from wocker (wocker.unixathome.org [192.168.0.99]) by bast.unixathome.org (Postfix) with ESMTP id 775183D28; Mon, 19 May 2003 11:52:47 -0400 (EDT) From: "Dan Langille" To: Tenebrae Date: Mon, 19 May 2003 11:52:47 -0400 MIME-Version: 1.0 Message-ID: <3EC8C58F.31591.809EB050@localhost> Priority: normal References: <3EC80214.5515.7DA30AAB@localhost> In-reply-to: <20030519083626.B46730@steeltoe.niceboots.com> X-mailer: Pegasus Mail for Windows (v4.02a) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body cc: freebsd-stable@freebsd.org Subject: Re: ad0: READ command timeout.... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 May 2003 15:52:50 -0000 On 19 May 2003 at 8:42, Tenebrae wrote: > On Sun, 18 May 2003, Dan Langille wrote: > > > This morning I found a frozen box. On the console was this: > > > > ad0: READ command timeout tag=0 serv=0 - resetting > > ata0: resetting devices .. ata0-slave: ATA identify retries exceeded > > done > > > > After reboot, those messages were found in /var/log/messages. > > > > I'm running FreeBSD 4.8-RC from Apr 4 10:45:49 EST 2003. > > > > Any ideas? > > Hey dvl, > I've had similar problems. This has come up a few times on the mailing > list in the past, especially regarding certain lines of IBM drives. ad0: 516MB [1049/16/63] at ata0-master PIO3 For what it's worth, it's been in there since the box was put together in November 2000 and this is the first indication of a problem. It's probably getting old. > Suggestions include replacing your IDE cable, making sure it's not longer > than 18 inches...and replacing the drive as it's probably on its last leg. > Back it up while you can. Luckily, it's not really an important drive (from a data point of view) in this system: $ df | grep ad0 /dev/ad0s1a 99183 50162 41087 55% / /dev/ad0s1e 413695 1 380599 0% /slow I'll get a new drive in there ASAP. I'm glad it's not the SCSI drives which are failing: $ df Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/ad0s1a 99183 50162 41087 55% / /dev/da1s1f 17130052 15553651 205997 99% /home /dev/ad0s1e 413695 1 380599 0% /slow /dev/da0s1e 17130052 10675758 5083890 68% /usr /dev/da1s1e 254063 156203 77535 67% /var procfs 4 4 0 100% /pro -- Dan Langille : http://www.langille.org/