Date: Fri, 1 Feb 2008 12:05:02 -0800 From: "Kurt Buff" <kurt.buff@gmail.com> To: "Bill Moran" <wmoran@potentialtech.com> Cc: FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Re: This has begun to annoy me... Message-ID: <a9f4a3860802011205i69ccfb7bq4c135bac86cca692@mail.gmail.com> In-Reply-To: <20080201144656.2c33af82.wmoran@potentialtech.com> References: <a9f4a3860802011140x5d50663bgfadcbaf351c95f6d@mail.gmail.com> <20080201144656.2c33af82.wmoran@potentialtech.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Feb 1, 2008 11:46 AM, Bill Moran <wmoran@potentialtech.com> wrote: > In response to "Kurt Buff" <kurt.buff@gmail.com>: > > > > 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. Thanks, Kurt
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?a9f4a3860802011205i69ccfb7bq4c135bac86cca692>