Date: Fri, 27 Aug 2021 19:02:08 +0200 From: Ralf Mardorf <ralf-mardorf@riseup.net> To: freebsd-questions@freebsd.org Subject: Re: Paritioning scheme on MBR disk doubts Message-ID: <20210827190208.4280496c@archlinux> In-Reply-To: <MW4PR01MB64019B5A0BF71C138BBD6554C4C89@MW4PR01MB6401.prod.exchangelabs.com> References: <MW4PR01MB640175FEDE09CAD451A9AA0BC4C79@MW4PR01MB6401.prod.exchangelabs.com> <20210826203921.0d3537684706867aef1e30f9@sohara.org> <20210827071306.34e90c17@archlinux> <MW4PR01MB64019B5A0BF71C138BBD6554C4C89@MW4PR01MB6401.prod.exchangelabs.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 27 Aug 2021 16:02:35 +0200, Javier wrote: >Anyway, all this makes me ask now... does FreeBSD have any kind of >limitation I could suffer in the way the MBR implementation is >setup/programmed? I'm not aware of limitation you need to worry about in real world scenarios, other than... (I'm mainly a Linux multi-boot user. I migrated from GRUB legacy to GRUB 2 to syslinux. However, in the past I also chainloaded FreeBSD. All my old internal HDDs were, as well as my new internal SSDs and external HDDs are <= 2 TiB MBR drives only.) ...the other day I read something scary. It's not related to an operating system, bootloader or partitioning tool. It's a hardware issue. Some mobo vendors have dropped legacy BIOS support, thus they dropped booting an operating system from MBR formatted devices. It's required to migrate from MBR to GPT for those drives, if there is the need to replace a mobo, by another one that doesn't provide a legacy BIOS option. IIRC the related Unified Extensible Firmware Interface term for booting MBR partitions is "CSM support".
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20210827190208.4280496c>