From owner-freebsd-hardware Fri Sep 13 7:53:40 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8A8BF37B4B3 for ; Fri, 13 Sep 2002 07:53:24 -0700 (PDT) Received: from flounder.jimking.net (flounder.jimking.net [209.205.176.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id A353D43EAC for ; Fri, 13 Sep 2002 07:53:23 -0700 (PDT) (envelope-from jim@jimking.net) Received: from jimking.net (charcoal.lgc.com [134.132.154.140]) (authenticated bits=0) by flounder.jimking.net (8.12.5/8.12.4) with ESMTP id g8DEqv8a060958 for ; Fri, 13 Sep 2002 09:52:58 -0500 (CDT) (envelope-from jim@jimking.net) Message-ID: <3D81FBC9.2070508@jimking.net> Date: Fri, 13 Sep 2002 09:52:57 -0500 From: Jim King User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.1) Gecko/20020826 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-hardware@freebsd.org Subject: 3Ware troubles Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I have a 3Ware 6200 with the latest firmware with a pair of drives in a RAID1 config. One of the drives flaked out, the 6200 marked the drive as bad, and kept on running - all is good. I replaced the failed drive and tried to rebuild the array, but original drive that's still on the 6200 comes up with a read error towards the end of the disk and the firmware aborts the rebuild. Help! 3Ware says the latest 3dm on Windows and Linux has a "force rebuild" option that will ignore read errors during a rebuild. Unfortunately it doesn't look like this option is available from the 3Ware BIOS or from the FreeBSD version of 3dm. Does anybody know a trick to initiate a "force rebuild" short of booting Linux or Windows on the box? Any other suggestions on recovery? I'm down to either booting Windows, rebuilding the array, and then replacing the second flaky drive; or just giving up and doing a complete reinstall (after replacing the flaky drive). Any comments on FreeBSD's support of 3Ware these days? It appears that after Mike Smith left the project no one has done any significant work (e.g. getting the latest 3dm). I don't exactly feel comfortable with the 3Ware/FreeBSD combo any more. Jim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message