Lets check to see if you have a crypt target
lsblk -o name,uuid,mountpoint
cryptsetup luksOpen <my-device>
sudo dmsetup targets
sudo apt install cryptsetup
send me an email if you can or anyone who can
maybe there is a bad sector on the drive you you run - fscki am almost certain that it's not because of cryptswap in particular, because when the error happens it doesn't find the whole ssd as well, like it's not even plugged in or something
nope, no bad sectorsmaybe there is a bad sector on the drive you you run - fsck
unmount the drive
fsck -y /dev/sdb
Just make sure and replace the /sdb with the correct drive
/etc/default/grub
cat /etc/fstab
PopOS uses systemd-boot not Grub as OP stated earlier.Please append the contents ofparticularly "GRUB_CMDLINE_LINUX" need to compare whats in the grub toCode:/etc/default/grub
to see if they are the sameCode:cat /etc/fstab
popos uses systemd-boot tho
Yep forgot - I am out of ideas thenPopOS uses systemd-boot not Grub as OP stated earlier.
maybe there is a bad sector on the drive you you run - fsck
unmount the drive
fsck -y /dev/sdb
Just make sure and replace the /sdb with the correct drive