Cannot find where to remove a boot entry

I had installed this on a 256GB disk encrypted. I cloned to a 510GB disk, removed the swap partition so that I could extend, don’t really care about hibernation so I removed all entries from /etc/mkinitcpio.conf, /etc/default/grub /etc/fstab ran mkinitcpio -p linux, ran grub-mkconfig and update-grub on restart I still get a timeout waiting for: /dev/disk/by-uuid/85d6682f-63b1-4423-b224-328dadb1f612

I assume this is the swap partition that doesn’t exist anymore but I cannot find where to remove this, it’s not in any cmdline for mkinitcpio or grub that I can tell.

I might be way off, but it sounds like the system is trying to mount your old 256GB drive using the UUID. Did you update fstab to reflect the change in disk?

Also, welcome to the community :beers:

Thanks!
And yes I did, I have /dev/mapper/luks-XXXX which boots and my EFI UUID which also boots. Then I have tmpfs at /tmp

Nothing else is present.

Perhaps you could run systemctl --type swap to see if there is any “leftover” .unit left trying to activate the now non-existent swap partition. If there is you could try masking it.

Zero units.

Check the output of:

sudo blkid

#and:

cat /etc/fstab

Do all the UUID’s match?

Yes. Is there like a grub but for luks? I’m thinking luks is trying to decrypt it.

EDIT> Yes it’s /etc/crypttab that is what is messing it up.

cat log | grep 85d6    

Nov 11 08:26:42 latitude systemd[1]: dev-disk-by\x2duuid-85d6682f\x2d63b1\x2d4423\x2db224\x2d328dadb1f612.device: Job dev-disk-by\x2duuid-85d6682f\x2d63b1\x2d4423\x2db224\x2d328dadb1f612.device/start timed out.
Nov 11 08:26:42 latitude systemd[1]: Timed out waiting for device /dev/disk/by-uuid/85d6682f-63b1-4423-b224-328dadb1f612.
░░ Subject: A start job for unit dev-disk-by\x2duuid-85d6682f\x2d63b1\x2d4423\x2db224\x2d328dadb1f612.device has failed
░░ A start job for unit dev-disk-by\x2duuid-85d6682f\x2d63b1\x2d4423\x2db224\x2d328dadb1f612.device has finished with a failure.
Nov 11 08:26:42 latitude systemd[1]: Dependency failed for Cryptography Setup for luks-85d6682f-63b1-4423-b224-328dadb1f612.
░░ Subject: A start job for unit systemd-cryptsetup@luks\x2d85d6682f\x2d63b1\x2d4423\x2db224\x2d328dadb1f612.service has failed
░░ A start job for unit systemd-cryptsetup@luks\x2d85d6682f\x2d63b1\x2d4423\x2db224\x2d328dadb1f612.service has finished with a failure.
Nov 11 08:26:42 latitude systemd[1]: systemd-cryptsetup@luks\x2d85d6682f\x2d63b1\x2d4423\x2db224\x2d328dadb1f612.service: Job systemd-cryptsetup@luks\x2d85d6682f\x2d63b1\x2d4423\x2db224\x2d328dadb1f612.service/start failed with result 'dependency'.
Nov 11 08:26:42 latitude systemd[1]: dev-disk-by\x2duuid-85d6682f\x2d63b1\x2d4423\x2db224\x2d328dadb1f612.device: Job dev-disk-by\x2duuid-85d6682f\x2d63b1\x2d4423\x2db224\x2d328dadb1f612.device/start failed with result 'timeout'.
Nov 11 08:26:42 latitude systemd[1]: Reached target Block Device Preparation for /dev/mapper/luks-85d6682f-63b1-4423-b224-328dadb1f612.
░░ Subject: A start job for unit blockdev@dev-mapper-luks\x2d85d6682f\x2d63b1\x2d4423\x2db224\x2d328dadb1f612.target has finished successfully
░░ A start job for unit blockdev@dev-mapper-luks\x2d85d6682f\x2d63b1\x2d4423\x2db224\x2d328dadb1f612.target has finished successfully.
Nov 11 08:26:42 latitude systemd[1]: Stopped target Block Device Preparation for /dev/mapper/luks-85d6682f-63b1-4423-b224-328dadb1f612.
░░ Subject: A stop job for unit blockdev@dev-mapper-luks\x2d85d6682f\x2d63b1\x2d4423\x2db224\x2d328dadb1f612.target has finished
░░ A stop job for unit blockdev@dev-mapper-luks\x2d85d6682f\x2d63b1\x2d4423\x2db224\x2d328dadb1f612.target has finished.