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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1061190

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

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to