Date: Mon, 07 Apr 2014 09:02:28 -0500 From: dweimer <dweimer@dweimer.net> To: Chris Nehren <cnehren+freebsd-stable@pobox.com> Cc: owner-freebsd-stable@freebsd.org, stable@freebsd.org Subject: Re: Note for those pulling in new ZFS feature flags Message-ID: <60a1b6ff504c5295479fc66c81e287a5@dweimer.net> In-Reply-To: <20140407135421.GA16385@behemoth> References: <20140407135421.GA16385@behemoth>
next in thread | previous in thread | raw e-mail | index | archive | help
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/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?60a1b6ff504c5295479fc66c81e287a5>