To recap: I'm booting from an NVMe drive, and both /boot and/boot/efi are successfully mounted there. I'm using BTRFS for root+/home, and have copied them from an existing SDD drive, which is still physically present. The system now boots from the NVMe drive, and /home is also there, *but* root is still being mounted from the SDD. I've run "dracut --fstab --force" (which supposedly should generate an initramd with root on the NVMe) and "grub2-mkconfig; grub2-install" but it makes no difference. The fstab does have the correct root line pointing to the NVMe, but it appears to be ignored. The loader entry is still pointing to the SSD: # cat /boot/loader/entries/63f58eeb1e8640c79ad45bdc9261a2bb-6.9.11-200.fc40.x86_64.conf title Fedora Linux (6.9.11-200.fc40.x86_64) 40 (KDE Plasma) version 6.9.11-200.fc40.x86_64 linux /vmlinuz-6.9.11-200.fc40.x86_64 initrd /initramfs-6.9.11-200.fc40.x86_64.img options root=UUID=8e1f7af4-c0bf-434e-b1c4-a9af2c810d56 ro rootflags=subvol=root modprobe.blacklist=i915 rd.blacklist=i915 vconsole.font=latarcyrheb-sun16 rhgb quiet audit=0 resume=UUID=8e1f7af4-c0bf-434e-b1c4-a9af2c810d56 resume_offset=413818937 grub_users $grub_users grub_arg --unrestricted grub_class fedora That UUID is for /dev/sdb3, not for /dev/nvme0n1p3 as desired. (the resume stuff is for hibernation and I'll eventually change it, but shouldn't affect root). Not sure what to do other than manually editing the loader entry. 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
