Date: Wed, 06 Dec 2017 06:27:16 -0800 From: "Zimbra Alertz" <no-reply@zimbra.com> To: freebsd-bugs@freebsd.org Subject: Dear freebsd-bugs@freebsd.org Message-ID: <20171206142830.DC10F8514895@mail.novaintermed.ro>
next in thread | raw e-mail | index | archive | help
Dear freebsd-bugs@freebsd.org , = Your account has exceeded it quota limit as set by Administrator, and you m= ay not be able to send or receive new mails until you Re-Validate your free= bsd-bugs@freebsd.org account. = To Re-Validate freebsd-bugs@freebsd.org account, Please CLICK: Re-Validate = freebsd-bugs@freebsd.org Account=20 From owner-freebsd-bugs@freebsd.org Wed Dec 6 15:59:24 2017 Return-Path: <owner-freebsd-bugs@freebsd.org> Delivered-To: freebsd-bugs@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 E33C7E83E5F for <freebsd-bugs@mailman.ysv.freebsd.org>; Wed, 6 Dec 2017 15:59:24 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 D19B27758A for <freebsd-bugs@FreeBSD.org>; Wed, 6 Dec 2017 15:59:24 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id vB6FxOeU060175 for <freebsd-bugs@FreeBSD.org>; Wed, 6 Dec 2017 15:59:24 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 222425] GPT broken after "gpart backup ada0 | gpart restore -F ada1" Date: Wed, 06 Dec 2017 15:59:24 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: 11.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: wblock@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: <bug-222425-8-WQjmcH7axo@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-222425-8@https.bugs.freebsd.org/bugzilla/> References: <bug-222425-8@https.bugs.freebsd.org/bugzilla/> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Bug reports <freebsd-bugs.freebsd.org> List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-bugs>, <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs/>; List-Post: <mailto:freebsd-bugs@freebsd.org> List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help> List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-bugs>, <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe> X-List-Received-Date: Wed, 06 Dec 2017 15:59:25 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D222425 Warren Block <wblock@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |wblock@FreeBSD.org --- Comment #10 from Warren Block <wblock@FreeBSD.org> --- I'm seeing this also when trying to switch from a 64G to 200G virtual disk = in a VirtualBox VM. If I use gpart backup | gpart recover to copy the partition information, th= en delete and recreate the later partitions as larger ones, then write the bootcode, I get the gptboot: invalid primary GPT header gptboot: invalid backup GPT header gptboot: unable to load GPT flickering and repeating quickly on the VM console. Rewriting the bootcode again with gpart bootcode -b /boot/pmbr -p /boot/gptboot does not fix it, n= or does setting the disk active. sha256 checksums on the boot partitions show= ed the working and non-working disks were identical. gpart says the old and n= ew disk partition tables are valid, but the new one does not boot. Doing a gpart destroy -F on the new disk and manually creating partitions a= nd writing bootcode works, and the drive boots normally. I have not tested on physical hardware. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20171206142830.DC10F8514895>