I found what I think is this bug in a system installed from the Lubuntu Vivid alternate 32-bit daily iso file.
vivid-alternate-i386.iso
cryptswap is there when I reboot from the installer, but the second time I reboot it is gone.
-----
/etc/crypttab:
cryptswap1 UUID=b66610ce-376c-42cf-8d02-8983f2a40d70 /dev/urandom swap,cipher=aes-cbc-essiv:sha256
modified /etc/crypttab:
# <target name> <source device> <key file> <options>
cryptswap1 /dev/sda5 /dev/urandom swap,cipher=aes-cbc-essiv:sha256
-----
Hint to the developers: It works with the modified crypttab :-)
So it seems that the device information is wrong in /etc/crypttab. Maybe it would be better to have to PARTUUID than the device /dev/sda5.
I found what I think is this bug in a system installed from the Lubuntu Vivid alternate 32-bit daily iso file.
vivid-alternate -i386.iso
cryptswap is there when I reboot from the installer, but the second time I reboot it is gone. 376c-42cf- 8d02-8983f2a40d 70 /dev/urandom swap,cipher= aes-cbc- essiv:sha256
-----
/etc/crypttab:
cryptswap1 UUID=b66610ce-
blkid: ebeb-4c33- a023-d34191a6b2 bd" TYPE="ext4" PARTUUID= "ef7fb1de- 01" "ef7fb1de- 05"
/dev/sda1: UUID="63725e48-
/dev/sda5: PARTUUID=
modified /etc/crypttab: aes-cbc- essiv:sha256
# <target name> <source device> <key file> <options>
cryptswap1 /dev/sda5 /dev/urandom swap,cipher=
-----
Hint to the developers: It works with the modified crypttab :-)
So it seems that the device information is wrong in /etc/crypttab. Maybe it would be better to have to PARTUUID than the device /dev/sda5.