Date: Sun, 04 Sep 2016 10:31:37 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: =?UTF-8?B?W0J1ZyAyMTE3MTVdIFNvbWUgY29tcHV0ZXJzIGNhbiBub3QgYm9vdCDigJMg?= =?UTF-8?B?bm8gZmlsZSBzeXN0ZW0gZm91bmQgKGUuZy4gJ05vbi1TeXN0ZW0gZGlzayBv?= =?UTF-8?B?ciBkaXNrIGVycm9yIOKApicpIOKAkyB3aGVyZSB0aGUgR1BUIGFuZCBwYXJ0?= =?UTF-8?B?aXRpb25zIGFyZSBjcmVhdGVkIGJ5IGdwYXJ0KDgp?= Message-ID: <bug-211715-8-wIoaI6Zyvs@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-211715-8@https.bugs.freebsd.org/bugzilla/> References: <bug-211715-8@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211715 --- Comment #4 from Graham Perrin <grahamperrin@gmail.com> --- Another workaround, which was good for at least one TrueOS Desktop case (tracking FreeBSD-CURRENT) and is good for today's test case of GhostBSD 10.3: 01) boot from something other than the disk to which the OS was installed 02) use gpart(8) to show the status of the affected disk – the GPT *appears* to be 'OK' but know that the computer will not boot from that disk 03) use gpart(8) to backup, destroy and restore the GPT of the affected disk – then restart, and the computer will boot the installed OS. -- You are receiving this mail because: You are the assignee for the bug.help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-211715-8-wIoaI6Zyvs>