From owner-freebsd-questions@FreeBSD.ORG Fri Oct 31 18:02:52 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 022B5106568F for ; Fri, 31 Oct 2008 18:02:52 +0000 (UTC) (envelope-from Thomas.Sparrevohn@btinternet.com) Received: from smtp810.mail.ird.yahoo.com (smtp810.mail.ird.yahoo.com [217.146.188.70]) by mx1.freebsd.org (Postfix) with SMTP id E9ADC8FC12 for ; Fri, 31 Oct 2008 18:02:50 +0000 (UTC) (envelope-from Thomas.Sparrevohn@btinternet.com) Received: (qmail 96329 invoked from network); 31 Oct 2008 17:36:10 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=btinternet.com; h=Received:X-YMail-OSG:X-Yahoo-Newman-Property:From:To:Subject:Date:User-Agent:Cc:References:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Content-Disposition:Message-Id; b=TRJe8KonI0zx6t+d3ZJeoiHqSjCVdWGP76A0z3TTnM53GQl7NbPV0idVS0kbNR9dehuKKePyU2EwyBy1E637qQbfr888dxfRbbgMkwmsWdVXWC9yrB0iHO1RC3l1jY2LXuGVnh1fIiUDPaS/1bRIRcTq7ZOwaEOJAPPL+pCDWQc= ; Received: from unknown (HELO w2fzz0vc03.aah-go-on.com) (Thomas.Sparrevohn@86.133.208.69 with login) by smtp810.mail.ird.yahoo.com with SMTP; 31 Oct 2008 17:36:10 -0000 X-YMail-OSG: h3fl1QIVM1nEZepaWMTyyWqF0hSdgmRjjJ3W.sCYC4pH6sZd2ryhnZF0gCBAH4uvMt_lQh57Mw.MU9llx3Y1.zcjyMWXEEMR_F3dYIvKb8laaDrTrM.gMppZ4Ofq6t9hur4- X-Yahoo-Newman-Property: ymail-3 From: Thomas Sparrevohn To: freebsd-questions@freebsd.org Date: Fri, 31 Oct 2008 17:36:08 +0000 User-Agent: KMail/1.9.10 References: <49067148.6080307@telus.net> <49082625.7080804@telus.net> <20081029100439.GA73714@icarus.home.lan> In-Reply-To: <20081029100439.GA73714@icarus.home.lan> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200810311736.09706.Thomas.Sparrevohn@btinternet.com> Cc: Carl , Jeremy Chadwick Subject: Re: gmirror slice insertion, "FAILURE - READ_DMA status=51" 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: Fri, 31 Oct 2008 18:02:52 -0000 On Wednesday 29 October 2008 10:04:39 Jeremy Chadwick wrote: > On Wed, Oct 29, 2008 at 02:00:21AM -0700, Carl wrote: > > Jeremy Chadwick wrote: > >> Seagate chooses to encode some raw data for some SMART attributes in a > >> custom format. The format is not publicly documented. This is why you > >> have to go off of the adjusted values shown in VALUE/WORST/THRESH. > >> "How am I supposed to know all of this?!" You aren't -- it comes with > >> experience. > > > > And yet my failing drive's VALUE numbers are still all above their > > THRESH values, despite it being bad enough to cripple the system. One > > might argue those threshold values leave something to be desired. > > I'd urge you to file complaint(s) with drive manufacturers, as they're > the ones who decide the values. Thresholds are not defined per the > ATA-ATAPI specification, so technically they can pick whatever value > they want. This is exactly why you'll encounter people screaming "SMART > is worthless, the drive is already dead by the time the overall SMART > health check fails!" > > If you go this route, please CC me, as I'd be quite to see what > manufacturers have to say. > Just a saw note - I saw the same problem with a hitachi disk - I ran a vendor diagnostics tool that I found on their home page and it rebuild the bad sector map and the problem went away The error occured after I had the disk for a couple of days - WHat puzzled me was that the drive did not do it automatically