From owner-freebsd-current@FreeBSD.ORG Fri Feb 18 15:25:06 2005 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 2629316A4CE; Fri, 18 Feb 2005 15:25:06 +0000 (GMT) Received: from csa.cs.okstate.edu (a.cs.okstate.edu [139.78.113.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id A083E43D1F; Fri, 18 Feb 2005 15:25:05 +0000 (GMT) (envelope-from lreid@a.cs.okstate.edu) Received: by csa.cs.okstate.edu (Postfix, from userid 601) id 4B672A063E; Fri, 18 Feb 2005 09:25:05 -0600 (CST) To: cperciva@freebsd.org Received: from 164.58.79.196 (auth. user lreid@a.cs.okstate.edu) by cs.okstate.edu with HTTP; Fri, 18 Feb 2005 09:25:05 -0600 X-IlohaMail-Blah: lreid@a.cs.okstate.edu X-IlohaMail-Method: mail() [mem] X-IlohaMail-Dummy: moo X-Mailer: IlohaMail/0.8.12 (On: cs.okstate.edu) In-Reply-To: <42160556.5040106@freebsd.org> From: "Reid Linnemann" Bounce-To: "Reid Linnemann" Errors-To: "Reid Linnemann" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Message-Id: <20050218152505.4B672A063E@csa.cs.okstate.edu> Date: Fri, 18 Feb 2005 09:25:05 -0600 (CST) cc: "freebsd-current@freebsd.org" Subject: Re: ad WRITE_DMA timing out frequently X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Feb 2005 15:25:06 -0000 On 2/18/2005, "Colin Percival" wrote: >Reid Linnemann wrote: >> ad0: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=2085599 >> ad0: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=2085599 >> kernel: ad0: FAILURE - WRITE_DMA timed out >> kernel: g_vfs_done():ad0s1d[WRITE(offset=52772864, length=16384)]error = 5 > >Looks like a dying disk. > >> It seems to me that a sector on the disk might be dead in the ad0s1d >> slice (/var), but I want to be certain before I take further steps that >> the behavior I'm experiencing is positively unrelated to the migration >> to 6-CURRENT. > >Install sysutils/smartmontools from ports and use smartctl. Odds are that >the drive has logged hundreds of errors by now. > >Colin Percival >_______________________________________________ >freebsd-current@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-current >To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" smartctl doesn't report any logged errors. On a hunch, I also dd'ed a file large enough to fill /var, hoping that it would crater on writing to that sector. It didn't. I know that's not a very useful test, but it seems to hint to me that the disk isn't bad, but the driver is freaking out from some event.