[Bug 874774] Re: could not mount /dev/mapper/cryptswap1
Benedikt
874774 at bugs.launchpad.net
Sat Mar 24 10:26:31 UTC 2012
Hello,
I can still simulate this in Precise.
Info:
cat /etc/crypttab
# <target name> <source device> <key file> <options>
cryptswap1 /dev/sda5 /dev/urandom swap,cipher=aes-cbc-essiv:sha256
cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc nodev,noexec,nosuid 0 0
# / was on /dev/sda1 during installation
UUID=bb0ce7e2-2c02-4e90-9fc7-c61ad3f7fe22 / ext4 errors=remount-ro 0 1
# swap was on /dev/sda5 during installation
#UUID=03876e10-2abe-4871-bee1-44f1bf8b339a none swap sw 0 0
/dev/mapper/cryptswap1 none swap sw 0 0
swapon -s
Filename Type Size Used Priority
/dev/mapper/cryptswap1 partition 1046524 968 -1
free -m
total used free shared buffers cached
Mem: 1001 836 164 0 99 319
-/+ buffers/cache: 418 583
Swap: 1021 0 1021
--
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/874774
Title:
could not mount /dev/mapper/cryptswap1
Status in “cryptsetup” package in Ubuntu:
Triaged
Status in “cryptsetup” source package in Oneiric:
Triaged
Status in “cryptsetup” source package in Precise:
Triaged
Bug description:
On multiple fresh installs since beta release 2 i have been experiencing this issue:
during boot up, i receive the message "could not mount /dev/mapper/cryptswap1 M for manual S for skip"
obviously I'm expecting no message to show up at all and it should boot perfectly fine. I do however believe that i have found where the problem lies, it is in /etc/fstab
This is how the original file looked:
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc nodev,noexec,nosuid 0 0
# / was on /dev/sda7 during installation
UUID=482c5b33-9ce8-4575-b787-cddeb1e93a5e / ext4 errors=remount-ro 0 1
# swap was on /dev/sda8 during installation
#UUID=eb23dadc-8e08-4769-8fc5-0b1216b67e5b none swap sw 0 0
/dev/mapper/cryptswap1 none swap sw 0 0
i believe the problem is that the following line of:
#UUID=eb23dadc-8e08-4769-8fc5-0b1216b67e5b none swap sw 0 0
is not supposed to be commented out, i believe this happens somewhere
in install. The ghetto fix for this is simply to remove the comment on
it, but it definitely should not be happening...
i have also found a eerily similar problem from Ubuntu 9.10 Bug
#490760 which is a "duplicate" of another bug that is why i
classified this as cryptsetup, because that bug was.
Here is more information:
Description: Ubuntu 11.10
Release: 11.10
cryptsetup:
Installed: 2:1.1.3-4ubuntu2
Candidate: 2:1.1.3-4ubuntu2
Version table:
*** 2:1.1.3-4ubuntu2 0
500 http://us.archive.ubuntu.com/ubuntu/ oneiric/main amd64 Packages
100 /var/lib/dpkg/status
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/874774/+subscriptions
More information about the foundations-bugs
mailing list