| 1 |
On Sun, Apr 13, 2014 at 11:08 AM, Jonathan Callen <jcallen@g.o> wrote: |
| 2 |
> On 04/12/2014 08:19 AM, Tom H wrote: |
| 3 |
>> |
| 4 |
>> You can have a gpt partition table with BIOS but if you want to boot from that disk, you need a |
| 5 |
>> bios_boot partition (which the OP has) for grub to embed a binary. |
| 6 |
> |
| 7 |
> Technically, I don't think you need a bios_boot partition if you leave enough space between the |
| 8 |
> partition table and the first partition (I don't recall having a problem when my first partition |
| 9 |
> started 2048 sectors (1MiB) into the disk). |
| 10 |
|
| 11 |
You're correct if you're talking about an msdos-labelled disk with |
| 12 |
bios firmware because having the first partition start on 2048 as it |
| 13 |
does now rather on 63 as it used to because the post-mbr gap will |
| 14 |
always be big enough for grub to embed core.img. |
| 15 |
|
| 16 |
But on a gpt-labelled disk with bios firmware, there's a <something> |
| 17 |
mbr into which grub embeds boot.img but there's no post-mbr gap. So a |
| 18 |
bios_boot partition's needed in order to embed core.img (IIRC parted |
| 19 |
calls it grub_bios or bios_grub). |
Archives