From owner-freebsd-geom@FreeBSD.ORG Wed Aug 3 15:46:26 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 E856516A41F; Wed, 3 Aug 2005 15:46:26 +0000 (GMT) (envelope-from snow@teardrop.org) Received: from imladris.teardrop.org (imladris.teardrop.org [66.92.66.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5D17643D4C; Wed, 3 Aug 2005 15:46:26 +0000 (GMT) (envelope-from snow@teardrop.org) Received: by imladris.teardrop.org (Postfix, from userid 100) id 786CFBE20E; Wed, 3 Aug 2005 11:46:30 -0400 (EDT) Date: Wed, 3 Aug 2005 11:46:30 -0400 From: James Snow To: Pawel Jakub Dawidek Message-ID: <20050803154630.GD9486@teardrop.org> References: <20050803012515.GA1227@teardrop.org> <20050803055847.GD59370@garage.freebsd.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050803055847.GD59370@garage.freebsd.pl> User-Agent: Mutt/1.4.2.1i Cc: freebsd-geom@freebsd.org Subject: Re: gmirror on boot device after upgrade from 5.4 to 6.0? 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, 03 Aug 2005 15:46:27 -0000 On Wed, Aug 03, 2005 at 07:58:47AM +0200, Pawel Jakub Dawidek wrote: > > I'm not aware of any issues. The main difference is root_mount KPI used > to hold boot process, but it works well for me. > Please, provide more details asap, so I can work on issues before 6.0. Well, my 6.x sources on this machine are about a month old. (Long story.) Also, I got it to boot from gmirror again through some strange path that involved booting off of the components of the gmirror devices a couple of times, panicking a few more times, and finally resyncing the primary drive in the pair. It seems to be working fine now and I'm updating the machine to 6.0-BETA1. Let's attribute this one to PEBCAK for the time being. I'll let you know if I have any further trouble. -Snow