Ubuntu

cryptsetup: evms_activate is not available

Reported by Matthew Carr on 2012-03-17
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
cryptsetup (Ubuntu)
Low
Unassigned

Bug Description

Fully encrypt system, with raid0 on 2 drives. Upgraded to beta 12.04 from update-manager -d, failed to boot. Verified that the kernel had correct crypted drive UUID's in conf.d by comparing to a back up of the boot partition from before the upgrade. Temporarily fixed by copying the initrd.img-3.0.0-16-generic from the backup and using that to boot instead of initrd.img-3.2.0-18-generic supplied by the upgrade. Re-installing the new kernel through synaptic package manager in hopes it would auto-generate the right settings did not fix this issue. From a previous ticket I researched prior to successfully booting (I don't know the ticket number because I was in the live-cd at the time), cryptsetup might not be the root cause, just the first error to display in the splash screen. (So this might be a dupe of a previously known issue, thought I should report since it still exits)

The above is pretty much the limit of my technical knowledge, so if you want further information please let me know what to run to get it for you.

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/957602/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
Fabio Marconi (fabiomarconi) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage . I have classified this bug as a bug in ecryptfs-utils.

When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://help.ubuntu.com/community/ReportingBugs.

affects: ubuntu → ecryptfs-utils (Ubuntu)
affects: ecryptfs-utils (Ubuntu) → cryptsetup (Ubuntu)
Steve Langasek (vorlon) wrote :

The evms message is not the root cause of any problems you're experiencing. The evms handling in cryptsetup should probably be dropped as obsolete, but since it *is* obsolete, lack of evms is not going to cause a boot failure.

Changed in cryptsetup (Ubuntu):
status: New → Triaged
importance: Undecided → Low
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers