I’m trying to migrate my system from a 512GB drive to a 4TB drive. I’ve includes pictures of the output of ‘lsblk -f’
and what happens at boot. The UUID looks the same as what it’s trying to mount, maybe the path or device name is different. Some guidance on modifying the boot loader would be appreciated.
Thank You!
Can you share the output of lsblk -o name,type,fstype,size,uuid
[liveuser@eos-2025.03.19 ~]$ lsblk -o name,type,fstype,size,uuid
NAME TYPE FSTYPE SIZE UUID
loop0 loop squashfs 2.6G
sda disk iso9660 57.3G 2025-03-19-11-30-07-00
├─sda1 part iso9660 2.8G 2025-03-19-11-30-07-00
└─sda2 part vfat 172M 67DA-AABF
nvme0n1 disk 3.7T
├─nvme0n1p1 part vfat 1G 6978-5ACC
├─nvme0n1p2 part ext4 3.6T 4f05b18e-4514-4e39-8deb-659106969677
└─nvme0n1p3 part swap 136.4G f7b22dc9-23e6-4685-9c22-35a44dbb4be9
Did you try booting the fallback entry?
I may have, but I don’t remember. It’s been awhile since I initially started this process. I’ll remove the live endeavorOS usb and try booting again and choose the fallback, then report back.
Hey, I got in using the 1st fallback option. Thought I had done this before. Thank You! Would I have to use a fallback if I had done a dracut repair? I had tried several things previously. How do get the fallback to be the default option?
Once you get in, run sudo dracut-rebuild
The issue is probably that the initrd doesn’t have the drivers for your new device. Rebuilding should fix that as it will now be detected.
Back in business! Automatic boot successful!
Thank You, so much!
Please mark @dalto’s post which gave you the solution as solution.
Other people with similar issue will find it that way.
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.
