From owner-freebsd-stable@FreeBSD.ORG Tue Oct 26 22:27:33 2004 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1DEB616A4CE for ; Tue, 26 Oct 2004 22:27:33 +0000 (GMT) Received: from hub.org (hub.org [200.46.204.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id E07BE43D55 for ; Tue, 26 Oct 2004 22:27:32 +0000 (GMT) (envelope-from scrappy@hub.org) Received: from localhost (unknown [200.46.204.144]) by hub.org (Postfix) with ESMTP id DF67C12AE5A; Tue, 26 Oct 2004 19:27:27 -0300 (ADT) Received: from hub.org ([200.46.204.220]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 71052-05; Tue, 26 Oct 2004 22:27:27 +0000 (GMT) Received: from ganymede.hub.org (blk-222-46-91.eastlink.ca [24.222.46.91]) by hub.org (Postfix) with ESMTP id 7E67512A074; Tue, 26 Oct 2004 19:27:27 -0300 (ADT) Received: by ganymede.hub.org (Postfix, from userid 1000) id E6D7848771; Tue, 26 Oct 2004 19:27:30 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id E5B19486F6; Tue, 26 Oct 2004 19:27:30 -0300 (ADT) Date: Tue, 26 Oct 2004 19:27:30 -0300 (ADT) From: "Marc G. Fournier" To: Carroll Kong In-Reply-To: <0ade01c4bba3$986c1520$0200a8c0@athena> Message-ID: <20041026192648.Q39377@ganymede.hub.org> References: <417E6F2A.9020508@borderware.com> <1127.209.152.53.188.1098822627.squirrel@209.152.53.188> <0ade01c4bba3$986c1520$0200a8c0@athena> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by amavisd-new at hub.org cc: freebsd-stable@freebsd.org Subject: Re: 3ware raid X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Oct 2004 22:27:33 -0000 On Tue, 26 Oct 2004, Carroll Kong wrote: > 4) Monitor the system carefully. Apparently in DEGRADED mode, the > system has a high chance of complete lockups if left unattended. It is > important to note that the 3Ware controller is very sensitive. People > have gone into DEGRADED mode randomly because of slight power drops or > "bad" IDE cabling. How do you test (and fix) something like this? revive the drive and hope the same drive doesn't happen again? ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664