From owner-freebsd-stable@FreeBSD.ORG Wed Jan 27 22:52:47 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 995C8106566C for ; Wed, 27 Jan 2010 22:52:47 +0000 (UTC) (envelope-from mattjreimer@gmail.com) Received: from mail-yx0-f192.google.com (mail-yx0-f192.google.com [209.85.210.192]) by mx1.freebsd.org (Postfix) with ESMTP id 541748FC1E for ; Wed, 27 Jan 2010 22:52:47 +0000 (UTC) Received: by yxe30 with SMTP id 30so61770yxe.29 for ; Wed, 27 Jan 2010 14:52:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=8nbnPR6HFhOx/7O73qYzJiecgoQDQRe3DqtON9pr0EY=; b=Z4yAy4HwB+6wyozxrLkZWodzVYx5a1mqg+ZXb/2ERsCKmzudZKMq9UiDC/ajOjccDf ZseOQB5p+pDI0t79/1EMYYqs1/CNZZvn44EOTTkBVtdyNgaJelF+VB9lkRgBm3xc39lL RrWbPQmS1MJMwIZCFVdf1AfvnP5ruvo+LKSlU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=c5kPpoDn9pq7ariNaqkgYjkP1P45u3d3BiwlJBTkxo1cZ10wmax+VBa4WvyVyigMMh CAUJ2MZm+pBnST+SHx5HfoOve4l5+O31k/femd+emJvmHpEhQWmCFPWPumkASDVVKrfF T2J1XAfPu31kANyiIfreNwdjEdYWbG9v8L8/k= MIME-Version: 1.0 Received: by 10.150.252.13 with SMTP id z13mr13629505ybh.116.1264632766586; Wed, 27 Jan 2010 14:52:46 -0800 (PST) In-Reply-To: <432A0ECC-A743-4D24-B508-1EDC9912DD5E@gromit.dlib.vt.edu> References: <432A0ECC-A743-4D24-B508-1EDC9912DD5E@gromit.dlib.vt.edu> Date: Wed, 27 Jan 2010 14:52:46 -0800 Message-ID: From: Matt Reimer To: Paul Mather Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-stable@freebsd.org Subject: Re: ZFS pool upgrade to v14 broke ZFS booting X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Jan 2010 22:52:47 -0000 On Wed, Jan 27, 2010 at 11:18 AM, Paul Mather wrote: > I have a FreeBSD guest running under VirtualBox 3.1.2 on Mac OS X. It's > running a recent 8-STABLE and is a ZFS-only install booting via gptzfsboot. > I use this VirtualBox guest as a test install. > > A day or so ago I noticed "zpool status" report that my pool could be > upgraded from v13 to v14. I did this, via "zfs upgrade -a". > > Today, when attempting to fire up this FreeBSD guest in VirtualBox I get > this on the console: > > ===== > ZFS: unsupported ZFS version 14 (should be 13) > No ZFS pools located, can't boot > _ > ===== > > and the boot halts at that point. I don't see the boot menu I normally see > that lists the opportunity to boot single-user; disable ACPI; and so on. > > Has anyone else experienced this? Is this a mismatch between gptzfsboot > and my current pool version? (Gptzfsboot includes the message I'm seeing.) > Am I supposed to rebuild and replace gptzfsboot every time the pool version > is updated? (There was no advisory in /usr/src/UPDATING concerning this, > nor do I remember seeing it elsewhere.) > > Yes, you're running a version of gptzfsboot that only knows how to run version 13 and below. The commit that brought in version 14 support also bumped the version number for gptzfsboot though it doesn't look like any of the code changed; perhaps version 14 doesn't change anything that gptzfsboot cares about. Try rebuilding and reinstalling gptzfsboot and zfsloader to see if that helps: cd /sys/boot make cleandir make cleandir make obj make depend make all make install gpart bootcode -p /boot/gptzfsboot -i 1 /dev/somedisk Of course adjust the gpart command for your setup. Matt