@manuel Thanks for the quick reply.
I’m sorry to proof you wrong tho. As for the UUIDs, this is my output of
lsblk -no NAME,LABEL,UUID:
├─sda1 UEFI_SYSTEM 12D7-771E
├─sda2 AntergosBoot 8c43bf91-8bcd-43ce-ac52-b24c766e0653
│ └─cryptAntergos AntergosRoot 29fdcc7f-95e1-4b89-b4d5-bb5340c904f8
└─sda4 AntergosSwap f454254e-336e-4178-8785-61de850eceea
├─nvme0n1p1 UEFI_SYSTEM 12D7-771E
├─nvme0n1p2 AntergosBoot 8c43bf91-8bcd-43ce-ac52-b24c766e0653
│ └─tmp AntergosRoot 29fdcc7f-95e1-4b89-b4d5-bb5340c904f8
└─nvme0n1p4 AntergosSwap f454254e-336e-4178-8785-61de850eceea
(cryptAntergos is the luks mapper
/dev/mapper/cryptAntergos of the running SSD and tmp is the mapper of my new one, decrypted it to show all UUIDs)
As for your note, I don’t really have anything important on the root partition anyway. It’s mainly the procedure of installing and configuring the system from the start, I try to avoid by cloning the SSD. Plus I doubt clonezilla would break my source disk while cloning it, but thanks for the well meant warning.
Yes, I indeed do not need my SWAP partition anymore. I used to with only 8GB of RAM, but I upgraded to 16GB about 2 weeks ago. Did not have time to change my configurations yet. But I would want a swap file just in case.
Yet again I don’t get the connection. I can try to boot without swap tho, and check if it makes a difference.
LABELs are a nice thing, but since I don’t normally mess with the root partition (and should not have to), I doubt they are useful in this case. Additionally as you can see they already have labels added by the Antergos Installtion. They aren’t used in my
/etc/fstab tho, because UUIDs are more precise - I guess.
My fstab on both SSDs:
UUID=a007d8e6-cc39-4549-b2e1-4f227529dcb7 / ext4 defaults,noatime,discard 0 1
UUID=8c43bf91-8bcd-43ce-ac52-b24c766e0653 /boot ext4 defaults,noatime,discard 0 0
UUID=12D7-771E /boot/efi vfat defaults,noatime 0 0
UUID=f454254e-336e-4178-8785-61de850eceea swap swap defaults 0 0
Please keep in mind that this should only be usable for the boot sequence, once I unlocked my encrypted root partition. Meaning the problem should be somewhere else. My first thoughts were something like this. But I just went in circles within the dm-crypt wiki pages.
I will need to clone the disk again anyway, because I worked on the old one now. But first I’d like to understand the problem completely.
One thing I forgot to mention is, the disks are the exact same size:
sudo fdisk -l
Disk /dev/sda: 232.9 GiB, 250059350016 bytes, 488397168 sectors
Disk /dev/nvme0n1: 232.9 GiB, 250059350016 bytes, 488397168 sectors
old: Samsung SSD 840 SATA; new: Samsung 960 EVO M.2