Ok, I’m up and running on the new drive, but I had to boot into fallback mode.
I’m running systemd-boot. Is fixing this as simple as running bootctl update?
Is this drive a full install of eos or you just added it and copied your home to it?
Edit: Better check with @dalto as he is the expert on this.
Full install of EOS. It is noticeably quicker
Did you do a full install with it installed here? Shouldn’t be doing that on boot? 
Edit: Not sure what the issue would even be.
I used dd to clone my install to the new drive. I’ve unplugged the SATA cable for the old drive and the new one is only booting if I use fallback mode.
UPDATE: Re-installing the kernel seems to have sorted it out.
That’s probably because the UUID would be different for the nvme drive compared to what it was previously installed on. I was going to say reinstalling the kernel might work but didn’t want to send you on a bad path.
This is why I thought I’d need to update /etc/fstab but was told the UUID would not change. No matter though, looks like I’m good to go.
nvme drives are the way to go for sure. I also like ssd drives as a secondary.
Edit: I use the Western Digital Black and they are superb.
yea, the original plan was to put /home on the NVMe and eventually get a SATA SSD for the rest of the OS but, after perusing a few forums, I got talked out of it. I will keep my old 1T HDD for media/document storage though.
Interestingly enough, I wound up going with the Western Digital Black myself…the version with the heat sink.
Nothing wrong with the HD for storage but they are significantly slower than an SSD and the m.2 drives just eat the SSD for breakfast!
This PC boots crazy fast now and websites and games are pretty snappy as well.
dd will supply the same UUID…there may have been other problems. I have used dd for years & checked the identification on source/destination drives to verify this many times— that’s why I use it.
From Substack: " The reason the second partition has the same UUID is because dd just copies data from one file to another (dd if=/dev/sda1 of=/dev/sdb1 = cat /dev/sda1 > /dev/sdb1); dd doesn’t know what a partition is, or how to generate a UUID, so it just copied all the data as-is, including the UUID, which is stored in the filesystem superblock near the start of the partition."
This also holds true for whole disc cloning—as dd comes across each partition, it renders the data exactly as it sees it on the source.
More information on dd here: https://www.geeksforgeeks.org/dd-command-linux/
I have 2 (a 1TB & a 2TB) in my system…have worked without fail since I bought them.
I did that but it I couldn’t get it to work by copying everything over - ended up doing a clean install and copying /home onto that.
Not sure what you did, how you did it and what did not work.
If you are referring to disk cloning, some more information could be useful.
Sorry, didn’t mean to derail the discussion. This was a while ago and I don’t need help now. Just wanted to point out that a fresh install is one way to do it.