From owner-freebsd-current@FreeBSD.ORG Mon Jan 12 02:40:26 2009 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E4B31106566B for ; Mon, 12 Jan 2009 02:40:26 +0000 (UTC) (envelope-from morganw@chemikals.org) Received: from warped.bluecherry.net (unknown [IPv6:2001:440:eeee:fffb::2]) by mx1.freebsd.org (Postfix) with ESMTP id 821C58FC17 for ; Mon, 12 Jan 2009 02:40:26 +0000 (UTC) (envelope-from morganw@chemikals.org) Received: from volatile.chemikals.org (morganw-1-pt.tunnel.tserv8.dal1.ipv6.he.net [IPv6:2001:470:1f0e:47e::2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by warped.bluecherry.net (Postfix) with ESMTPSA id C01BAA303E6F; Sun, 11 Jan 2009 20:40:22 -0600 (CST) Received: from localhost (morganw@localhost [127.0.0.1]) by volatile.chemikals.org (8.14.3/8.14.3) with ESMTP id n0C2eEKs078473; Sun, 11 Jan 2009 20:40:17 -0600 (CST) (envelope-from morganw@chemikals.org) Date: Sun, 11 Jan 2009 20:40:13 -0600 (CST) From: Wes Morgan To: George Neville-Neil In-Reply-To: Message-ID: References: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: current@freebsd.org Subject: Re: GEOM and moving to CURRENT from 7.1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Jan 2009 02:40:27 -0000 On Sun, 11 Jan 2009, George Neville-Neil wrote: > Howdy, > > Beware if you are upgrading from a 7.1 system to CURRENT that you may > need to have the kernel options GEOM_MBR and GEOM_BSD in your kernel. > I spent a couple of hours dealing with this on my Thinkpad X60 today > which had, what I thought, was a pretty simple setup of 1 slice for BSD, > and a simple layout of /, swap and /usr. When I tried to boot the new > kernel I got to the mount error prompt and could not mount ad4p1 or > anything like it. Adding the GEOM_MBR and GEOM_BSD options back into the > kernel fixed things. Happily I was able to boot 7.1 still and fix this. There are several things to be aware of moving from GEOM_MBR|BSD to GEOM_PART_*. My label was "wrong" in gpart's eyes, and I had to relabel the drive with a copy of the same label (no data loss). I also have a ZFS root filesystem embedded in the "e" part of the slice, which was marked as "unused" in the label, and thus GEOM_PART_BSD created no device node in /dev. Changing it from "unused" to "ZFS" in the label was the solution to that. Unfortunately, during the process of "fixing" the label, grub stopped working, leaving my system without a boot loader. In the absence of a bootable live cd, I had to pop out the drive and plug it in to another system to install the standard boot loader. Was not a fun evening!