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

[Steve Langasek]

On Sat, Apr 14, 2012 at 10:45:33AM -0000, Benedikt wrote:
> Is this really fix released?

To the best of my knowledge!

> I have the same problem in Recovery Mode.

There is nothing in this bug report which is specific to recovery mode. 
You're probably encountering a different bug.

You also don't mention if you're running 12.04 or an earlier release.  The
bug in cryptsetup has only been fixed for 12.04.

> When I Press "Network" and then want that the program mounts my partitions
> it hangs.  I press than Ctrl + C.  Then I can see that friendly-recovery
> is hanging with the problem: "could not mount /dev/mapper/cryptswap1 M for
> manual S for skip" Then the program is killed and the computer starts
> normally.

It appears that friendly-recovery calls 'udevadm trigger' manually instead
of starting the 'udevtrigger' job.  As a result, the cryptdisks-enable job,
which is the catch-all that starts random-crypted swap devices, is never
started.

So yes, this is a different bug.  Please file a new bug report against
friendly-recovery; feel free to quote this message when filing.

> But what is when i start the recovery Mode because i can't start the PC
> normally.  I can not rescue my data because friendly-recovery hangs on
> mounting my swap partitions!

Friendly-recovery also gives options for you to launch an interactive shell
from which to recover the system.  You should be able to remount your
filesystem read-write by hand from the shell ('mount -orw,remount /') and
recover from there.

Ideally, you would be able to interact with mountall anyway to tell it to
skip a missing partition, just as you do during a normal boot;
friendly-recovery can probably accomplish this by further manipulating the
plymouth splash.

-- 
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:
  Fix Released
Status in “cryptsetup” source package in Oneiric:
  Triaged
Status in “cryptsetup” source package in Precise:
  Fix Released

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