From owner-freebsd-questions@FreeBSD.ORG Fri Feb 7 16:30:08 2014 Return-Path: Delivered-To: freebsd-questions@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 96380F70 for ; Fri, 7 Feb 2014 16:30:08 +0000 (UTC) Received: from wonkity.com (wonkity.com [67.158.26.137]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 49E161FA5 for ; Fri, 7 Feb 2014 16:30:08 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.7/8.14.7) with ESMTP id s17GU4so006628; Fri, 7 Feb 2014 09:30:04 -0700 (MST) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.7/8.14.7/Submit) with ESMTP id s17GU4xi006625; Fri, 7 Feb 2014 09:30:04 -0700 (MST) (envelope-from wblock@wonkity.com) Date: Fri, 7 Feb 2014 09:30:04 -0700 (MST) From: Warren Block To: Christopher Sean Hilton Subject: Re: gptboot: unable to read backup GPT header In-Reply-To: <20140205222751.GA48019@geonosis.vindaloo.com> Message-ID: References: <20140205222751.GA48019@geonosis.vindaloo.com> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (wonkity.com [127.0.0.1]); Fri, 07 Feb 2014 09:30:04 -0700 (MST) Cc: freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Feb 2014 16:30:08 -0000 On Wed, 5 Feb 2014, Christopher Sean Hilton wrote: > I'm getting this on a freshly installed FreeBSD 9.2 System. It boots > fine but the error message has me concerned. Has anyone encountered > and fixed this? New to me. Could you describe the hardware, particularly whether a RAID controller or an external USB drive is involved? The exact output of the error message (in context) would help. The output of 'gpart show' might be useful.