Date: Tue, 18 May 2010 10:19:55 -0500 From: "Doug Poland" <doug@polands.org> To: "Matthew Seaman" <m.seaman@infracaninophile.co.uk> Cc: questions@freebsd.org Subject: Re: Interpretting 3Ware error messages Message-ID: <dcc93cce2bafbc2d4b5d3f19a4b291cc.squirrel@email.polands.org> In-Reply-To: <4BF2AA7F.9090503@infracaninophile.co.uk> References: <f889b374b170eba47ff5f7d530a9c878.squirrel@email.polands.org> <4BF2AA7F.9090503@infracaninophile.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, May 18, 2010 09:55, Matthew Seaman wrote: > > On 18/05/2010 15:43:25, Doug Poland wrote: >> Hello, >> >> I have a 7.2-R i386 system running a 3ware 9500S-4LP SATA 150 >> controller with 4 SATA drives. I recently starting seeing the >> following in my logs.... >> >> >> I suspect a disk problem, but cannot identify the individual disk >> or the nature of the problem. Can anyone shed some light on this? >> >> > > Look at the SMART data for the disk(s) -- my guess is that you're > seeing sectors failing and being re-mapped by the drive firmware. If > this is happening to any significant extent the disk may well be > reaching the end of its usable life: happily you would seem to have > been alerted to that in time to do something about it without needing > to run around in a blind panic. > > There's a background task you can set up on 3ware controllers that > will attempt to access all sectors of a disk specifically to bring to > light problems like this, which otherwise could go unnoticed for a > long time and lead to silent data corruption. > Will do, thanks for the info. -- Regards, Doug
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?dcc93cce2bafbc2d4b5d3f19a4b291cc.squirrel>