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

[DiagonalArg]

I am having the same problem as bug #1003309, though in my case I am not running in a virtual machine. Ubuntu 12.04 with lvm on top of an encrypted mirrored system. After running an update, which updated the kernel from 3.2.0-60 to -64, on reboot I was met with: “cryptsetup: evms_activate is not available". Booting with the previous kernel works fine. I am including my apt logs, here. Let me know if I should add anything else.

Tyan-S3970:~$ lsb_release -a
LSB Version: core-2.0-amd64:core-2.0-noarch:core-3.0-amd64:core-3.0-noarch:core-3.1-amd64:core-3.1-noarch:core-3.2-amd64:core-3.2-noarch:core-4.0-amd64:core-4.0-noarch
Distributor ID: Ubuntu
Description: Ubuntu 12.04.4 LTS
Release: 12.04
Codename: precise

Tyan-S3970:~$ uname -a
Linux Tyan-S3970 3.2.0-60-generic #91-Ubuntu SMP Wed Feb 19 03:54:44 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: dev 2733 F.... pulseaudio
 /dev/snd/controlC1: dev 2733 F.... pulseaudio
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
Card0.Amixer.info:
 Card hw:0 'NVidia'/'HDA NVidia at 0xfd77c000 irq 17'
   Mixer name : 'Nvidia GPU 0b HDMI/DP'
   Components : 'HDA:10de000b,10de0101,00100200'
   Controls : 24
   Simple ctrls : 4
Card1.Amixer.info:
 Card hw:1 'Audigy'/'SB Audigy 1 [SB0092] (rev.3, serial:0x531102) at 0xd480, irq 30'
   Mixer name : 'TriTech TR28602'
   Components : 'AC97a:54524123'
   Controls : 194
   Simple ctrls : 30
DistroRelease: Ubuntu 12.04
HibernationDevice: RESUME=UUID=bdbecead-fce1-4f50-ba0e-e523c0762ed1
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110426)
IwConfig:
 lo no wireless extensions.

 eth1 no wireless extensions.

 eth0 no wireless extensions.
MachineType: empty empty
MarkForUpload: True
NonfreeKernelModules: nvidia
Package: linux (not installed)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-60-generic root=/username/mapper/tyan--s3970-root ro quiet splash
ProcVersionSignature: Ubuntu 3.2.0-60.91-generic 3.2.55
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-60-generic N/A
 linux-backports-modules-3.2.0-60-generic N/A
 linux-firmware 1.79.15
RfKill:

StagingDrivers: zram
Tags: precise running-unity staging
Uname: Linux 3.2.0-60-generic x86_64
UpgradeStatus: Upgraded to precise on 2012-06-17 (744 days ago)
UserGroups: adm admin apt-mirror cdrom dialout kismet lpadmin plugdev sambashare src vboxusers
WifiSyslog:

dmi.bios.date: 10/25/2007
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 080011
dmi.board.asset.tag: empty
dmi.board.name: S3970
dmi.board.vendor: TYAN Computer Corporation
dmi.board.version: empty
dmi.chassis.asset.tag: empty
dmi.chassis.type: 3
dmi.chassis.vendor: empty
dmi.chassis.version: empty
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080011:bd10/25/2007:svnempty:pnempty:pvrempty:rvnTYANComputerCorporation:rnS3970:rvrempty:cvnempty:ct3:cvrempty:
dmi.product.name: empty
dmi.product.version: empty
dmi.sys.vendor: empty

[DiagonalArg (diagonalarg)]

apt's history log.

[DiagonalArg (diagonalarg)]

apt's terminal log

[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 1336659

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.

[DiagonalArg (diagonalarg)]

I am running apport-collect, but this will be on the working kernel.

[DiagonalArg (diagonalarg)]

apport information

[DiagonalArg (diagonalarg)]

apport information

[DiagonalArg (diagonalarg)]

apport information

[DiagonalArg (diagonalarg)]

apport information

[DiagonalArg (diagonalarg)]

apport information

[DiagonalArg (diagonalarg)]

apport information

[DiagonalArg (diagonalarg)]

apport information

[DiagonalArg (diagonalarg)]

apport information

[DiagonalArg (diagonalarg)]

apport information

[DiagonalArg (diagonalarg)]

apport information

[DiagonalArg (diagonalarg)]

apport information

[DiagonalArg (diagonalarg)]

apport information

[DiagonalArg (diagonalarg)]

apport information

[DiagonalArg (diagonalarg)]

apport information

[DiagonalArg (diagonalarg)]

apport information

[DiagonalArg (diagonalarg)]

apport information

[DiagonalArg (diagonalarg)]

apport information

[DiagonalArg (diagonalarg)]

apport information

[DiagonalArg (diagonalarg)]

apport information

[DiagonalArg (diagonalarg)]

apport information

[DiagonalArg (diagonalarg)]

apport information

[DiagonalArg (diagonalarg)]

apport information

[DiagonalArg (diagonalarg)]

apport information

[Andy Whitcroft (apw)]

The specific error message is emitted when the source partition (ie the container for the encrypted data) is not found. I assum as well as that error you get dropped to a busy box prompt? If so could you check the source /dev/disk/by-*/* links if they are there, and if they have changed from what you seen when booted in the older kernel. Please post the info here.

[DiagonalArg (diagonalarg)]

@Andy - I do not get dropped into buysbox. I end up sitting at a purpleish screen saying "Ubuntu" with the 4-dots cycling left to right and a white font saying, “cryptsetup: evms_activate is not available". In other words, it looks very much like a proper decrypt-prompt, but with the wrong text.

Alt-F1 does drop me into busybox. I am also able to drop myself into busybox during the boot with the working kernel. Comparing the two:

In the non-working case, there are no "disks/by-label" or "disks/by-uuid" directories. The "disks/by-path" directory is missing three of what should be seven entries:

pci-0000:02:06.0-sas-0x500e81000011bd5-lun-0
pci-0000:02:06.0-sas-0x500e81000011bd5-lun-0-part1
pci-0000:02:06.0-sas-0x500e81000011bd5-lun-0-part2

The "disks/by-id" directory is missing all the "md-name" and "md-uuid" entries and is missing half of the "ata-" "scsi-" and "wwn-" entries.

I am guessing that I am missing one of my disks on the non-working kernel. The system has two Western Digital 1TB disks (in a RAID), each on a different controller. One is on the main controller on the board, and the other is on a PCI-X based (SATA/SAS) controller. I am looking at what is missing under "disks/by-path" and, because of the "sas" there, wondering if that second controller is for some reason not being seen with the new kernel?

Can you help me with next steps?

Thanks/

[DiagonalArg (diagonalarg)]

Yes, moving the drive that was on the PCI-X controller to the main board solved the problem. Does this mean that a driver disappeared between the -60 and -64 kernels? Or is it that somehow the driver is just not available on boot?

Any thoughts on how to correct this?

[DiagonalArg (diagonalarg)]

Ok, on upgrading to 3.2.0-67, the terminal reports:

W: Possible missing firmware /lib/firmware/aic94xx-seq.fw for module aic94xx

I believe this should be the problem.

(If anyone has a comment about the fix, I'd appreciate it.)

[Tim Gardner (timg-tpi)]

DiagonalArg - if you are willing we can do a bisect between Ubuntu-3.2.0-60.91 and Ubuntu-3.2.0-64.97 in order to isolate the offending commit (of which there are 378). I suspect a stable update has caused this problem.

[DiagonalArg (diagonalarg)]

@Tim - Not sure what's involved, but you lead the way and I'll do my best! :)