Comment 26 for bug 874774

Revision history for this message
Ilya A. Potapov (ilya-a-potapov) wrote :

Hello!

I can still simulate this in Precise. I just updated and i think i still experience this bug.
During boot up, i receive the message: "could not mount /dev/mapper/cryptswap1 M for manual S for skip"

Here is some info:

# cat /etc/crypttab
# <target name> <source device> <key file> <options>
cryptswap1 /dev/sda3 /dev/urandom swap,cipher=aes-cbc-essiv:sha256,hash=ripemd160,size=256
(EOF)

I just added "hash=ripemd160,size=256", because in output of apt-get i notice, that hash and size should be specified for cryptsetup to work properly

# cat /etc/fstab
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc nodev,noexec,nosuid 0 0
# / was on /dev/sda4 during installation
UUID=2916dc57-771e-497d-a759-d6cd80343a09 / ext4 errors=remount-ro 0 1
# /storage was on /dev/sda2 during installation
UUID=4AB49887B49876E3 /storage ntfs defaults,umask=007,gid=46 0 0
# /windows was on /dev/sda1 during installation
UUID=36B0C3A1B0C36649 /windows ntfs defaults,umask=007,gid=46 0 0
# swap was on /dev/sda3 during installation
#UUID=e6f22fea-379b-44f7-a64c-c41b4ca601bc none swap sw 0 0
/dev/mapper/cryptswap1 none swap sw 0 0
(EOF)

# cryptsetup status cryptswap1
/dev/mapper/cryptswap1 is active and is in use.
  type: PLAIN
  cipher: aes-cbc-essiv:sha256
  keysize: 256 bits
  device: /dev/sda3
  offset: 0 sectors
  size: 6297480 sectors
  mode: read/write

It seems that swap is encrypted and in use... I think.

I will provide any further usefull information on this bug on request.