ZFS pool upgrade to v14 broke ZFS booting
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.) Now I have to figure out how to dig out from this. Well, I guess that's what test installations are for... :-) Cheers, Paul.___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: ZFS pool upgrade to v14 broke ZFS booting
On Wed, Jan 27, 2010 at 11:18 AM, Paul Mather p...@gromit.dlib.vt.eduwrote: 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 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: ZFS pool upgrade to v14 broke ZFS booting
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, On 2010/01/27 11:18, 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.) Now I have to figure out how to dig out from this. Well, I guess that's what test installations are for... :-) There is no on-disk format change that affects ZFS boot itself, but you will need to install new gptzfsboot. If you have another system and have the file, you can do it by booting from the LiveFS Disc, fetch it from network, and use gpart to install it. Cheers, - -- Xin LI delp...@delphij.nethttp://www.delphij.net/ FreeBSD - The Power to Serve! Live free or die -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.14 (FreeBSD) iQEcBAEBAgAGBQJLYMZSAAoJEATO+BI/yjfBgNcH/jwK8bZTlX6Dr0wKYRRaaa72 wuTswokvVLCr6xZJbo18/je8F68tXkYqBdPSVm2pZsZs4kBPw8gHzQWNdQcIudVN m4qhE8QlAZVd8DIXk6hJM+7A/k6k9vo6AtHYY/nvNsKrk9Xxo1rDI5cVo9WMJeB2 6ONbPAG6aDOGEFyICRo4NoB6Qbh/Ylzx4wiLkENrI2SdDDlZQ1YmaXl8RFtCAMoK LjnNt+G/cAIm/MvYzFbEDa1Ok5YD/Osc74P+fPJvJSYNd/QmJ4PU+Lb4MPsrKBU0 FtAHl5o3f7xz1YTwmybY+9Sw67izDIDc8lalNiguTj77Uj8zLiete91t/c7BmIE= =6CG3 -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: ZFS pool upgrade to v14 broke ZFS booting
On Wed, Jan 27, 2010 at 6:03 PM, Xin LI delp...@delphij.net wrote: On 2010/01/27 11:18, 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 There is no on-disk format change that affects ZFS boot itself, but you will need to install new gptzfsboot. If you have another system and have the file, you can do it by booting from the LiveFS Disc, fetch it from network, and use gpart to install it. Since this is so fatal, you might want to give them the option to continue here. I suspect that zpool format changes that truly break the boot loader (which is read-only at any rate) are uncommon where the chances of ending up in this situation (with an unbootable machine) are much more common. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: ZFS pool upgrade to v14 broke ZFS booting
On 28.01.2010 2:03, Xin LI wrote: There is no on-disk format change that affects ZFS boot itself, but you will need to install new gptzfsboot. If you have another system and have the file, you can do it by booting from the LiveFS Disc, fetch it from network, and use gpart to install it. Some time ago i had the same problem. I think it is good idea to add a note about updating gptzfsboot in src/UPDATING. -- WBR, Andrey V. Elsukov ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
