On Fri, 2019-11-29 at 11:35 +0000, Patrick O'Callaghan wrote:
On Thu, 2019-11-28 at 20:15 -0800, Samuel Sieb wrote:
> On 11/28/19 2:50 PM, Patrick O'Callaghan wrote:
> > Thanks. The only line that looks relevant seems to be this one (from
> > /var/log/anaconda/journal.log):
> >
> > localhost-live anaconda[2737]: program: Running in chroot
'/mnt/sysroot'... efibootmgr -c -w -L Fedora -d /dev/sda -p 1 -l
\EFI\fedora\shimx64.efi
> >
> > which doesn't look like it needs to be changed (given that the new
> > drive will become /dev/sda on rebooting).
>
> The problem is that the BIOS does not know about /dev/sda, it has an
> identifier for the physical disk. You're changing that, so you will
> most likely need to change the EFI boot entry. Look at the "Fedora"
> entry in "efibootmgr -v" to see what I mean.
It currently shows:
Boot0000* Fedora
HD(1,GPT,7554722f-6e12-4c21-89da-5c43790ced1e,0x800,0x12c000)/File(\EFI\fedora\shimx64.efi)
However the man page for efibootmgr only talks about disks in terms of
/dev/... so I'm not clear on how to a) identify the new SSD, and b)
tell the boot manager about it.
Never mind, I figured it out (I think). I just use the *current* /dev
entry for the new drive and efibootmgr figures out the proper id.
poc