From owner-freebsd-questions@FreeBSD.ORG Mon Nov 12 17:26:34 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 E4C9D16A417 for ; Mon, 12 Nov 2007 17:26:34 +0000 (UTC) (envelope-from dnewman@networktest.com) Received: from mail.networktest.com (mail.networktest.com [207.181.8.134]) by mx1.freebsd.org (Postfix) with ESMTP id BF90913C4BE for ; Mon, 12 Nov 2007 17:26:34 +0000 (UTC) (envelope-from dnewman@networktest.com) Received: by mail.networktest.com (Postfix, from userid 1002) id 9FE4578C53; Mon, 12 Nov 2007 09:26:22 -0800 (PST) X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on mail.networktest.com X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00 autolearn=ham version=3.2.3 Received: from dhcp254.eng.networktest.com (ns.networktest.com [207.181.8.130]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.networktest.com (Postfix) with ESMTP id B5A9C78C4D for ; Mon, 12 Nov 2007 09:26:16 -0800 (PST) Message-ID: <47388CCE.6080201@networktest.com> Date: Mon, 12 Nov 2007 09:26:38 -0800 From: David Newman Organization: Network Test Inc. User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: freebsd-questions@freebsd.org References: <4736593E.1090905@networktest.com> <64c038660711102109x2ea186afjdd219292d8eed700@mail.gmail.com> <47372644.4060201@networktest.com> <20071112161416.GB98697@gizmo.acns.msu.edu> In-Reply-To: <20071112161416.GB98697@gizmo.acns.msu.edu> X-Enigmail-Version: 0.95.5 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit 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:26:35 -0000 -----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. 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-----