From owner-freebsd-fs@FreeBSD.ORG Thu Dec 12 22:04:19 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5A646E2F; Thu, 12 Dec 2013 22:04:19 +0000 (UTC) Received: from mail-vb0-x236.google.com (mail-vb0-x236.google.com [IPv6:2607:f8b0:400c:c02::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id E36401D75; Thu, 12 Dec 2013 22:04:18 +0000 (UTC) Received: by mail-vb0-f54.google.com with SMTP id g10so765169vbg.27 for ; Thu, 12 Dec 2013 14:04:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type:content-transfer-encoding; bh=0HFd4eREWcbOKxgPWJ6OWUH/whb7uaLOl8zUrFzBJN0=; b=f+oFZc/OImnluvyu6uq1Kw/jX7BZ/n3ydioAMNjwUefmh5qMVhTW3VzE3c1L6PoM+F W4V4AamaiXiC4HX0QqXiF7CNtMc8Sll0IpEmdaveEE37W/WR43CeIVlB6ShqHkGcBupr XNbn1di+q6v5ssVS3Qmt0YiQADhS14bdj9J0gnWAa4IRHuhi8H/I5gXlxDOxetg+NjY1 Nezet9YhaHcO4xxcOUdu/g2/hzs3XoxsewAGpDaQOP6/PwAbJ3UceP5dC2KrHRaC0m8S KiNNw60cxAxKm5iDwceR+pnxLCO9rbvU3Xla6O5xac3ye1bjW2E+nHdl0s2mPRBULfbR AcjQ== MIME-Version: 1.0 X-Received: by 10.220.99.72 with SMTP id t8mr4977598vcn.10.1386885858128; Thu, 12 Dec 2013 14:04:18 -0800 (PST) Sender: artemb@gmail.com Received: by 10.221.9.2 with HTTP; Thu, 12 Dec 2013 14:04:18 -0800 (PST) In-Reply-To: <52AA26DA.30809@peterschmitt.fr> References: <52A6EB67.3000103@peterschmitt.fr> <52A99917.2050200@FreeBSD.org> <52A9AA45.2000907@peterschmitt.fr> <52A9ABEF.8080509@FreeBSD.org> <52AA26DA.30809@peterschmitt.fr> Date: Thu, 12 Dec 2013 14:04:18 -0800 X-Google-Sender-Auth: y39z1U8UriqqOUinpd5TOLdsJYU Message-ID: Subject: Re: 10.0-BETA4 (upgraded from 9.2-RELEASE) zpool upgrade -> boot failure From: Artem Belevich To: Florent Peterschmitt Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Cc: freebsd-fs , freebsd-stable stable , Andriy Gapon X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Dec 2013 22:04:19 -0000 On Thu, Dec 12, 2013 at 1:12 PM, Florent Peterschmitt wrote: >> do "zdb -l /dev/ada0" (and all other slices on ada0) and check >> whether it reports anything unexpected. >> >> --Artem > > rescue-bsd# zdb -l /dev/ada0 > -------------------------------------------- > LABEL 0 > -------------------------------------------- > failed to unpack label 0 > -------------------------------------------- > LABEL 1 > -------------------------------------------- > failed to unpack label 1 > -------------------------------------------- > LABEL 2 > -------------------------------------------- > failed to unpack label 2 > -------------------------------------------- > LABEL 3 > -------------------------------------------- > failed to unpack label 3 > > > Well=85 this sounds bad, right? This looks the way it's supposed to -- no unwanted ZFS pool info is found. Now repeat that for all ada0p? and make sure only the slice that's part of your pool shows ZFS labels and only for one pool. Think a bit about how bootloader figures out how your pool is built. All it has access to is a raw disk and partition table. So in order to find the pool it probes raw disk and all partitions trying to find ZFS labels and then uses info in those labels to figure out pool configuration. If bootloader finds stale ZFS labels left from a previous use of the disk in some other pool, it would potentially mess up detection of your real boot pool. --Artem