From owner-freebsd-questions@freebsd.org Sun Dec 6 18:02:34 2015 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 C5A5F9A0E71 for ; Sun, 6 Dec 2015 18:02:34 +0000 (UTC) (envelope-from vsasjason@gmail.com) Received: from mail-wm0-x22d.google.com (mail-wm0-x22d.google.com [IPv6:2a00:1450:400c:c09::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6517B10F5 for ; Sun, 6 Dec 2015 18:02:34 +0000 (UTC) (envelope-from vsasjason@gmail.com) Received: by wmww144 with SMTP id w144so123604881wmw.0 for ; Sun, 06 Dec 2015 10:02:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=oxLM5I2+RYJXyVPKPjVdfD0D9xDn/XddcqgJ/3KdZr4=; b=jU7MPaP/c56Ixn5nUZepG6AuEdAUdck6PZQPFSnqBrcuIm73HB1kowfB02B0wwS75G IC274sHDIZDd/KSpVsNMxb8n5gmdnccz1LXa0Z2Tkcrrj5gy3CPaYjgIJNZ+pe157YWO nWLNiaM1mqlSibo9StOHmpr3rVd1t9tWaPoIxZx/Brbu37fbyEjYHxkS0RwEyXZsYrn+ DawQXicQpUgcH0rni83iGoBJN50MF/2kDUdXIRDQU9puiZ34AUmqjtA6qO7IexSAr13s 82FDLEz0so71toMusr6QBDPs5HxTXM5QM+W9xsX9jWwJk2n8D4I975MgzCDd2kFLEJz2 S50Q== X-Received: by 10.194.2.33 with SMTP id 1mr32922662wjr.150.1449424952064; Sun, 06 Dec 2015 10:02:32 -0800 (PST) MIME-Version: 1.0 Received: by 10.194.140.75 with HTTP; Sun, 6 Dec 2015 10:02:12 -0800 (PST) In-Reply-To: <5663c0d6.8giker3InrIlK8n+%perryh@pluto.rain.com> References: <566299bf.2z11XFWfUMRFyXGs%perryh@pluto.rain.com> <5663c0d6.8giker3InrIlK8n+%perryh@pluto.rain.com> From: Anton Sayetsky Date: Sun, 6 Dec 2015 20:02:12 +0200 Message-ID: Subject: Re: resizing a memstick image, on FreeBSD 8 To: Perry Hutchison Cc: freebsd-questions@freebsd.org Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 Dec 2015 18:02:34 -0000 2015-12-06 7:00 GMT+02:00 Perry Hutchison : > Is it possible to accomplish that on the FreeBSD 8 system that I'm > using to set things up for the FreeBSD 10.2 install? While it is > the FreeBSD 8 kernel that suggests "recovery": > GEOM: da2: the secondary GPT table is corrupt or invalid. > GEOM: da2: using the primary only -- recovery suggested. > > the FreeBSD 8 gpart apparently does not understand "recover": > # gpart recover da2 > gpart: Unknown command: recover. > usage: gpart add [-b start] [-s size] -t type [-i index] [-l label] [-f flags] geom > gpart bootcode [-b bootcode] [-p partcode] [-i index] [-f flags] geom > gpart commit geom > gpart create -s scheme [-n entries] [-f flags] provider > gpart delete -i index [-f flags] geom > gpart destroy [-f flags] geom > gpart modify -i index [-l label] [-t type] [-f flags] geom > gpart set -a attrib -i index [-f flags] geom > gpart show [-lr] [geom ...] > gpart undo geom > gpart unset -a attrib -i index [-f flags] geom > gpart help > gpart list [name ...] > gpart status [-s] [name ...] > gpart load [-v] > gpart unload [-v] > > I didn't find any mention of recovering from a missing or corrupted > secondary GPT in either the FreeBSD 8 Handbook or the FreeBSD 8 > gpart(8) manpage. You can recover GPT after updating to 10. Even if one of the GPT copies corrupted, disk is fully functional.