From owner-freebsd-geom@FreeBSD.ORG Wed Dec 14 02:52:11 2005 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 C69AC16A41F for ; Wed, 14 Dec 2005 02:52:11 +0000 (GMT) (envelope-from mark@gaiahost.coop) Received: from biodiesel.gaiahost.coop (biodiesel.gaiahost.coop [64.95.78.120]) by mx1.FreeBSD.org (Postfix) with ESMTP id 53A7E43D55 for ; Wed, 14 Dec 2005 02:52:11 +0000 (GMT) (envelope-from mark@gaiahost.coop) Received: from localhost (host-64-65-195-19.spr.choiceone.net [::ffff:64.65.195.19]) (AUTH: LOGIN mark@hubcapconsulting.com) by biodiesel.gaiahost.coop with esmtp; Tue, 13 Dec 2005 21:52:08 -0500 id 003940CB.439F88D9.000073A5 Received: by localhost (sSMTP sendmail emulation); Tue, 13 Dec 2005 21:52:22 -0500 Date: Tue, 13 Dec 2005 21:52:22 -0500 From: Mark Bucciarelli To: freebsd-geom@freebsd.org Message-ID: <20051214025222.GB2708@rabbit> Mail-Followup-To: freebsd-geom@freebsd.org References: <20051213131637.GC2188@rabbit> <20051213232008.GA749@garage.freebsd.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline In-Reply-To: <20051213232008.GA749@garage.freebsd.pl> User-Agent: Mutt/1.4.2.1i Subject: Re: How to recover a gmirror from a disaster 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: Wed, 14 Dec 2005 02:52:11 -0000 On Wed, Dec 14, 2005 at 12:20:08AM +0100, Pawel Jakub Dawidek wrote: > Could you add kern.geom.mirror.debug=3 to your /boot/loader.conf and > boot again? I'm sorry, with the previous posters help I was able to boot and this error no longer occurs. > +> This is 5.4-RELEASE. > +> > +> The da0 disk is good (I did a surface scan) and I can mount it and > +> backup the data when I put it in bay #2. > +> > +> So ... > +> > +> Did my command in step #6 cause this mess? If so, what should I > +> have used--forget first? > > If da1 was disconnected you should get an error, that mirror is not > complete. Yes, 'forget' is the right command. Yes, as is documented in the man page. > +> How can I get this disk to boot again? > > Actually you can simply: > > # gmirror label gm0 da0 > > No data will be lost. You can also boot from da0 directly. No data loss. My error was not using the forget command. m