I experienced this with Linux Mint 17 (based on 14.04) and searched for a solution without success.

I did a little investigation as you had above and it showed that while an entry existed in crypttab, that UUID didn't actually exist when viewing the blkid output. So, I issued a sudo mkswap /dev/mapper/mint--vg-swap_1 and copied the newly generated UUID into my crypttab file's cryptswap1 entry and rebooted. My swap problem is solved!

Your entry for mkswap will be specific to your distro and according to the information above should be /dev/mapper/ubuntu--vg-swap_1. YMMV.


I had the same issue and I succeed to solved it with the existed comments, thanks guys :). Here the following steps I followed, my home is encrypted and I have a dedicated swap partition.

Log on via CLI with the root account and format swap partition

sudo mkswap /dev/sdaX

Check the swap partition UUID

sudo blkid /dev/sdaX

Add the following line in the /etc/fstab

UUID=XXXXXXXXXX none swap sw 0 0

Note! I disable the line /dev/mapper/cryptswap1 none swap sw 0 0 but I assume my swap should not be encrypted...

If someone know how to do the same with an encrypted swap, I will appreciate :).


Do you really need swap? How much ram do you have? Swap can unnecessarily shorten the lives of SSD systems with plenty of ram...

It looks to me like somehow your swap partition didn't get created during setup although you do have a uuid for it. I'm not really sure how that happened...I guess it depends on a lot of factors. The unfortunate recommendation I have for you is to go without a swap partition if you have at least 4 gb of ram or simply reinstall from the start.

The guide I like most, although it takes a lot more manual work is here.

Hope that helps...