← Back to team overview

kernel-packages team mailing list archive

[Bug 1003309] Re: Boot fails after installing updates, error: “cryptsetup: evms_activate is not available"

 

This bug report goes back to 2012, it is now 2016 and this bug is STILL
happening in kernel 4.2.0-35??? Pleas fix this, I had this happen when
upgrading kernel in Ubuntu 14.04lts and had to load 15.10 on my external
to even use my computer, still cannot get into by internal drive. I
figured a very cumbersome workaround out for the 15.10 external but
cannot even get to that place on the internal...there I just get a
blinking cursor and it goes nowhere. This is ridiculously lame for this
to be continuing for more than 4 years....

** Changed in: linux (Ubuntu)
       Status: Expired => New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1003309

Title:
  Boot fails after installing updates, error: “cryptsetup: evms_activate
  is not available"

Status in linux package in Ubuntu:
  New

Bug description:
  I run 12.04 LTS on a virtualbox image. I use LUKS and LVM for whole
  disk encryption.

  After installing recent kernel updates, my system no longer boots. It
  says: "cryptsetup: evms_activate is not available" when it would
  normally ask for passphrase.

  If I boot the previous kernel, I do not get this error.

  This appears to be a bug in the new kernel package?

  Until this is fixed, is there any workaround that will let me boot my
  system with the new kernel?

  
  More info:
  Maybe this issue is related to this bug: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/957602 ?
  However, this is a much more recent kernel.

  This kernel works: 3.2.0-23-generic, while this one fails:
  3.2.0-24-generic

  
  I have tried doing this:
  sudo su -
  cd /boot/grub
  update-initramfs -u
  update-grub
  reboot

  This did not solve the issue.


  
  It seems that the new kernel does not include evms support, while the older kernel does.
  Is this something that has been officially removed from the Ubuntu provided kernel? If so, why? I am pretty sure this breaks a lot of Ubuntu deployments using LUKS and dmcrypt.


  My /etc/fstab is available here:
  http://p.adora.dk/P2400.html

  My /etc/crypttab is available here:
  http://p.adora.dk/P2401.html
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  AplayDevices:
   **** List of PLAYBACK Hardware Devices ****
   card 0: I82801AAICH [Intel 82801AA-ICH], device 0: Intel ICH [Intel 82801AA-ICH]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USER        PID ACCESS COMMAND
   /dev/snd/controlC0:  tdn        2056 F.... pulseaudio
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
  Card0.Amixer.info:
   Card hw:0 'I82801AAICH'/'Intel 82801AA-ICH with STAC9700,83,84 at irq 21'
     Mixer name	: 'SigmaTel STAC9700,83,84'
     Components	: 'AC97a:83847600'
     Controls      : 34
     Simple ctrls  : 24
  DistroRelease: Ubuntu 12.04
  HibernationDevice: RESUME=UUID=f1d46fd3-d40c-43e3-b4a3-74fa5f699952
  InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120424)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
  MachineType: innotek GmbH VirtualBox
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_DK:en
   TERM=xterm
   PATH=(custom, user)
   LANG=en_DK.UTF-8
   SHELL=/bin/zsh
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-23-generic root=/dev/mapper/barbera-root ro quiet splash
  ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
  RelatedPackageVersions:
   linux-restricted-modules-3.2.0-23-generic N/A
   linux-backports-modules-3.2.0-23-generic  N/A
   linux-firmware                            1.79
  RfKill:
   
  SourcePackage: linux
  Tags:  precise precise
  Uname: Linux 3.2.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin photo plugdev sambashare sudo users video
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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