From owner-freebsd-stable@FreeBSD.ORG Wed Jul 31 09:20:32 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 6032A61D for ; Wed, 31 Jul 2013 09:20:32 +0000 (UTC) (envelope-from trond@fagskolen.gjovik.no) Received: from smtp.fagskolen.gjovik.no (smtp.fagskolen.gjovik.no [IPv6:2001:700:1100:1:200:ff:fe00:b]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id C2FDA24BA for ; Wed, 31 Jul 2013 09:20:31 +0000 (UTC) Received: from mail.fig.ol.no (localhost [127.0.0.1]) by mail.fig.ol.no (8.14.7/8.14.7) with ESMTP id r6V9KQup093442 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 31 Jul 2013 11:20:26 +0200 (CEST) (envelope-from trond@fagskolen.gjovik.no) Received: from localhost (trond@localhost) by mail.fig.ol.no (8.14.7/8.14.7/Submit) with ESMTP id r6V9KQB0093439; Wed, 31 Jul 2013 11:20:26 +0200 (CEST) (envelope-from trond@fagskolen.gjovik.no) X-Authentication-Warning: mail.fig.ol.no: trond owned process doing -bs Date: Wed, 31 Jul 2013 11:20:26 +0200 (CEST) From: =?ISO-8859-1?Q?Trond_Endrest=F8l?= Sender: Trond.Endrestol@fagskolen.gjovik.no To: J David Subject: Re: Problem with zfsloader on 9.2-BETA2 In-Reply-To: Message-ID: References: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) Organization: Fagskolen Innlandet OpenPGP: url=http://fig.ol.no/~trond/trond.key MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="2055831798-939378192-1375262426=:1327" X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED autolearn=unavailable version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on mail.fig.ol.no Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 31 Jul 2013 09:20:32 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --2055831798-939378192-1375262426=:1327 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT On Wed, 31 Jul 2013 03:49-0400, J David wrote: > In order to test ZFS on the upcoming 9.2 release, we upgraded a > non-production 8.4 root-on-ZFS fileserver to 9.2-BETA2. > > The result was a non-bootable system. The first problem was > gptzfsboot, but that was our fault? it never got upgraded when we > switched to feature flags. So some time with the 8.4 live CD (the 9.x > CD's do not boot on this system -- kern/162160 ) solved that. > > But the system still wouldn't boot, moving on to: > > ZFS: can't find pool by guid > ZFS: can't find pool by guid > > We got around this by interrupting the stage1 loader and invoking > data/root:/boot/zfsloader.old instead. Then we moved the 9.2 > zfsloader out of the way and restored the 8.4 loader. > > So this system only boots with the 9.2 gptzfsboot and the 8.4 zfsloader. > > To the best of my knowledge, there is nothing broken or out of date > with this zpool: > > $ zpool status > pool: data > state: ONLINE > scan: resilvered 451G in 70h36m with 0 errors on Fri Feb 17 00:26:19 2012 > config: > > NAME STATE READ WRITE CKSUM > data ONLINE 0 0 0 > raidz2-0 ONLINE 0 0 0 > da2p1 ONLINE 0 0 0 > da3p1 ONLINE 0 0 0 > da4p1 ONLINE 0 0 0 > da5p1 ONLINE 0 0 0 > da6p1 ONLINE 0 0 0 > da7p1 ONLINE 0 0 0 > logs > gpt/slog0 ONLINE 0 0 0 > cache > gpt/cache1 ONLINE 0 0 0 > > errors: No known data errors > $ zpool upgrade > This system supports ZFS pool feature flags. > > All pools are formatted using feature flags. > > Every feature flags pool has all supported features enabled. > > > Does anyone know why the 9.2 zfsloader won't load it? > > Thanks! I'm curious as to why you use da?p1 as the freebsd-zfs partitions. Where does the freebsd-boot partition reside? da?p2? What does the "gpart show" command tell you? I normally use *p1 for freebsd-boot, *p2 for freebsd-swap and *p3 for freebsd-swap. I know some people who put freebsd-zfs on *p2 and freebsd-swap on *p3. Maybe the partitions are interchangeable after all. As a general rule, I think it's wise to always update the boot blocks whenever you plan to upgrade the pool format or the filesystems. If I have the time later this afternoon, or maybe tomorrow, I will attempt the following on a couple of VMs: 1. Install 8.4-RELEASE with ZFS SPA v28. 2. Upgrade ZFS SPA to v5000. Updating the boot blocks shouldn't be necessary this time. 3. Upgrade by source to 8.4-STABLE and see what happens then. 4. Upgrade by source to 9.2-BETA2, and possibly update the boot blocks using the installed files prior to rebooting, and see what happens then. A second attempt would involve going straight from 8.4-RELEASE to 9.2-BETA2. I'll let you know how well I fared. -- +-------------------------------+------------------------------------+ | Vennlig hilsen, | Best regards, | | Trond Endrestøl, | Trond Endrestøl, | | IT-ansvarlig, | System administrator, | | Fagskolen Innlandet, | Gjøvik Technical College, Norway, | | tlf. mob. 952 62 567, | Cellular...: +47 952 62 567, | | sentralbord 61 14 54 00. | Switchboard: +47 61 14 54 00. | +-------------------------------+------------------------------------+ --2055831798-939378192-1375262426=:1327--