[Bug 669466] Re: encrypted /tmp partition doesn't mount during boot after update to lucid

[Steve Langasek]

*** This bug is a duplicate of bug 874774 ***
    https://bugs.launchpad.net/bugs/874774

** This bug has been marked a duplicate of bug 874774
   could not mount /dev/mapper/cryptswap1

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

Title:
  encrypted /tmp partition doesn't mount during boot after update to
  lucid

Status in “mountall” package in Ubuntu:
  New

Bug description:
  After an upgrade from karmic to lucid (kubuntu) my luks-encrypted /tmp
  partition failes to mount during booting the system.

  It then gives me the option to boot it manualy and then to continue with booting. The mounting of tmp works, but unfortunatly I'm not able to decrypt my ecrytptfs-encrypted home directory for some reason.
  On the other hand, when I continue booting without mounting /tmp and then first login to a console (graphical login fails due to missing tmp-directory) and then mount tmp with sudo everything works fine.

  Here is the relevant entry of my fstab:
  /dev/mapper/tmp  /tmp  ext2  defaults  0  0

  And this is what my cryptab looks like:
  tmp     /dev/disk/by-id/ata-WDC_WD800JD-55MUA1_WD-WMAMD5727339-part6 /dev/urandom  tmp,cipher=aes-xts-plain,size=256

  I'm not sure if this bug is related to
  https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/544812 so I
  decided to report it as a new bug for now.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/669466/+subscriptions