Date: Wed, 29 Oct 2008 03:04:39 -0700 From: Jeremy Chadwick <koitsu@FreeBSD.org> To: Carl <k0802647@telus.net> Cc: freebsd-questions@freebsd.org Subject: Re: gmirror slice insertion, "FAILURE - READ_DMA status=51<READY, DSC, ERROR>" Message-ID: <20081029100439.GA73714@icarus.home.lan> In-Reply-To: <49082625.7080804@telus.net> References: <49067148.6080307@telus.net> <20081028024143.GA37131@icarus.home.lan> <20081028120407.G3326@wojtek.tensor.gdynia.pl> <20081028122013.GA49298@icarus.home.lan> <4907DB6B.8090000@telus.net> <20081029043314.GA66773@icarus.home.lan> <49082625.7080804@telus.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20081029100439.GA73714>