From owner-freebsd-questions@freebsd.org Tue Aug 2 21:42:03 2016 Return-Path: Delivered-To: freebsd-questions@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 C44CDBA87AA for ; Tue, 2 Aug 2016 21:42:03 +0000 (UTC) (envelope-from merlyn@geeks.org) Received: from mail.geeks.org (mail.geeks.org [IPv6:2001:470:c2ca:1::1]) (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 A76D61BE9 for ; Tue, 2 Aug 2016 21:42:03 +0000 (UTC) (envelope-from merlyn@geeks.org) Received: from mail.geeks.org (localhost [127.0.0.1]) by after-clamsmtpd.geeks.org (Postfix) with ESMTP id 94191110235; Tue, 2 Aug 2016 16:42:02 -0500 (CDT) Received: by mail.geeks.org (Postfix, from userid 1003) id 71B9F110234; Tue, 2 Aug 2016 16:42:02 -0500 (CDT) Date: Tue, 2 Aug 2016 16:42:02 -0500 From: Doug McIntyre To: Trond =?iso-8859-1?Q?Endrest=F8l?= Cc: Doug McIntyre , freebsd-questions@freebsd.org Subject: Re: FreeBSD-10.3-RELEASE-amd64-memstick.img broken? Message-ID: <20160802214202.GA46160@geeks.org> References: <20160802184142.GA45983@geeks.org> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.6.1 (2016-04-27) X-Virus-Scanned: ClamAV using ClamSMTP X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Aug 2016 21:42:03 -0000 On Tue, Aug 02, 2016 at 08:48:34PM +0200, Trond Endrestøl wrote: > On Tue, 2 Aug 2016 20:45+0200, Trond Endrestøl wrote: > > On Tue, 2 Aug 2016 13:41-0500, Doug McIntyre wrote: > > > > > I've tried several times to have systems boot off of > > > FreeBSD-10.3-RELEASE-amd64-memstick.img ... > > > Error 1 > > > LBA 1339168 Invalid Format > > > > > > and then a boot prompt, that fails to boot further. > > You might need correct the primary and secondary GPT's on the memstick > > by running: > > > > gpart recover da0 # or da1, etc > > > > It's due to your memstick being larger than the image. > > No, I'm wrong. The advice above applies only to > FreeBSD-10.3-RELEASE-amd64-uefi-memstick.img. Yep, doesn't seem to be needed.. tritium:> gpart recover da2 da2 recovering is not needed