Date: Fri, 30 Jun 2023 14:20:44 +0000 From: bugzilla-noreply@freebsd.org To: sysinstall@FreeBSD.org Subject: [Bug 271262] bsdinstaller in AutoZFS + MBR mode always wipes disklabel - rendering system non-bootable Message-ID: <bug-271262-8135-AErGh5O1Ih@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-271262-8135@https.bugs.freebsd.org/bugzilla/> References: <bug-271262-8135@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=3D271262 Allan Jude <allanjude@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |allanjude@FreeBSD.org --- Comment #8 from Allan Jude <allanjude@FreeBSD.org> --- I would concur that removing MBR support is better. There are significant issues with updating `zfsboot` (the next stage bootst= rap) in an MBR pool, since it lives within the partition which is opened exclusi= vely when the system is booted. So you have to use GEOM debug flags to allow scribbling over random offsets of the disk in order to update your bootcode. So even if it was not broken, it is a bad idea in general. It only really existed because of some BIOSes that couldn't boot from GPT, = but that was fixed with the "GPT + Active" and "Lenovo Fix" options. --=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-271262-8135-AErGh5O1Ih>