From owner-freebsd-stable@FreeBSD.ORG Mon Apr 7 14:02:36 2014 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 31BEFA73; Mon, 7 Apr 2014 14:02:36 +0000 (UTC) Received: from webmail.dweimer.net (24-240-198-187.static.stls.mo.charter.com [24.240.198.187]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "webmail2.dweimer.local", Issuer "webmail2.dweimer.local" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id F0B531E8; Mon, 7 Apr 2014 14:02:35 +0000 (UTC) Received: from www.dweimer.net (webmail [192.168.5.2]) by webmail.dweimer.net (8.14.7/8.14.7) with ESMTP id s37E2Sib026410 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 7 Apr 2014 09:02:28 -0500 (CDT) (envelope-from dweimer@dweimer.net) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Mon, 07 Apr 2014 09:02:28 -0500 From: dweimer To: Chris Nehren Subject: Re: Note for those pulling in new ZFS feature flags Organization: dweimer.net Mail-Reply-To: dweimer@dweimer.net In-Reply-To: <20140407135421.GA16385@behemoth> References: <20140407135421.GA16385@behemoth> Message-ID: <60a1b6ff504c5295479fc66c81e287a5@dweimer.net> X-Sender: dweimer@dweimer.net User-Agent: Roundcube Webmail/1.0-rc Cc: owner-freebsd-stable@freebsd.org, stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: dweimer@dweimer.net List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Apr 2014 14:02:36 -0000 On 04/07/2014 8:54 am, Chris Nehren wrote: > Not too long ago I upgraded my FreeBSD workstation to 10-STABLE > from 10-RELEASE in order to try newcons. After I upgraded to > 10-STABLE, I saw in `zpool status` that my pools could be > upgraded to a new version of ZFS. I did this, and then needed to > reboot the machine for unrelated reasons. When it came back up, > it refused to boot because gptzfsboot couldn't import the pools. > > I solved this by re-running `gpart bootcode` for the afflicted > drives. This was a bit trying, though, as my workstation is the > only FreeBSD machine I have readily available. So, for those > upgrading their zpools, be careful and remember to fix the > bootcode if you're using ZFS for the root filesystem. > > I have also filed a PR to note that situations like these should > be noted in UPDATING, kern/188328. Hopefully this post saves > someone else a few hours. If I am not mistaken, zpool upgrade displays a message on the screen indicating that you should do the gpart bootcode after it completes the upgrade. -- Thanks, Dean E. Weimer http://www.dweimer.net/