From owner-freebsd-questions@FreeBSD.ORG Sun Feb 19 22:44:40 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org 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 5013E16A420 for ; Sun, 19 Feb 2006 22:44:40 +0000 (GMT) (envelope-from mike@sentex.net) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id A03E943D66 for ; Sun, 19 Feb 2006 22:44:39 +0000 (GMT) (envelope-from mike@sentex.net) Received: from BLUELAPIS.sentex.ca (cage.simianscience.com [64.7.134.1]) by smarthost2.sentex.ca (8.13.4/8.13.4) with SMTP id k1JMibNH031554; Sun, 19 Feb 2006 17:44:38 -0500 (EST) (envelope-from mike@sentex.net) From: Mike Tancsa To: "V.I.Victor" Date: Sun, 19 Feb 2006 17:44:39 -0500 Message-ID: References: In-Reply-To: X-Mailer: Forte Agent 1.93/32.576 English (American) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Scanned-By: MIMEDefang 2.51 on 205.211.164.50 Cc: freebsd-questions@freebsd.org Subject: Re: Every 12-hrs -- "ad0: TIMEOUT - WRITE DMA" 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: Sun, 19 Feb 2006 22:44:40 -0000 On Sun, 19 Feb 2006 22:21:04 +0000, in sentex.lists.freebsd.questions you wrote: >On Thu, 16 Feb 2006, Mike Tancsa wrote: > >>> For the last 4-days, our (otherwise OK) 5.4-RELEASE machine has been >>> reporting: >>> >>> Feb 12 12:08:05 : ad0: TIMEOUT - WRITE_DMA retrying (2 retries left) = LBA=3D2701279 >>> Feb 13 00:08:51 : ad0: TIMEOUT - WRITE_DMA retrying (2 retries left) = LBA=3D2701279 >>> Feb 13 12:09:38 : ad0: TIMEOUT - WRITE_DMA retrying (2 retries left) = LBA=3D2963331 >>> Feb 14 00:10:24 : ad0: TIMEOUT - WRITE_DMA retrying (2 retries left) = LBA=3D2705947 >>> >>> So -- can anyone help track this down? >> >> >> It sounds like a hardware issue. Install >> /usr/ports/sysutils/smartmontools and "ask" the drive to see whats up. > >I installed 'smartmontools' but haven't used as yet. I've been waiting = to >see what happens -- the "problem" simply stopped. There've been no "ad0: >TIMEOUT" messages for 3-days. The errors get logged in the drive so you dont have to wait for more errors to happen. Start it running now so you can see if any of the "bad" counters are changing as well as to ask the drive what it was. My guess is you have some bad sectors the drive remapped. ---Mike -------------------------------------------------------- Mike Tancsa, Sentex communications http://www.sentex.net Providing Internet Access since 1994 mike@sentex.net, (http://www.tancsa.com)