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

[Ruth Cheesley]

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.
---
ApportVersion: 2.12.5-0ubuntu2.2
Architecture: amd64
DistroRelease: Debian GNU/Linux 7
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=f5b87452-8dcc-489f-80e9-24c17c5a0636
InstallationDate: Installed on 2013-12-30 (111 days ago)
InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
IwConfig:
 eth0 no wireless extensions.

 lo no wireless extensions.
MachineType: ASUS All Series
MarkForUpload: True
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-14-generic.efi.signed root=/dev/mapper/kubuntu--vg-root ro quiet splash
ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7
RelatedPackageVersions:
 linux-restricted-modules-3.11.0-14-generic N/A
 linux-backports-modules-3.11.0-14-generic N/A
 linux-firmware 1.116.2
RfKill:

Tags: saucy
Uname: Linux 3.11.0-14-generic x86_64
UnreportableReason: This is not an official Debian package. Please remove any third party package and try again.
UpgradeStatus: Upgraded to saucy on 2014-04-19 (0 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 10/25/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0903
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z87-K
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0903:bd10/25/2013:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-K:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: All Series
dmi.product.version: System Version
dmi.sys.vendor: ASUS

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1310265

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Ruth Cheesley (rcheesley)]

apport information

[Ruth Cheesley (rcheesley)]

apport information

[Ruth Cheesley (rcheesley)]

apport information

[Ruth Cheesley (rcheesley)]

apport information

[Ruth Cheesley (rcheesley)]

apport information

[Ruth Cheesley (rcheesley)]

apport information

[Ruth Cheesley (rcheesley)]

apport information

[Ruth Cheesley (rcheesley)]

apport information

[Ruth Cheesley (rcheesley)]

apport information

[Ruth Cheesley (rcheesley)]

apport information

[Ruth Cheesley (rcheesley)]

apport information

[Ruth Cheesley (rcheesley)]

apport information

[Ruth Cheesley (rcheesley)]

apport information

[Ruth Cheesley (rcheesley)]

apport information

[Ruth Cheesley (rcheesley)]

apport information

[Ruth Cheesley (rcheesley)]

I have run the script however this is using the kernel that works, as I cannot boot into the kernel which is causing the problem.

[Ruth Cheesley (rcheesley)]

The versions of the kernel which do not work are as follows:

3.11.0-19-generic

3.11.0-15-generic

I am able to boot into the following kernel:

3.11.0-14-generic

[Tim Gardner (timg-tpi)]

Ruth - I've been attempting to reproduce your problem without success. How did you install 12.04 using LUKS ? There is no support in the installer for it. I've successfully installed Kubuntu 13.10 using encrypted LVM and then upgraded to 14.04.

[Ruth Cheesley (rcheesley)]

Hi Tim,

I'm not sure, pretty sure it was the LTS I installed but it could have been a newer version, I don't have the CD to hand that I used.

It would have been done (afaik) using the in-built system, I've only ever done it manually on my laptop, so that'd date it to when there was in-built encryption offered during the installation process I guess.

Ruth

[Tim Gardner (timg-tpi)]

Looks like 12.10 was the first version to offer encrypted LVM.

[Ruth Cheesley (rcheesley)]

Could have been 12.10 - is there any way I can find what the first installed version was? That might help?

Thanks,

Ruth

[Tim Gardner (timg-tpi)]

Looks like from the initial info that you installed from 13.10:

InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)

I've installed Kubuntu 12.04.4 and upgraded through Quantal to Saucy to Trusty without issue. You may have to re-install 14.04 from scratch because I'm at a loss as to what might be going wrong (but then I'm a kernel guy).