From owner-freebsd-hardware@FreeBSD.ORG  Mon Nov  3 01:44:00 2014
Return-Path: <owner-freebsd-hardware@FreeBSD.ORG>
Delivered-To: freebsd-hardware@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id C705AC98;
 Mon,  3 Nov 2014 01:44:00 +0000 (UTC)
Received: from potato.growveg.org (potato.growveg.org [62.49.247.163])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 86A38EB;
 Mon,  3 Nov 2014 01:44:00 +0000 (UTC)
Received: from john by potato.growveg.org with local (Exim 4.84 (FreeBSD))
 (envelope-from <john@potato.growveg.org>)
 id 1Xl6gI-000OSf-1H; Mon, 03 Nov 2014 01:43:42 +0000
Date: Mon, 3 Nov 2014 01:43:41 +0000
From: John <freebsd-lists@potato.growveg.org>
To: freebsd-hardware@freebsd.org, freebsd-fs@freebsd.org
Subject: Re: gptboot: invalid backup GPT header
Message-ID: <20141103014341.GA91255@potato.growveg.org>
Mail-Followup-To: freebsd-hardware@freebsd.org, freebsd-fs@freebsd.org
References: <20141101224426.GA69717@potato.growveg.org>
 <alpine.BSF.2.11.1411020653130.97570@wonkity.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <alpine.BSF.2.11.1411020653130.97570@wonkity.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
Sender: John <john@potato.growveg.org>
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: john@potato.growveg.org
X-SA-Exim-Scanned: No (on potato.growveg.org); SAEximRunCond expanded to false
X-BeenThere: freebsd-hardware@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: General discussion of FreeBSD hardware <freebsd-hardware.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-hardware>, 
 <mailto:freebsd-hardware-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hardware/>
List-Post: <mailto:freebsd-hardware@freebsd.org>
List-Help: <mailto:freebsd-hardware-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hardware>, 
 <mailto:freebsd-hardware-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Nov 2014 01:44:00 -0000

On Sun, Nov 02, 2014 at 07:15:59AM -0700, Warren Block wrote:
> Clearing the last blocks will remove the warning, at least if the 
> assumption is correct.  ZFS is not supposed to be using the last 
> portion of the disk(*) to make replacing disks of slightly different 
> sizes easier.  Still, I would back up either the whole array, the 
> whole disk, or at least the last 33 blocks of mfid1 first.

Thanks for replying. So, in short - is my data on the array in any 
danger, or is this just a cosmetic issue?

[I think the reason it happened is that during the install process, 
where the installer asks you to choose partitions, I removed 
*everything* from mfid1,2 & 3 as I knew zfs likes to deal with the raw 
disk. I don't want to have to blat the system again though, unless 
absolutely necessary].

-- 
John