From owner-freebsd-stable@FreeBSD.ORG Tue Aug 21 04:58:00 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 D886916A419 for ; Tue, 21 Aug 2007 04:58:00 +0000 (UTC) (envelope-from matrix@itlegion.ru) Received: from corpmail.itlegion.ru (corpmail.itlegion.ru [84.21.226.211]) by mx1.freebsd.org (Postfix) with SMTP id 2A97713C457 for ; Tue, 21 Aug 2007 04:57:59 +0000 (UTC) (envelope-from matrix@itlegion.ru) Received: (qmail 96391 invoked from network); 21 Aug 2007 08:57:58 +0400 Received: from unknown (HELO Artem) (192.168.0.12) by 84.21.226.211 with SMTP; 21 Aug 2007 08:57:58 +0400 X-AntiVirus: Checked by Dr.Web [version: 4.33, engine: 4.33.5.10110, virus records: 238958, updated: 20.08.2007] Message-ID: <02fe01c7e3af$d3b86ed0$0c00a8c0@Artem> From: "Artem Kuchin" To: , References: Date: Tue, 21 Aug 2007 08:57:22 +0400 Organization: IT Legion MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="koi8-r"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.3138 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138 Cc: 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 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 04:58:00 -0000 David Schwartz wrote: >> 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. Um.. it is because i did not have a map of hot swap baskets to conroller ports and i needed to check every driver basket to understand which port it sits on. I have no choise, i think. >> 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. Read the post before. I still don't known which driver has the bad sectors. And it is very posible that EACH driver has them. RAID6 would not help then. -- Artem