Marafon

Same, actually.

Hard pull or Atomic pull means to allow the pla inside the hotend to either cool to or heat up to ~80-100°C and then pull it out through the top. The semi melted plastic grabs clogs on its way out. Very easy and effective remedial action for small internal clogs.

Sudo blkid confirms UUIDs do match. When I boot with the new SSD after using gparted to copy the partitions from the HDD for the third time exactly how you described above it still takes forever to think about booting and then lands me on that same page I screenshotted before. e still gives a "command not found error." Also the UUIDs both match the ones in the error message, but not that directory structure. Instead of /dev/disk/by-uuid/blahblahblah they are referred to as dev/nvme0n1p2 and dev/nvme0n1p1 in gparted and blkid.

I did find an interesting line in journalctl that suggested something about boot failing due to secure boot mode.

I really really appreciate your help and you sticking it out with me. But unless anything here gives you a brain blast "Aha!" Moment I think I'm done fucking with this lol I'm just going to fresh install and call it a day.

Followed your instructions and I got really excited when the SSD actually showed the screen with the boot options but then it hangs trying to boot for a long time and hits me with this screen:

Spoiler

This feels like the closest I've gotten so far!

I am absolutely thinking of Frontline! Thanks for setting me straight!

"GRAB THOSE BANGALORES!"

Yes! This game was amazing at the time. Storming Normandy and a later mission on German u boat are both core memories for me. And I can confirm (though this was almost 10 years ago now, so it's probably worse still) graphics do not hold up today at all but I remember still liking the actual gameplay still. Might try to spin that up in an emulator sometime for shits and gigs. Thanks for the blast from the past OP.

sudo blkid shows all UUIDs are the same as the partitions they are cloned from. I'm unable to mount /dev/nvme0n1p2 (SSD root partition) and it gives a "bad superblock" error. A little bit of googling led me to attempt to use the command sudo btrfs rescue super-recover -v /dev/nvme0n1p2 but it told me "all supers are valid, no need to recover" I then run sudo dmesg and see BTRFS error (device nvme0n1pe): bad tree block start, mirror 1 want 2521222217728 have 0 BTRFS error (device nvme0n1pe): bad tree block start, mirror 2 want 2521222217728 have 0 BTRFS error (device nvme0n1pe): failed to read chunk root BTRFS error (device nvme0n1pe): open_ctree failed

I think you're right I am 99% confident I have seen the /boot/efi directory on my system before in the past.

I am using Mint as my live USB image. But now I'm thinking it might have been wiser to use an opensuse tumbleweed live image since id reckon it would be better equipped to handle btrfs.

I think I might need to clone the drive again to fix the superblock issue but I don't know if I want to do it for what would be the 4th or 5th time now. I might just bite the bullet and fresh install to SSD again and copy my /home over and set everything up again. It will be a pain but not as big as this is becoming lol

I am very appreciative of your time though! And this experience has certainly taught me more about Linux and gave me some familiarity with new commands. So thank you again!

Most recently I have used gparted to resize the root partition of my HDD (/dev/sda2) to be only a little larger than the amount of data I actually had on it. Taking it from ~7 TB to 1tb, mostly so that I wouldn't have to copy "empty" space and also so that the partition would actually fit on my 4tb SSD (/dev/nvme0n1p2) Then I created 3 partitions on my SSD that matched the file structures on the HDD (fat=nvme0n1p1, btrfs=nvme0n1p2, linux-swap=nvme0n1p3).

I then booted from a USB with clonezilla live on it and proceeded to clone partition to partition sda1>nvme0n1p1, sda2>nvme0n1p2, sda3>nvme0n1p3. The only way I could perform the clones without errors was to run in expert mode, selecting -icds (disables check for drive size), -k (can't remember exactly what this one did, something about not copying partition header or title?) after cloning all partitions I unhooked the HDD inside the case and tried to boot. Hit the same grub screen and hitting e returned error: ../../grub-core/script/function.c119:can't find command 'e'.

I think it's booting from UEFI? But I'm not sure how to actually tell. I will check for those grub configs in the morning though. Your help is greatly appreciated!

Screenshot of screen ssd boots to currently

spoiler

results of sudo btrfs subvolume list newboot:

I appreciate your help! I probably won't have time to work on it again really until tomorrow, but I feel like I'm close.

I tried that and for some reason it only had one directory in /etc and that was snapper. I unmounted and remounted without the -o subvol=/ and I checked in /etc for fstab again and this time I found it so I'm sure I just overlooked it the first time.

I was able to verify that the UUIDs were all the same but then when I attempted to boot from the SSD it went straight to what I think is the grub recovery screen? I just typed shutdown and booted back into the HDD. I guess I'm going to try and clone the drive again. If it doesn't work again I'll probably just bite the bullet and perform a fresh install on the SSD again and set everything up manually.

I have hit a bit of a snag. Quick rundown of what I have done. I attempted to use clonezilla but then I learned that it can't clone a larger partition to a smaller partition, even if it is mostly "empty" space. So I learned how to use gparted from a live USB version of Linux mint to size the partition on my hdd with all of my stuff on it to be the same size as my new SSD (8tb to 4tb) so that it could clone to it. Well clonezilla ran for a couple hours overnight and then when I went to check things in the morning I got an error attempting to mount the drive as described in step 12. I don't remember the error specifically,something about a super block, but my googling told me it was most likely an issue with the cloning process. So I decided to just follow your directions exactly and use disc destroyer for the first time. It took five-ever as in almost 5 hours to copy everything over lol but I am able to mount it as described in step 12, great joy! But then at step 13 when I type sudo nano /newboot/etc/fstab I am told that it doesn't exist. I mosey on over in the file browser and sure enough there is no file at that location. For shits and gigs I run sudo nano /etc/fstab to look at the one on the live USB version of Linux mint and it doesn't seem to be what I should be looking for either:

overlay / overlay rw 0 0 tmpfs /tmp tmpfs nosuid,nodev 0 0

I thought about saying YOLO but then I remembered this was the exact UUID stuff I was worried about when I read the thread from Google so I thought I'd ask before just trying to boot the SSD and seeing what happens.

Also I have some clarifying questions about the last few instructions. Step 15 says to remove the source HDD before booting, which I can do to test that the SSD cloned successfully but after the test I do want to be able to put the HDD back in to the computer and reformat it as extra storage space. Does that change anything about what I should do? If I want to use both drives together do the UUIDs still need to be identical? Or should they be different in that case?

Thanks again so much for your help, I feel like I'm making progress and Im accidentally learning quite a bit in the process.