[Bug 1155222] Re: Cryptsetup initramfs wants EVMS - Bug in /usr/share/initramfs-tools/scripts/local-top/cryptroot

[Steve Langasek]

On Thu, Mar 14, 2013 at 05:36:52PM -0000, Swâmi Petaramesh wrote:
> The "sometimes" is real, and I saw that this part of code suggest
> something that is called when the device "hasn't shown up yet", and I
> saw in the past these kind of scripts have trouble with devices taking a
> while to show up... Sometimes it works, sometimes not.

> In my case, either my machine boots like it always did before, or it
> stops forever on this EVMS message... Until I reboot it, and then,
> either it works , or I get the same message again...

So the crypttab in your bug report shows a single entry, for an LVM VG that
uses a keyscript.  I assume that since the cryptroot script is being run,
your root device is on this VG.  What does /usr/local/sbin/bootkeyscript do? 
Can you attach it?

Is there a reason you're not using the default decrypt method (console
prompting via plymouth)?

If the last message you see when it hangs is about evms, then the source
device must already be set up.  Otherwise, it would be followed by the
message:

  "Waiting for encrypted source device..."

The next command run is 'udev_settle'.  It's possible something's going
wrong with udev on your system; perhaps an event loop that prevents udev
from ever settling.  What version of udev do you have installed?

After that, the next steps are to check the device with 'cryptsetup isLuks',
then call your keyscript.  So there are very few opportunities for bugs in
the script itself.  Maybe you can annotate the script with additional debug
statements locally, to pinpoint exactly where the hang is happening?

-- 
Steve Langasek                   Give me a lever long enough and a Free OS
Debian Developer                   to set it on, and I can move the world.
Ubuntu Developer                                    http://www.debian.org/
slangasek at ubuntu.com                                     vorlon at debian.org

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

Title:
  Cryptsetup initramfs wants EVMS - Bug in /usr/share/initramfs-
  tools/scripts/local-top/cryptroot

Status in “cryptsetup” package in Ubuntu:
  Incomplete

Bug description:
  This bug has been reported upstream both to dm-crypt at saout.de and pkg-
  cryptsetup-devel at lists.alioth.debian.org

  I've recently upgraded one of my fully encrypted systems from Ubuntu
  12.10 to 13.04 Alpha, and was surprised to see my system sometimes
  fail to boot, complaining it cannot find evms_activate.

  I just checked and noticed a logic error in /usr/share/initramfs-
  tools/scripts/local-top/cryptroot : If the crypto source is
  unavailable (script line 205) it then tries to activate both LVM and
  EVMS (line 160), AND EXITS IN ERROR IF EVMS IS NOT AVAILABLE on
  system. It doesn't give a shit trying to guess whether EVMS is needed
  or not, it plain fails and exits.

  This really looks like a serious bug - that has started preventing my
  system from booting randomly at times... - and needs a fix, especially
  taking into consideration that EVMS is essentially and obsolete,
  abandoned system, that will thus be available on very few systems,
  with good chances that this bug will then be triggered...

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: cryptsetup 2:1.4.3-4ubuntu2
  ProcVersionSignature: Ubuntu 3.8.0-12.21-generic 3.8.2
  Uname: Linux 3.8.0-12-generic x86_64
  ApportVersion: 2.9.1-0ubuntu1
  Architecture: amd64
  Date: Thu Mar 14 17:37:34 2013
  InstallationDate: Installed on 2012-04-30 (318 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: cryptsetup
  UpgradeStatus: Upgraded to raring on 2013-03-01 (13 days ago)
  crypttab:
   # <target name>	<source device>		<key file>	<options>
   c_VG1		/dev/sda6		UUID=9a0ce396-36f6-492f-b947-3fc078d5eec7:.fnix.rootkey.bin	luks,tries=1,keyscript=/usr/local/sbin/bootkeyscript

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