From owner-freebsd-stable@FreeBSD.ORG Tue Aug 21 02:26:14 2007 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9EBB616A417 for ; Tue, 21 Aug 2007 02:26:14 +0000 (UTC) (envelope-from davids@webmaster.com) Received: from mail1.webmaster.com (mail1.webmaster.com [216.152.64.169]) by mx1.freebsd.org (Postfix) with ESMTP id 875C613C474 for ; Tue, 21 Aug 2007 02:26:14 +0000 (UTC) (envelope-from davids@webmaster.com) Received: from however by webmaster.com (MDaemon.PRO.v8.1.3.R) with ESMTP id md50001646705.msg for ; Mon, 20 Aug 2007 19:25:46 -0700 From: "David Schwartz" To: Date: Mon, 20 Aug 2007 19:25:11 -0700 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) In-Reply-To: <028f01c7e37a$d8f441b0$0c00a8c0@Artem> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138 Importance: Normal X-Authenticated-Sender: joelkatz@webmaster.com X-Spam-Processed: mail1.webmaster.com, Mon, 20 Aug 2007 19:25:46 -0700 (not processed: message from trusted or authenticated source) X-MDRemoteIP: 206.171.168.138 X-Return-Path: davids@webmaster.com X-MDaemon-Deliver-To: freebsd-stable@freebsd.org X-MDAV-Processed: mail1.webmaster.com, Mon, 20 Aug 2007 19:25:46 -0700 Subject: RE: A little story of failed raid5 (3ware 8000 series) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: davids@webmaster.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Aug 2007 02:26:14 -0000 > A day ago at 11 am i have turn off the server, > pull out the old driver, installed a new one, turned of the server > and started rebuild in an hour from remote location via web interface. > After about 5 minuted the machine became unresponsive. Tried rebooting > - nothing. I went to the machine and fingure out, that rebuild failed (0%) > and some data cannot be read because of bad sectors. Why would you power cycle a RAID 5 array with a failed drive? That's like the biggest no-no that there is. When you lose a drive on a RAID 5 array, you are vulnerable until a replacement drive is configured and the array is rebuilt. Any high risk operations during that time would be foolhardy. > So, no raid5 or even raid 6 for me any more. Never! Since RAID6 would have saved you from what presumably was a drive failure before a rebuild could be done, it's hard to understand why you would say this is a reason to avoid RAID 6. Perhaps you would do better to understand your failure and avoid the causes of the failure rather than avoiding the things you happened to be using at the time of the failure. If you get food poisoning while wearing a blue shirt, the solution is not to avoid blue shirts in the future. DS