Date: Fri, 25 Jan 2008 13:55:12 -0700 From: Joe Peterson <joe@skyrush.com> To: Chuck Swiger <cswiger@mac.com> Cc: freebsd-stable@freebsd.org Subject: Re: "ad0: TIMEOUT - WRITE_DMA" type errors with 7.0-RC1 Message-ID: <479A4CB0.5080206@skyrush.com> In-Reply-To: <3803988D-8D18-4E89-92EA-19BF62FD2395@mac.com> References: <479A0731.6020405@skyrush.com> <20080125162940.GA38494@eos.sc1.parodius.com> <479A3764.6050800@skyrush.com> <3803988D-8D18-4E89-92EA-19BF62FD2395@mac.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Chuck Swiger wrote: > On Jan 25, 2008, at 11:24 AM, Joe Peterson wrote: >> ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE >> UPDATED WHEN_FAILED RAW_VALUE >> 1 Raw_Read_Error_Rate 0x000f 114 071 006 Pre-fail >> Always - 82422948 > [ ... ] >> 7 Seek_Error_Rate 0x000f 084 060 030 Pre-fail >> Always - 286126605 > [ ... ] >> 195 Hardware_ECC_Recovered 0x001a 063 046 000 Old_age >> Always - 166181300 > > These numbers are quite worrysome-- they should be zero or nearly so > in a healthy drive. It seems to depend on the drive manufacturer. E.g. this is a Seagate. Every Seagate I've ever had (or heard about on the web via smartctl dumps) reports very large numbers for these values. I've heard it described that Seagate shows you the raw numbers (and correctable errors do happen all the time in all drives). In Western Digital drives (IIRC), the numbers shown are the ones that *should* be zero, thereby hiding the low-level errors. Hard to say if my numbers are "too high", but these "corrected" error counts are always frighteningly high in Seagates. -Joe
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?479A4CB0.5080206>