BIOS boot partition: Difference between revisions

Revision as of 19:36, 29 June 2019

Revision as of 05:20, 30 November 2019

Line 1:

{{Refimprove|date=June 2014}}

The '''BIOS boot partition''' is a [[partitionPartition (computing)|partition]] on a [[data storage device]] that [[GNU&nbsp; GRUB]] uses on legacy [[BIOS]]-based [[personal computer]]s in order to [[Booting|boot]] an [[operating system]], when the actual [[boot device]] contains a [[GUID Partition Table]] (GPT). Such a layout is sometimes referred to as BIOS/GPT boot.<ref>{{cite web

| url = https://wiki.archlinux.org/index.php/GUID_Partition_Table

| title = GUID Partition Table

Line 13:

[[File:GNU GRUB components.svg|thumb|upright=2|In the example 2 above, [[GRUB&nbsp;2]] stores its {{Mono|core.img}} in a BIOS boot partition.]]

When used, the BIOS boot partition contains the second stage of the [[boot loader]] program, such as the [[GRUB&nbsp;2]]; the first stage is the code that is contained within the [[Master Boot Record]] (MBR). Use of this partition is not the only way BIOS-based boot can be performed while using GPT-partitioned hard drives; however, complex boot loaders such as [[GRUB 2]] cannot fit entirely within the confines of the MBR's 398<!-- MBR with disk timestamp, disk signature, AAP and NEWLDR support --> to 446<!-- classic MBR without any extensions --> bytes of space, thus they need an ancillary storage space. On MBR disks, such boot loaders typically use the sectors immediately following the MBR for this storage; that space is usually known as the "MBR gap". No equivalent unused space exists on GPT disks, and the BIOS boot partition is a way to officially allocate such space for use by the boot loader.

The [[globally unique identifier]] (GUID) for the BIOS boot partition in the GPT scheme is <tt>21686148-6449-6E6F-744E-656564454649</tt><ref>{{cite web

Line 20:

| accessdate = 2014-06-26

| website = gnu.org

}}</ref> (which, when written to a GPT in the required little endian fields, forms the ASCII string "<tt>Hah!IdontNeedEFI</tt>").<!-- See talk page for some notes on endianness confusion. --> In the context of GPT on a BIOS-based computer, a BIOS boot partition is similar in some respects to the [[EFI Systemsystem partition]], which is used by systems based on [[Extensible Firmware Interface|EFI]]. The EFI System partition holds a filesystem and files used by the UEFI, while the BIOS boot partition is used in BIOS-based systems and accessed without a filesystem by holding raw binary code.

The size requirements for a BIOS boot partition are quite low so it can be as small as about 30&nbsp;KiB; however, as future boot loaders might require more space, 1&nbsp;MiB might be a reasonable BIOS boot partition size. Due to the [[1 MB partition alignment|1&nbsp;MiB partition alignment]] policies used by most modern disk partitioning tools to provide optimum performance with [[Advanced Format]] disks, [[Solid-state drive|SSD devices]] and certain [[RAID]] configurations, some room is left allowing the placement of a BIOS boot partition between the GPT and the first partition aligned that way. If created by utilizing that free space, the BIOS boot partition would be out of the GPT alignment specification, but that is not very important{{cncitation needed|date=June 2017|reason=Who says it is unimportant? Is this just opinion or is it declared in the partitioning standard / bootloader's documentation? Even if it is *written* to rarely, it is *read* every boot, and anything that clobbers it will prevent the system from being able to boot.}} since it is written to very infrequently.

== Creation ==

Line 34:

== See also ==

* [[Unified Extensible Firmware Interface]] (UEFI)

* [[EFI System partition]] (ESP)

* [[Windows To Go]]