How to painlessly clone a Linux SSD to another SSD?

Question

linux

Good evening, forum users.
A problem has arisen - I can not clone my home SSD (WD 120Gib) to another SSD (Intel 12 8 Gib) for work.
Note - on the second disk, where the cloning takes place, there is even more space.
The donor has 118 gigs of /dev/sda1 and 2 gigs of swap.
On the recipient - stupidly empty unallocated space 128 gigs.
I clone like nothing ever happened:

sudo fdisk /dev/sdb
>d (удаляю раздел)
>w (пишу)
sudo ddrescue -f /dev/sda /dev/sdb

Everything is copied quickly in 10 minutes.
And ..
Nothing is loaded, climbs out (initramfs).

I execute fsck /dev/sda1 in it on his own advice and everything is OK:

And the system boots perfectly from the second disk, like the first one, only faster.
The problem fell out here:
I’m booting from the first home SSD to run GParted, and delete the swap on the second, larger working disk, which I didn’t give up at work, because the RAM at the workplace is dozupy, and the swap is useless.
Great - I delete the swap, I resize the /dev/sdb1 partition all the way. I press "apply".
Job done, no errors in general.
Now I’m booting from a brand new working Intela - and then this pops up:

Then Raise network interfaces is hammered for a minute and a half, then again 25:

But in the end the system boots normally. But after the reboot, this war begins again.
I loaded from a home SSD, and did
sudo fsck /dev/sdb1
. To which fsck answered me that everything was OK. Fine.
Faced such a problem for the first time. Google - they write that fsck will help, but how will it help if he does not see an error - everything is OK for him.
Help!

Answer 1

Now I'm booting from a brand new working Intela - and then this comes out:
"This" has come out before, it's just less noticeable, it has nothing to do with disks.
You most likely have a swap left in /etc/fstab and it is trying to connect it, remove the swap in fstab and rejoice. And Raise network interfaces - some network interface is trying to rise but cannot, here telepaths are on vacation, look for yourself who is trying to climb where

Answer 2

Alternatively, use clonezilla

Answer 3

As I understand it, the uuid of the old disk is copied to fstab, it would be necessary to correct it for the uuid of the new disk. Well, swap in the system should be disabled before deleting.

Answer 4

Done wrong. It was necessary to delete the swap under the system with which you booted, and then delete the swap partition in it. Otherwise, this section will remain written somewhere in /etc/fstab or somewhere else in cron jobs or in systemd (yes, there is such a thing somewhere, I myself came across such a problem).
I think the details and solutions here will be prompted by more experienced ones. And now - I would clone again to get a working system again, and score on these 2 gigs - the system will not use them anyway if the memory is normal.