| 1 |
On Sat, 28 Jan 2017 12:11:28 -0500, Alan Grimes wrote: |
| 2 |
|
| 3 |
> >> Device Start End Sectors Size Type |
| 4 |
> >> /dev/sdc1 2048 264191 262144 128M EFI System |
| 5 |
> >> /dev/sdc2 526336 537233407 536707072 255.9G Linux filesystem |
| 6 |
> >> /dev/sdc3 264192 526335 262144 128M BIOS boot |
| 7 |
> > You don't have a BIOS boot partition on a UEFI system. They are for |
| 8 |
> > compatibility when using GPT disks with BIOS systems, and even hen you |
| 9 |
> > don't put anything on them. |
| 10 |
> > |
| 11 |
> > Just create an EFI System partition, formatted using FAT and mounted |
| 12 |
> > at /boot as the first partition, then divide the rest of the disk |
| 13 |
> > between /, /home swap as you see fit. |
| 14 |
> |
| 15 |
> It appears to be a 2-stage boot process: |
| 16 |
> |
| 17 |
> BIOS boot -> Binary of GRUB bootstrap loader. |
| 18 |
|
| 19 |
You don't have a BIOS with a UEFI system. |
| 20 |
|
| 21 |
> Boot -> Grub libraries, config, and kernels. |
| 22 |
|
| 23 |
The boot manager in the firmware picks an EFI boot image from the ESP, |
| 24 |
usually sda1. Once it loads that it's job is done. The boot image can be |
| 25 |
a kernel or a secondary bootloader like GRUB. |
| 26 |
|
| 27 |
Really, there is rarely a point in using GRUB on a UEFI system. Any |
| 28 |
bootloader adds extra complication, GRUB does it in spades. Just use a |
| 29 |
boot manager like rEFInd or systemd-boot - the latter is the simpler to |
| 30 |
work with AFAICT. |
| 31 |
|
| 32 |
|
| 33 |
-- |
| 34 |
Neil Bothwick |
| 35 |
|
| 36 |
"We demand rigidly defined areas of doubt and uncertainty!" |
Archives