Date: Fri, 18 Sep 2020 00:43:21 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 222425] GPT broken after "gpart backup ada0 | gpart restore -F ada1" Message-ID: <bug-222425-227-SchKWGQwpN@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-222425-227@https.bugs.freebsd.org/bugzilla/> References: <bug-222425-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D222425 Louis <lrb@minmet.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lrb@minmet.org --- Comment #13 from Louis <lrb@minmet.org> --- I had this exact same problem (11.2), and this is the only page that I was = able to find which had the same complaints. Nothing I did fixed it. Eventually, after wiping the disk, I tried a clean install, having concluded that it might be a hardware problem. It booted. Curious. Then it hit me: gpart backup ada0 | gpart restore -F ada1 gpart bootcode -b /boot/pmbr -p /boot/gptboot -i 1 ada1 actually *is* the problem. I ended up manually repartitioning the disk with gpart create then manually creating the partitions (and doing the gpart bootcode bit as above). All works. Guesses: either something is wrong with backup/restore, or having a larger = disk causes the problem. Since examining the output of "backup" doesn't indicate anything disk-size related that changes, I'm guessing that "restore" doesn'= t do quite the same thing as "create". Possibly if one did a "create" prior to the backup/restore, it might work o= ut differently. Anyway, this has been my experience, so if nothing else works and you lande= d on this page, try my "solution" and good luck to y'all. (If nothing else, it got me to create an account!) --=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?bug-222425-227-SchKWGQwpN>