From owner-freebsd-questions@FreeBSD.ORG Mon Nov 12 17:57:46 2007 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 5F7E816A41B for ; Mon, 12 Nov 2007 17:57:46 +0000 (UTC) (envelope-from jerrymc@gizmo.acns.msu.edu) Received: from gizmo.acns.msu.edu (gizmo.acns.msu.edu [35.8.1.43]) by mx1.freebsd.org (Postfix) with ESMTP id F1EC913C4BE for ; Mon, 12 Nov 2007 17:57:45 +0000 (UTC) (envelope-from jerrymc@gizmo.acns.msu.edu) Received: from gizmo.acns.msu.edu (localhost [127.0.0.1]) by gizmo.acns.msu.edu (8.13.6/8.13.6) with ESMTP id lACHrpsp099289; Mon, 12 Nov 2007 12:53:52 -0500 (EST) (envelope-from jerrymc@gizmo.acns.msu.edu) Received: (from jerrymc@localhost) by gizmo.acns.msu.edu (8.13.6/8.13.6/Submit) id lACHrpMl099288; Mon, 12 Nov 2007 12:53:51 -0500 (EST) (envelope-from jerrymc) Date: Mon, 12 Nov 2007 12:53:51 -0500 From: Jerry McAllister To: David Newman Message-ID: <20071112175351.GA99195@gizmo.acns.msu.edu> References: <4736593E.1090905@networktest.com> <64c038660711102109x2ea186afjdd219292d8eed700@mail.gmail.com> <47372644.4060201@networktest.com> <20071112161416.GB98697@gizmo.acns.msu.edu> <47388CCE.6080201@networktest.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <47388CCE.6080201@networktest.com> User-Agent: Mutt/1.4.2.2i Cc: freebsd-questions@freebsd.org Subject: Re: dealing with a failing drive 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: Mon, 12 Nov 2007 17:57:46 -0000 On Mon, Nov 12, 2007 at 09:26:38AM -0800, David Newman wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 11/12/07 8:14 AM, Jerry McAllister wrote: > > > An update: After doing what you suggest (leaving in the "good" disk, > > adding a new disk, RAID rebuilding) I still got soft write errors -- > > with *either one* of the disks I tried. > > > > Then I tried putting both disks in an identical server and they came up > > fine, no read or write errors. > > > > Ergo, the bad RAID controller is bad and the disks may be OK. > > > >> Probably not. > >> Generally, if the RAID controller is bad, you will see errors > >> all over and not it just one place, tho I suppose it is possible. > >> Check and see what it reports as error locations and see if they > >> move around any. > > Jerry, thanks for your response. > > After 36 hours of running the same disks in a different, identical > machine there hasn't been a single read or write error. I'm hardly a > storage expert but from the evidence I have I'm inclined to believe the > root cause was a bad RAID controller and not failed disks. That is not much proof. The different machine would probably be accessing the disks in a different way, either slightly different positioning or using different space. Also, 36 hours is not really much time. It could be you are right, but disks have a way of starting small in errors and then avalanching on you with accelerating volume of errors just when you begin to feel safe. You could be right, but is the price of a disk worth it - the price of a new RAID controller, for that matter? Replace them both. ////jerry > > I'm aware of CLI tools to monitor 3Ware SATA RAID controllers. Anyone > know if there are similar tools for HP/Compaq SCSI RAID controllers? > > thanks > > dn > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.3 (Darwin) > > iD8DBQFHOIzOyPxGVjntI4IRAmMWAJ4grMR6mcL/j9qbcGY/fJfDEqv3KgCg8BVW > wcHVDkZPykFcQzVYnp8mx+g= > =8rws > -----END PGP SIGNATURE----- > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"