Comment 24 for bug 1310058

Yes, Albert, you are right. My last precise/cryptab backup says:

cryptswap1 /dev/sdaX /dev/urandom swap,cipher=aes-cbc-essiv:sha256

My problem with trusty seems to be two different bugs happening at the same time. The first, the UUID problem, that is solved with offset = 6 & mkswap, and the second, the hateful message 'The disk drive for /dev/mapper/cryptswap1 is not ready yet or not present' and the recurrent issue on some systems preventing ubuntu to mount the swap partition on some configurations. Using noauto to ignore the disk at boot an mounting it automatically using an alternative way solves it in precise & trusty. The message is so recurrent in various editions that I think ubiquity must implement some solution similar to my noauto solution when only encrypts the home user directory and the swap partition.