[Bug 874774] Re: could not mount /dev/mapper/cryptswap1

[TJ]

This also affected my custom encrypted configuration. I see the prompt
twice, once for each encrypted volume. I can use the (M)anual option to
drop to the busybox shell, manually unlock the volumes with cryptsetup,
then exit the shell, after which mountall carries on successfully.

After remaining on Lucid until now I installed Oneiric into empty LVs,
one for "/" and another encrypted for "/var". In addition I added the
encrypted "/home".

/etc/crypttab has:

Oneiric_var /dev/mapper/Ubuntu-Oneiric_var_encrypted /media/USB/somefile.key luks
home /dev/mapper/Ubuntu-home /media/USB/somefile.key luks

and lvm2 and cryptsetup are installed into the new volumes and have updated the initrd.img.
 
/etc/fstab has:

proc            /proc           proc    nodev,noexec,nosuid 0       0
/dev/mapper/Ubuntu-Oneiric /               ext4    errors=remount-ro 0       1
/dev/mapper/Oneiric_var /var            ext4    defaults        0       2
/dev/mapper/Ubuntu-swap none            swap    sw              0       0
# /boot was on /dev/sda3 during installation
UUID=af296c2f-a6f5-4cdb-b74c-66310f169677 /boot           ext3    defaults        0       2
/dev/mapper/Ubuntu-usr_local /usr/local      ext3    defaults        0       2
/dev/mapper/home /home           ext3    defaults        0       2

-- 
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