From owner-freebsd-questions@FreeBSD.ORG Sun Feb 19 22:22:27 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 08DAB16A424 for ; Sun, 19 Feb 2006 22:22:27 +0000 (GMT) (envelope-from idmc_vivr@intgdev.com) Received: from mail.networksolutionsemail.com (omr2.networksolutionsemail.com [205.178.146.52]) by mx1.FreeBSD.org (Postfix) with SMTP id 77E9743DF0 for ; Sun, 19 Feb 2006 22:21:31 +0000 (GMT) (envelope-from idmc_vivr@intgdev.com) Received: (qmail 25716 invoked from network); 19 Feb 2006 22:21:04 -0000 Received: from unknown (HELO webmail15) (205.178.146.50) by omr2.mgt.bos.netsol.com with SMTP; 19 Feb 2006 22:21:04 -0000 Received: from 69.40.204.177 (unverified [69.40.204.177]) by webmail15 (VisualOffice 4.01) with WEBMAIL id 13080; Sun, 19 Feb 2006 22:21:04 +0000 From: "V.I.Victor" To: freebsd-questions@freebsd.org Importance: Normal Sensitivity: Normal Message-ID: X-Mailer: Mintersoft VisualOffice, Build 4.01.1003 X-Originating-IP: [69.40.204.177] Date: Sun, 19 Feb 2006 22:21:04 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit 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:22:27 -0000 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=2701279 >> Feb 13 00:08:51 : ad0: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=2701279 >> Feb 13 12:09:38 : ad0: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=2963331 >> Feb 14 00:10:24 : ad0: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=2705947 >> >> 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 only thing done outside of the ordinary, prior to the messages stopping, was to set the date. It's probably a coincidence but setting the date was also the last thing done before the the messages started.