From owner-freebsd-current@freebsd.org  Tue Mar 21 02:08:31 2017
Return-Path: <owner-freebsd-current@freebsd.org>
Delivered-To: freebsd-current@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id BA7CDD144B3
 for <freebsd-current@mailman.ysv.freebsd.org>;
 Tue, 21 Mar 2017 02:08:31 +0000 (UTC)
 (envelope-from bsd-lists@bsdforge.com)
Received: from udns.ultimatedns.net (static-24-113-41-81.wavecable.com
 [24.113.41.81])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 9E52718A
 for <freebsd-current@freebsd.org>; Tue, 21 Mar 2017 02:08:30 +0000 (UTC)
 (envelope-from bsd-lists@bsdforge.com)
Received: from ultimatedns.net (localhost [127.0.0.1])
 by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id v2L28Z68083833
 for <freebsd-current@freebsd.org>; Mon, 20 Mar 2017 19:08:41 -0700 (PDT)
 (envelope-from bsd-lists@bsdforge.com)
To: "FreeBSD CURRENT" <freebsd-current@freebsd.org>
From: "Chris H" <bsd-lists@bsdforge.com>
Subject: why are the GEOM secondary GPT tables always corrupt?
Date: Mon, 20 Mar 2017 19:08:41 -0700
Content-Type: text/plain; charset=UTF-8; format=fixed
MIME-Version: 1.0
Message-id: <55f81bad1176cc0135610f56549e85aa@ultimatedns.net>
Content-Transfer-Encoding: 8bit
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Mar 2017 02:08:31 -0000

I've seen this discussed before, but there were so many
"solutions", I was left feeling this *must* be some sort
of bug in GEOM/gpart. So. I just blew away the tables on
a USB3 flash drive:

# gpart destroy -F da0

# gpart create -s gpt da0

# gpart add -t freebsd-ufs -l jails da0

# newfs -U /dev/gpt/jails

Added an entry to fstab(5)
OK this should be good to go. Mount, and umount
all return as expected, as does fsck(8).

Upon reboot, I receive the following:

/dev/gpt/jails: clean, 29961779 free (27 frags, 3745219 blocks, 0.0%
fragmentation)
GEOM: diskid/DISK-E600665E1DC77749: the secondary GPT table is corrupt or
invalid.
GEOM: diskid/DISK-E600665E1DC77749: using the primary only -- recovery
suggested.

But why?

This is on:
FreeBSD 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r314700: amd64

Thanks for any information.

--Chris