On Thu, 2019-11-28 at 10:56 -0800, Samuel Sieb wrote: > On 11/28/19 9:29 AM, Patrick O'Callaghan wrote: > > Will this work without adjusting the EFI setup or grub2? If not, what > > other steps are required? Clearly /etc/fstab would also need some > > editing but I'm comfortable with that. EFI is the kicker as I've only > > just started to use it and really don't know what I'm doing. > > Since you're cloning the partitions, grub and fstab shouldn't need > adjusting because by default they use the filesystem label. However, > EFI has to identify the disk drive, so the boot entry will need to be > changed. "efibootmgr" is the tool. "efibootmgr -v" will show you the > details of the current entries. If you still have your anaconda logs > from the original install, you can find the command it used to create > the boot entry originally. You might be able to use it again directly, > or you might need to adjust it. 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). poc _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
