From owner-freebsd-geom@FreeBSD.ORG Tue Apr 25 05:18:22 2006 Return-Path: X-Original-To: freebsd-geom@freebsd.org Delivered-To: freebsd-geom@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6502516A401 for ; Tue, 25 Apr 2006 05:18:22 +0000 (UTC) (envelope-from cdjones-freebsd-geom@novusordo.net) Received: from correo.novusordo.net (cdjj.org [216.194.85.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id C40B143D55 for ; Tue, 25 Apr 2006 05:18:21 +0000 (GMT) (envelope-from cdjones-freebsd-geom@novusordo.net) Received: from [192.168.2.100] (S010600c049bda6b5.ed.shawcable.net [68.149.198.157]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by correo.novusordo.net (Postfix) with ESMTP id 5BE23114B3; Mon, 24 Apr 2006 23:18:17 -0600 (MDT) In-Reply-To: <000001c66318$82b3bc60$0f02a8c0@chimay> References: <000001c66318$82b3bc60$0f02a8c0@chimay> Mime-Version: 1.0 (Apple Message framework v749.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Chris Jones Date: Mon, 24 Apr 2006 23:18:15 -0600 To: Thomas Coppens X-Mailer: Apple Mail (2.749.3) Cc: freebsd-geom@freebsd.org Subject: Re: Replacing Failed Drive... with gvinum... again X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Apr 2006 05:18:22 -0000 On 18-Apr-06, at 12:47 PM, Thomas Coppens wrote: > More users are interested in this issue. Could someone give some > directions > on how to replace a failed drive with gvinum (RAID 1 and 5)? Hi, Thomas --- I think something along the following lines should work: 0. Install new disk, ensuring it has the same device name as the old one. 1. Partition / slice new disk in the same way as the old one, or to taste. 2. 'gvinum saveconfig' should write the gvinum configuration to the new disk. 3. 'gvinum start' or 'gvinum rebuildparity' as needed to rebuild the disk. With that said, I haven't tried this, and I don't have any equipment immediately at hand with which to test this, but it seems plausible. Cheers, Chris