Public bug reported:
Allowing MaaS to do it's own DHCP/DNS but isolating it onto its own
network segment and having nodes with two network interfaces (one
interface connected to the network segment the Maas controllers are on
and the second interface connected to another (different) network
segmen
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
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)
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
