On Fri, 2024-07-26 at 23:02 +0100, Patrick O'Callaghan 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. > > 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? > > poc Last night I found this guide: https://gist.github.com/Tamal/73e65bfb0e883e438310c5fe81c5de14 and followed it. This is the current state of blkid: # blkid ... /dev/nvme0n1p3: UUID="3401c3f8-b6cf-4a01-8a9c-263f2083a68a" UUID_SUB="386a65e9-b741-4cf5-808b-6889c4be244b" BLOCK_SIZE="4096" TYPE="btrfs" PARTLABEL="Fedora" PARTUUID="9d3f36f6-c887-4c58-bea7-18f2d472a8a6" /dev/nvme0n1p1: LABEL_FATBOOT="EFI" LABEL="EFI" UUID="5CAC-77AC" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="EFI" PARTUUID="e7207d2d-25fa-4f56-8fc0-5730b65a9d3e" /dev/nvme0n1p2: LABEL="Boot" UUID="cddd8454-0f83-4298-b981-f750b5510b17" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="Boot" PARTUUID="55f81e24-5567-458d-baa7-07fc5ca0955c" /dev/sdb2: UUID="6750ec14-043e-4cca-acba-5943b71a6029" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="ddc50fe5-4cd9-466c-96b2-7d07868e819a" /dev/sdb3: LABEL="fedora_localhost-live" UUID="8e1f7af4-c0bf-434e-b1c4-a9af2c810d56" UUID_SUB="67b164a9-ed56-402e-9a6d-fd84e6d6123d" BLOCK_SIZE="4096" TYPE="btrfs" PARTUUID="0bcf9f58-f7e0-4f0f-beab-c67c5e969b55" /dev/sdb1: UUID="AB68-7FA5" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="EFI System Partition" PARTUUID="8a303a03-0b91-453a-8555-f9627c261f65" ... and efibootmgr: # efibootmgr BootCurrent: 0001 Timeout: 1 seconds BootOrder: 0001,0002,0000 Boot0000* Fedora HD(1,GPT,e7207d2d-25fa-4f56-8fc0-5730b65a9d3e,0x800,0x80000)/\EFI\fedora\grubx64.efi Boot0001* Fedora HD(1,GPT,8a303a03-0b91-453a-8555-f9627c261f65,0x800,0x12c000)/\EFI\fedora\shimx64.efi0000424f Boot0002* Fedora HD(1,GPT,e7207d2d-25fa-4f56-8fc0-5730b65a9d3e,0x800,0x80000)/\EFI\fedora\shimx64.efi0000424f (I don't care about the TPM stuff so don't think I need the shim). So I now appear to be booting from the NVMe drive. I still don't understand why it doesn't appear in the BIOS list of bootable drives, but maybe it's just assumed to be there. The MSI docs are completely useless in this regard. Fingers crossed that this has now been sorted out, and thanks to all who contributed. I still need to fix the (unrelated) issue of where root is living, but small steps ... 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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
