[Bug 1153661] Re: The disk drive for /dev/mapper/cryptswap1 is not ready yet or not present

[Sm17H]

The issue arises from using UUID to identify encrypted swap space: that
is not supported, as stated at section 2.3 of the cryptsetup FAQ
(https://code.google.com/p/cryptsetup/wiki/FrequentlyAskedQuestions#2._Setup):

"Specifying it directly by UUID does not work, unfortunately, as the
UUID is part of the swap signature and that is not visible from the
outside due to the encryption and in addition changes on each reboot
with this setup."

Just use disk IDs in /etc/crypttab and reboot,

$ more /etc/crypttab
cryptoswap	/dev/sdaX	/dev/urandom	swap,cipher=aes-cbc-essiv:sha256

Bear in ming though the disk ID may change if you multiple disk in the
system!

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to cryptsetup in Ubuntu.
https://bugs.launchpad.net/bugs/1153661

Title:
  The disk drive for /dev/mapper/cryptswap1 is not ready yet or not
  present

Status in cryptsetup:
  New
Status in “cryptsetup” package in Ubuntu:
  Triaged

Bug description:
  Related to this bug
  (https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1091792)
  mountall 2.48 is still showing most times on booting that
  /dev/mapper/cryptswap1 is not ready.

  My system was configured on installing to use ecryptfs on my home
  partition. This is why my swap partition was automatically configured
  to be encrypted with dm-crypt.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cryptsetup/+bug/1153661/+subscriptions