From owner-freebsd-questions@FreeBSD.ORG Thu Feb 8 01:30:55 2007 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 67B9E16A403 for ; Thu, 8 Feb 2007 01:30:51 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from pi.codefab.com (pi.codefab.com [199.103.21.227]) by mx1.freebsd.org (Postfix) with ESMTP id 3B0D613C441 for ; Thu, 8 Feb 2007 01:30:51 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from localhost (localhost [127.0.0.1]) by pi.codefab.com (Postfix) with ESMTP id 5FEC460AD; Wed, 7 Feb 2007 20:30:50 -0500 (EST) X-Virus-Scanned: amavisd-new at codefab.com Received: from pi.codefab.com ([127.0.0.1]) by localhost (pi.codefab.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WeYjTmHfU4Kf; Wed, 7 Feb 2007 20:30:44 -0500 (EST) Received: from [192.168.1.251] (pool-68-161-114-230.ny325.east.verizon.net [68.161.114.230]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by pi.codefab.com (Postfix) with ESMTP id 7E91F5D95; Wed, 7 Feb 2007 20:30:43 -0500 (EST) Message-ID: <45CA7D3A.6040302@mac.com> Date: Wed, 07 Feb 2007 20:30:34 -0500 From: Chuck Swiger User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: ceo@l-i-e.com References: <33987.216.230.84.67.1170885541.squirrel@www.l-i-e.com> In-Reply-To: <33987.216.230.84.67.1170885541.squirrel@www.l-i-e.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org Subject: Re: READ_DMA48 error interpretation 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: Thu, 08 Feb 2007 01:30:55 -0000 Richard Lynch wrote: > [I've tried to snip away a lot of stuff, without losing any context...] [ ...trimming away context good, people can go back and read the thread... ] > I can touch the exposed front and back top (above IDE cable) and lay > my finger along it. It's "hot" but not like, "ouch hot" :-) You're not seeing any reallocated sectors and you're not seeing UDMA errors (ie, in the cabling). For lack of any better guesses, I'd gather that your drives are running above normal temps and aren't reading data perfectly, but are doing well enough that the built-in ECC is managing to deal with the issues. > I don't think it's 100C+ hot, as that's boiling -- but perhaps the > thermometer is somewhere inside or... On a good day, the thermometers actually provide a real, calibrated, accurate result...but many drives don't even come close. >> The output of smartctl -a for one or two of your drives would likely >> be much more indicative. I don't claim to be an expert in this at all, >> but some of us might spot any obvious anomalies. > > I sure appreciate the time y'all are taking on this! > > I am definitely not a hardware guy, as you have probably already > surmised. :-) You should actually run "smartctl -t long /dev/ad0" and repeat for all of the devices, and then re-check the "smartctl -a" output. Might be better not to run the self-tests all at once, come to think of it. -- -Chuck