From owner-freebsd-fs@FreeBSD.ORG Thu Jul 29 22:35:15 2010 Return-Path: Delivered-To: fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CB386106567B for ; Thu, 29 Jul 2010 22:35:15 +0000 (UTC) (envelope-from mm@FreeBSD.org) Received: from mail.vx.sk (core.vx.sk [188.40.32.143]) by mx1.freebsd.org (Postfix) with ESMTP id 406868FC08 for ; Thu, 29 Jul 2010 22:35:15 +0000 (UTC) Received: from core.vx.sk (localhost [127.0.0.1]) by mail.vx.sk (Postfix) with ESMTP id 37554941B1; Fri, 30 Jul 2010 00:18:37 +0200 (CEST) X-Virus-Scanned: amavisd-new at mail.vx.sk Received: from mail.vx.sk ([127.0.0.1]) by core.vx.sk (mail.vx.sk [127.0.0.1]) (amavisd-new, port 10024) with LMTP id GXzhdCkYg5e7; Fri, 30 Jul 2010 00:18:35 +0200 (CEST) Received: from [10.9.8.1] (188-167-78-139.dynamic.chello.sk [188.167.78.139]) by mail.vx.sk (Postfix) with ESMTPSA id 5E63B9418B; Fri, 30 Jul 2010 00:18:35 +0200 (CEST) Message-ID: <4C51FE41.8030906@FreeBSD.org> Date: Fri, 30 Jul 2010 00:18:41 +0200 From: Martin Matuska User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; sk; rv:1.8.1.23) Gecko/20090812 Lightning/0.9 Thunderbird/2.0.0.23 Mnenhy/0.7.5.0 MIME-Version: 1.0 To: David Newman References: <4C51ECAA.2070707@networktest.com> In-Reply-To: <4C51ECAA.2070707@networktest.com> X-Enigmail-Version: 1.1.1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Cc: fs@freebsd.org Subject: Re: fixing a busted ZFS upgrade X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Jul 2010 22:35:15 -0000 Booting from GPT ZFS was not officially supported before 8.1-RELEASE Here is a upgrade guide for users who want to run "zpool upgrade" on their ZFS boot pools: Excerpt from 9-CURRENT UPDATING file: BEGIN EXCERPT ZFS notes --------- When upgrading the boot ZFS pool to a new version, always follow these two steps: 1.) recompile and reinstall the ZFS boot loader and boot block (this is part of "make buildworld" and "make installworld") 2.) update the ZFS boot block on your boot drive The following example updates the ZFS boot block on the first partition (freebsd-boot) of a GPT partitioned drive ad0: "gpart bootcode -p /boot/gptzfsboot -i 1 ad0" Non-boot pools do not need these updates. END EXCERPT In case the boot record is messed even more, you need to reinstall it completely: "gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 ad0" For recovering a system that does not boot anymore, you can use mfsBSD ISO's: http://mfsbsd.vx.sk You can boot from the iso and repair the boot record. I recommend you check your gpart partitions with "gpart show" and verify discovered pools with "zpool import" (without any flags or arguments) first. mm Dňa 29. 7. 2010 23:03, David Newman wrote / napísal(a): > Attempting to upgrade an 8.0-RELEASE to 8.1-RELEASE failed on a system > running a bootable ZFS partition. > > The system boots to the loader prompt and complains there's no bootable > kernel. Running 'lsmod' shows there are four ZFS disks present. > > Thanks in advance for clues on fixing this, and also on the right way to > upgrade FreeBSD systems with bootable ZFS partitions. > > Steps to reproduce: > > 1. Build 8.0-RELEASE system following the freebsd.org wiki: > > http://wiki.freebsd.org/RootOnZFS/GPTZFSBoot/RAIDZ1 > > In this case the system uses raidz1 across four SATA drives. > > 2. Upgrade to 8.1-RELEASE using the 'FreeBSD Update' directions: > > http://www.freebsd.org/releases/8.1R/announce.html > > 3. After first reboot, system boots to the loader prompt. > > dn > > _______________________________________________ > freebsd-fs@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org"