This version is no longer supported. If this is still reproducible on a
newer/supported version, please reopen.
** Changed in: linux (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
** Also affects: cryptsetup (Debian)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/663053
Title:
encrypted block devices unavailable with linux-virtual
T
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: lvm2 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/663053
Title:
encryp
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: cryptsetup (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/663053
Title:
** Package changed: linux-meta (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/663053
Title:
encrypted block devices unavailable with linux-virtual
To manage notifications
I just received the same error message:
"evms_activate is not available"
After a short time, I'm dropped to a prompt (initramfs), with the
initial error indicating the following:
"-r ALERT /dev/disk/by-uuid/ does not exist. Dropping to shell"
I just installed ubuntu-10.10-alternate-amd64.iso. P
Recently dist-upgraded my netbook to 10.10 and it started exhibiting the
same problem. Interestingly enough, both my laptop and my netbook will
occasionally boot up and present the screen properly, but statistically
it gives me the above mentioned issue (cryptsetup: evms_activate is not
available)
Ok, so I came here because of the following error:
cryptsetup: lvm device name (/dev/disk/by-uuid/...) does not begin with
/dev/mapper/
cryptsetup: evms_activate is not available
You may only see the last three characters of your uuid followed by ")
does not begin with /dev/mapper/" depending on
toobuntu, would you mind regenerating your initrd for both -generic and
-virtual to verify that the bug you are seeing is definitely between
kernel types rather than the cryptsetup package available during initrd
generation? (keep a backup of your working -generic, just in case.)
I am also having
What's still perplexing (and disturbing) me is why this works with
-generic but not with -virtual. Perhaps something to do with
upstart/udev?
Regarding lvm2, see http://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=544487:
Message #41 received at 544...@bugs.debian.org (full text, mbox):
From: Jona
The initrd's have the same cryptroot!
$ cat initrd-virtual/initrd/conf/conf.d/cryptroot
target=sda5_crypt,source=UUID=e8bd3ebc-0510-4df6-b734-826ea47050b6,key=none,rootdev,lvm=maverick-root
$ cat initrd-generic/initrd/conf/conf.d/cryptroot
target=sda5_crypt,source=UUID=e8bd3ebc-0510-4df6-b734-8
Toobuntu: different kernel versions have different initramfs files.
Check if your working and non-working have the same
conf/conf.d/cryptroot in them.
I find using UUIDs a bit too hard (or at least I'm not used to deal with
them so much), that's why I did my initial fix with /dev/sdaX so that I
wa
For me it is not a UUID issue. I checked /dev/disk/by-uuid and cross
checked that with /etc/crypttab and also unpacked the initrd and checked
conf/conf.d/cryptroot
It was the same UUID in all cases. I don't have linux-virtual installed
like toobuntu does. My case is a system that has whole disk
TuxFan: If I wait log enough, I get also "-r ALERT! /dev/disk/by-uuid/[id] does
not exist. Dropping to a shell!"
The timeout is four minutes, IIRC.
I'm glad you solved your problem. I suppose it is possible that the
affected package is initramfs-tools, but it seems like it's linux-
virtual to me.
That was really the reason, wrong UUID and therefore cryptsetup failed
since it didn't find the correct partition. The first visible error
message "cryptsetup: evms_activate is not available" was kinda
misleading.
So toobuntu and Eric, check that you have correct UUID.
You can check and fix it by
Ehm... Actually my "bug" seems to be a copy&paste mistake made by myself
in crypttab. I didn't remember to change the UUID to match this laptop
when I copied it from a previous install.
--
encrypted block devices unavailable with linux-virtual
https://bugs.launchpad.net/bugs/663053
You received t
I'm getting the "cryptsetup: evms_activate is not available" on boot
too, but I don't think this has anything to do with linux-virtual, since
I don't use it. I have just installed 4 laptops without problems using
the 10.10beta image (i386) in last two weeks, and now with the fifth I
used the final
Set to confirmed per Eric Frost's comments.
** Changed in: linux-meta (Ubuntu)
Status: New => Confirmed
** Changed in: cryptsetup (Ubuntu)
Status: New => Confirmed
** Changed in: cryptsetup (Ubuntu)
Status: Confirmed => New
--
encrypted block devices unavailable with linux
I can confirm this is a problem. My system was installed with the
alternate Gutsy installer with whole disk encryption. I've dist-
upgraded all the way to Lucid with no problem and after doing an upgrade
to Maverick I receive the cyptsetup: evms_activate is not available
error message.
--
encry
** Also affects: cryptsetup (Ubuntu)
Importance: Undecided
Status: New
--
encrypted block devices unavailable with linux-virtual
https://bugs.launchpad.net/bugs/663053
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-
$ cat /etc/crypttab
vg--root-lv--root_crypt UUID=9bdcff58-de6d-40e4-8f3e-d214da46ddf2 none luks
$ cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid -o value -s UUID' to print the universally unique identifier
# for a device; this may be used with UUID= as a more robust
21 matches
Mail list logo
