From owner-freebsd-questions@FreeBSD.ORG Fri Apr 29 17:45:10 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CC0D916A4CE for ; Fri, 29 Apr 2005 17:45:10 +0000 (GMT) Received: from wrongcrowd.com (dsl231-043-085.sea1.dsl.speakeasy.net [216.231.43.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5436643D1F for ; Fri, 29 Apr 2005 17:45:10 +0000 (GMT) (envelope-from matt@wrongcrowd.com) Received: from tbird ([192.168.1.95]:3497) by wrongcrowd.com with esmtp (Exim 4.34 (FreeBSD)) id 1DRZXI-000Ejc-5o for freebsd-questions@freebsd.org; Fri, 29 Apr 2005 10:44:20 -0700 Message-ID: <427272A1.9080800@wrongcrowd.com> Date: Fri, 29 Apr 2005 10:45:05 -0700 From: Matt Staroscik User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-questions@freebsd.org References: <20050429120035.A9EF916A4D7@hub.freebsd.org> In-Reply-To: <20050429120035.A9EF916A4D7@hub.freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) Subject: 3ware rebuild problems fixed X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Apr 2005 17:45:10 -0000 I solved my own problem a while back and neglected to post my solution. I hate it when people do that to me. :) My original post is here: http://lists.freebsd.org/pipermail/freebsd-questions/2004-November/064038.html The summary is simply this: when rebuilding a mirror on a 3ware 7000-2, the rebuild would crap out with a vague disk error message. Doing a dump on the volume uncovered a couple of read errors. Solution: The read errors were killing the rebuild process. The hard disk's built-in SMART error correction was not kicking in though, because it only corrects bad sectors on a write. I tried to fix the disk with fsck, but the damage was too low-level, I guess... Anyway, I deleted the files with read errors--luckily they were trivial--and then copied a load of files to the partition to fill up the empty space. This triggered a SMART sector repair--I verified that with a SMART checker from ports. Once the bad sectors were remapped, I was able to rebuild my array. Hope this helps someone! -- ***** I am Matt Staroscik and I approved this message. ****** matt@wrongcrowd.com * http://wrongcrowd.com * 4 8 15 16 23 42