[Bug 1061190] Re: could not mount /dev/mapper/cryptswap1 M for manual S for skip

[Cédric Dufour]

Hello,

On Quantal, I've been trying to get rid of this message on my system
when using LUKS (passphrase-protected) encrypted LVM partitions.

Looking at the source code of "mountall.c", it appears the "Continue to
wait [...] S to skip or M for recovery" (warning) message is triggered
by the (recurrent) "boredom" (hardcoded) 3-second timeout. When using
passphrase, there are good chances that mountall will get "bored" (thus
the message). Could it be that this 3-seconds timeout is also reached in
this (bug) case?

In the end, the partition gets mounted and the boot process continues.

I have found no "logic" in the mountall source code that allows it to detect cryptsetup-ped resources and be a little more "patient".
I was wondering whether a (fstab) "quiet" option may be useful to "silence" those "boredom" messages in mountall. But then, it might not be such a good idea to remove the "M for recovery" option in case something is really wrong with the resource. But further on, the M/S keypress will most likely not reach mountall when plymouth (or the console) is waiting for a passphrase (cf. the crypsetup/askpass script).
Maybe a "bepatient" (fstab) option would be more appropriate. If mountall gets "bored" on a mountpoint which has that option, we would discard the initial "boredom" message and change the "boredom" timeout to something bigger (and then show the "boredom" message only after that longer delay).
PS: I also have found no code matching the documented "--quiet" option of mountall.

What do you think? (I'll send a patch if you deem the proposed option(s)
acceptable)

Cédric

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

Title:
  could not mount /dev/mapper/cryptswap1 M for manual S for skip

Status in “cryptsetup” package in Ubuntu:
  Confirmed

Bug description:
  I get the message in the bug summary during the boot process. The boot
  takes quite a long time and also, the Resources tab in the Gnome
  System Monitor reports the swap is not available.

  I am on 12.04, and during installation, I selected the "encrypted
  home" option. Though it is a fresh install, I left my /home partition
  intact, and it dates back to ... I don't even know, maybe 10.04? At
  first I installed Kubuntu, but since then I have changed to Unity and
  I have uninstalled the Kubuntu desktop.

  I am aware of bug #874774, but I felt the need to open a new bug
  report, since even though the fix has supposedly already been released
  for that one, I still experience this problem.

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