From owner-freebsd-questions@FreeBSD.ORG Fri Feb 1 20:21:35 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5D20E16A418 for ; Fri, 1 Feb 2008 20:21:35 +0000 (UTC) (envelope-from wmoran@potentialtech.com) Received: from mail.potentialtech.com (internet.potentialtech.com [66.167.251.6]) by mx1.freebsd.org (Postfix) with ESMTP id 3027713C46B for ; Fri, 1 Feb 2008 20:21:35 +0000 (UTC) (envelope-from wmoran@potentialtech.com) Received: from vanquish.ws.pitbpa0.priv.collaborativefusion.com (pr40.pitbpa0.pub.collaborativefusion.com [206.210.89.202]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.potentialtech.com (Postfix) with ESMTP id 56B1EEBC3B; Fri, 1 Feb 2008 15:21:34 -0500 (EST) Date: Fri, 1 Feb 2008 15:21:33 -0500 From: Bill Moran To: "Kurt Buff" Message-Id: <20080201152133.978bb073.wmoran@potentialtech.com> In-Reply-To: References: <20080201144656.2c33af82.wmoran@potentialtech.com> X-Mailer: Sylpheed 2.4.7 (GTK+ 2.12.1; i386-portbld-freebsd6.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: FreeBSD Questions Subject: Re: This has begun to annoy me... X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Feb 2008 20:21:35 -0000 In response to "Kurt Buff" : > On Feb 1, 2008 11:46 AM, Bill Moran wrote: > > In response to "Kurt Buff" : > > > > > > > I've been getting this in my daily security email from one of my boxes > > > for quite a while, and have been ignoring it, because of workload. > > > > > > However, it's finally annoyed me enough to pursue it. > > > > > > What would the significance of the following section be? > > > > > > zsquid.mycompany.com kernel log messages: > > > +++ /tmp/security.4blejPLW Fri Feb 1 03:02:08 2008 > > > +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=4662143 > > > +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=113995359 > > > +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=112970015 > > > +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=4668319 > > > +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=4849151 > > > +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=115527359 > > > +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=113714335 > > > +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=113715199 > > > +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=4570911 > > > +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=42958719 > > > +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=113343327 > > > +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=117315327 > > > > > > It looks like disk write errors to me, but I'm not sure. > > > > > > Thoughts? > > > > Looks like a failing disk to me. > > > > Depending on the importance of the data on that drive, make sure you're > > getting backups and get a new drive on order. > > > > If it's always done this, it could also be faulty or non-standard hardware > > (such as the SATA controller). > > That's pretty much what I expected. > > It's done this since I've been running the machine, about six months > now. Given your comment, I expect it's an issue with the controller. I recommend you _not_ trust that system. In my experience, systems with weird errors like this can suddenly lose your data for no reason. -- Bill Moran http://www.potentialtech.com