I had the same problem when using an encrypted swap partition. Neither the general Swap FAQ, Puny Geek's solution to the "cryptswap1 is not ready yet or not present" message nor Braiam's answer to this question solved the problem for me - sometimes the swap was available, sometimes it wasn't. After many reboots and some poking around, I think I have found the underlying reason:
The path to the swap partition like /dev/sda3
is sometimes different, e.g. /dev/sdb3
. Since the file /etc/crypttab
by default seems to identify the swap partition through this path, sometimes it would find it (if that partition happens to get the same path at boot) or not (if the partition gets a different path assigned at boot).
Seems like I wasn't the only one with that problem becasue as described here, a better solution would be to bind the swap partition through it's drive ID instead of its /dev/sd*
path. This can be found by running
ls -l /dev/disk/by-id/
which lists the disk IDs for all partitions including the swap, which in my case was
ata-TOSHIBA_MQ01UBD100_73JATD5GT-part3 -> ../../sdb3
Double check in a program like Disk Utility that the -> ../../sdb*
part of this line is indeed the partition you intend to use for swapping, as this (as I said before) can sometimes change names. As always, keep this in mind:
Caution: fiddling with cryptsetup and disk devices is dangerous for
data and OS. I personally made a full backup on a separate disk and
then umplugged it to be sure it wouldn’t be involved in any mishap.
Then edit your /etc/crypttab
file by using the ID link instead of the "raw" path, in my case this line is
cryptswap1 /dev/disk/by-id/ata-TOSHIBA_MQ01UBD100_73JATD5GT-part3 /dev/urandom swap,cipher=aes-cbc-essiv:sha256
I think this method should be the default for new installations, as one apparently can never be sure of the /dev/sd*
paths... which I find somewhat worrying as I have the feeling that there are way more scripts and software out there which still rely on these paths (instead of IDs, labels or UUIDs) to stay the same across reboots.
TODO:
I haven't checked if resuming out of hibernation still works with this setup, as this seems to rely on a UUID (which my swap partition didn't have), as stated on this page: https://altinukshini.wordpress.com/2012/10/15/devmappercryptswap1-is-not-ready-yet-or-not-present/
Update:
Hibernation seems to work fine so far. Hope this solves these problems for others as well!
Best Answer
The link necordian provided has steps that do resolve this problem (I tested on a system with RAID and encrypted home directory/swap) except 1 step is missing you need to reboot before swap becomes available. Here is what I did to get my encrypted swap partition working.
Need UUID and Device name for the swap partition to fix this on RAID system with encrypted home directory/swap:
Find Device ID using "Disks" utility:
Click the ubuntu logo in the unity toolbar and then type Disks to open disk utility.
Select the SWAP partition and the device name should be listed below.
(usually /dev/dm-# for RAID or /dev/sda# for non RAID)
On my PC with RAID it was /dev/dm-6.
Get UUID from crypttab:
My /etc/crypttab:
Then run the following with your swap UUID and device name:
Add the following text ,1024 to the swap line in /etc/crypttab directly after swap,cipher=aes-cbc-essiv:sha256 do not leave any spaces.
/etc/crypttab should now look similar to this:
Run the following command:
Reboot and your swap should now work (well it worked for me).
Try rebooting a few times to make sure it's all good.