#Easy to boot on partition code#

Partitioning tools to provide optimum performance with Advanced FormatР”Вisks, SSD devices, and some types of RAID configurations, 1 MiB is a

The 1 MiB partition alignment, policies used by most modern disk Space, so creating a larger BIOS boot partition is advisable. It can be as smallР”Р„s about 30 KiB however, future boot loaders might require more The BIOS boot partition is typically quite small. Looking at the Wikipedia page on BIOS boot partitions it looks as though it's really your choice. Instead there's an EFI system partition that contains a completely different 'stage 1' bootloader, which is able to mount /boot and access the 'stage 2' files on its own, without needing 'stage 1.5' as an intermediate step. On a system that uses EFI-style booting, there's no BIOS boot partition.

#Easy to boot on partition code#

It holds the 'stage 1.5' code that the bootloader uses to mount the partition with the 'stage 2' files.

The BIOS boot partition is only applicable when you're using legacy MBR-style booting with a GPT disk.

The /boot directory contains the majority of the bootloader code and its configuration this is what GRUB calls 'stage 2'.

This is different from the BIOS boot partition. Note that some systems have a separate partition for the /boot directory, containing a filesystem with other files used by the bootloader. Create a separate (larger) partition for your filesystem.

The BIOS boot partition should be very small: a megabyte is more than enough. On a GPT disk, that area is used by the (larger) partition table and isn't available for bootloader code, so the bootloader code goes in a small partition instead.

A BIOS boot partition doesn't contain a filesystem it's just a place to put some GRUB code that on an MBR disk would've been located immediately after the boot sector, before the start of the first partition.