kernel-packages team mailing list archive

[Ruth Cheesley <1310265@xxxxxxxxxxxxxxxxxx>]

** Attachment added: "lspci-vnvn.log"
   https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1310265/+attachment/4090013/+files/lspci-vnvn.log

** Description changed:

  I think this is a duplicate of this report:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1003309
  
- I am unable to boot into newer kernels after upgrading, I get the error:
+ I am unable to boot into newer kernels after upgrading from
+ 13.10->14.04, I get the error:
  
  cryptsetup: evms_activate is not available
  
- I have whole-drive encryption set up which has been set up since 12.04
- LTS, I've done incremental upgrades since then and not had a problem.
+ I have whole-drive encryption set up which has been set up since Kubuntu
+ 12.04 LTS, I've done incremental upgrades since then and not had a
+ problem.
  
  I rebooted several times trying each kernel, currently running
  (according to uname -r) 3.11.0-14-generic which allowed me to decrypt
  the volume and log in.
  
  I am not sure how to go about filing logs, as I am unable to actually
  boot into the problematic kernel.

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

Title:
  Upgrading from 13.10 to 14.04 using GUI updater results in error:
  “cryptsetup: evms_activate is not available"

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  I think this is a duplicate of this report:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1003309

  I am unable to boot into newer kernels after upgrading from
  13.10->14.04, I get the error:

  cryptsetup: evms_activate is not available

  I have whole-drive encryption set up which has been set up since
  Kubuntu 12.04 LTS, I've done incremental upgrades since then and not
  had a problem.

  I rebooted several times trying each kernel, currently running
  (according to uname -r) 3.11.0-14-generic which allowed me to decrypt
  the volume and log in.

  I am not sure how to go about filing logs, as I am unable to actually
  boot into the problematic kernel.

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