From owner-freebsd-questions@FreeBSD.ORG Mon Feb 28 01:01:16 2005 Return-Path: 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 C155E16A4CE for ; Mon, 28 Feb 2005 01:01:16 +0000 (GMT) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6BEBC43D2F for ; Mon, 28 Feb 2005 01:01:16 +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.1/8.13.1) with SMTP id j1S11FPB074353; Sun, 27 Feb 2005 20:01:15 -0500 (EST) (envelope-from mike@sentex.net) From: Mike Tancsa To: Anthony Atkielski Date: Sun, 27 Feb 2005 20:01:24 -0500 Message-ID: References: <1561762673.20050227155330@wanadoo.fr> <1742881516.20050227230950@wanadoo.fr> In-Reply-To: <1742881516.20050227230950@wanadoo.fr> 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-Virus-Scanned: ClamAV 0.82/732/Sun Feb 27 11:51:18 2005 on smarthost2.sentex.ca X-Virus-Status: Clean cc: freebsd-questions@freebsd.org Subject: Re: WRITE_DMA errors on SATA drive under 5.3-RELEASE X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Feb 2005 01:01:16 -0000 On Sun, 27 Feb 2005 23:09:50 +0100, in sentex.lists.freebsd.questions you wrote: >Mike Tancsa writes: > >> Could be a bad sector on the drive, or bad cable. Hard to say. Try >> /usr/ports/sysutils/smartmontools/ >> >> It can read all sorts of info off the drive and help you narrow down >> what the problem might be. > > >The two SATA drives show no errors. The older IDE drive (which contains >the filesystem root) shows the stuff below. There have been over 1000 > >Device does not support Selective Self Tests/Logging Try running some of the tests on the SATA drives as well as run the monitoring daemon. With any luck, it will provide a little more information about the error condition you are seeing. ---Mike -------------------------------------------------------- Mike Tancsa, Sentex communications http://www.sentex.net Providing Internet Access since 1994 mike@sentex.net, (http://www.tancsa.com)