1 |
> |
2 |
> > The Gentoo Handbook says to create a small unformatted partition at the |
3 |
> > beginning of the (primary?) disk, then to create a FAT-32 partition for |
4 |
> > /boot, then whatever other partitions are required. |
5 |
> |
6 |
> Another question answered: yes, it has to be the primary disk. I installed |
7 |
> a |
8 |
> small test system on another disk. It has its own FAT-32 /boot partition, |
9 |
> in |
10 |
> which I set up a similar directory structure to the main system's. |
11 |
> Efibootmgr |
12 |
> still insisted on adding the UEFI entry to the main set, in spite of my |
13 |
> telling it to use the secondary disk. And the BIOS couldn't see the image |
14 |
> on |
15 |
> the secondary disk. |
16 |
> |
17 |
|
18 |
I found my BIOS didn't recognise the UEFI setup until it was |
19 |
specified/setup by efibootmgr, so that checks out. What was the efibootmgr |
20 |
command you were using for the second disk? |
21 |
|
22 |
The conclusion is that, at least on this motherboard, there is precisely |
23 |
> one |
24 |
> set of UEFI boot images, and it lives on the primary disk of the system. |
25 |
> Well, |
26 |
> I haven't yet worked out how much of it is on the disk and how much in |
27 |
> BIOS |
28 |
> storage. The point remains, however, that I can't spread boot images over |
29 |
> several disks. |
30 |
> |
31 |
|
32 |
That's pretty poor. |
33 |
|
34 |
What does efibootmgr show? |
35 |
|
36 |
I got the impression that I would be able to UEFI boot from multiple |
37 |
different devices, eg a USB drive with UEFI as well as the hard disk. |