On Fri, Jul 26, 2024 at 6:03 PM Patrick O'Callaghan <pocallaghan@xxxxxxxxx> wrote: > > I've cloned my existing SSD onto a new NVMe drive, copying EFI (vfat), > /boot (ext4) and root+/home (BTRFS with /home subvolume) partitions and > editing /etc/fstab appropriately. > > However I have a couple of questions: > > 1) I'm puzzled that the NVMe drive (a 2TB WD Black) doesn't appear as > bootable in the UEFI screen. This is a new MSI motherboard with 2 M_2 > slots (one occupied) and the BIOS does detect the presence of the > drive, just not as a boot option. Sorry, I can't provide advice on this problem. > 2) Given the above, I'm still booting using the existing SSD and the > /boot, /boot/efi and /home all appear correctly on the NVMe drive, but > the root partition still comes up on the SSD. I ran dracut with the > UUID of the appropriate root NVMe partition but it made no difference. > What am I missing here? Follow the boot chain.... ! I have never used btrfs, so I do not know how the below might need to be modified for use with btrfs ! It might be helpful to disable the SSD to avoid confusion - you may be able to do this from your computer's "BIOS". - boot off of a live CD or the "rescue" option from an install DVD - you might want to chroot to your cloned root disk to avoid device confusion - use blkid to examine the UUIDs on the disk(s) in question - use efibootmgr to examine the EFI variables - EFI needs a variable that points to the desired disk and the desired partition on that disk - the UUID from the EFI variable needs to match the PARTUUID for the EFI partition on the desired disk - the directory from the EFI var should be EFI/fedora - grub.cfg in EFI/fedora has the uuid of the /boot partition - the /boot partition has /boot/grub2/grub.cfg - /boot/grub2/grub.cfg has the uuid for the /boot partition, the uuid for the /boot/efi partition, and "kernelopts" which specify the root device - the root device *may* have /etc/kernel/cmdline, which will also have the root device - the root device will have /etc/fstab, which will have the devices to mount, specified either as devices, UUIDs, or LABELs Go through the above confirming the uuids and devices are correct. Your system *may* be bootable at this point, but you may need to do a "dracut --force" to rebuild your initramfs. If you can boot off of the initramfs, you might want to do a "dracut --force --regenerate-all" to rebuild all of them, and also remove/rebuild the "rescue" kernel. -- _______________________________________________ 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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
