Comment 41 for bug 874774

Revision history for this message
Steve Langasek (vorlon) wrote : Re: [Bug 874774] Re: could not mount /dev/mapper/cryptswap1

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.