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"
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.
Hello!
I can still simulate this in Precise. I just updated and i think i still experience this bug. cryptswap1 M for manual S for skip"
During boot up, i receive the message: "could not mount /dev/mapper/
Here is some info:
# cat /etc/crypttab aes-cbc- essiv:sha256, hash=ripemd160, size=256
# <target name> <source device> <key file> <options>
cryptswap1 /dev/sda3 /dev/urandom swap,cipher=
(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 771e-497d- a759-d6cd80343a 09 / ext4 errors=remount-ro 0 1 9876E3 /storage ntfs defaults, umask=007, gid=46 0 0 C36649 /windows ntfs defaults, umask=007, gid=46 0 0 379b-44f7- a64c-c41b4ca601 bc none swap sw 0 0 cryptswap1 none swap sw 0 0
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc nodev,noexec,nosuid 0 0
# / was on /dev/sda4 during installation
UUID=2916dc57-
# /storage was on /dev/sda2 during installation
UUID=4AB49887B4
# /windows was on /dev/sda1 during installation
UUID=36B0C3A1B0
# swap was on /dev/sda3 during installation
#UUID=e6f22fea-
/dev/mapper/
(EOF)
# cryptsetup status cryptswap1 cryptswap1 is active and is in use. essiv:sha256
/dev/mapper/
type: PLAIN
cipher: aes-cbc-
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.