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 how many characters fit on your screen.
But it turns out, this error is presented for any number of issues resulting in the crypted volume not being available. In my case, it was that modprobe ahci was producing an Oops. Subsequently, scripts/init-premount/mdadm and scripts/init-premount/lvm2 failed, leaving no crypted volume to identify by UUID. To make sure the disks you are expecting are there, wait for the timeout and:
ls -l /dev/disk/by-*
Also, take a look at /tmp/mountroot-fail-hooks.d/ for clues.
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 how many characters fit on your screen.
But it turns out, this error is presented for any number of issues resulting in the crypted volume not being available. In my case, it was that modprobe ahci was producing an Oops. Subsequently, scripts/ init-premount/ mdadm and scripts/ init-premount/ lvm2 failed, leaving no crypted volume to identify by UUID. To make sure the disks you are expecting are there, wait for the timeout and:
ls -l /dev/disk/by-*
Also, take a look at /tmp/mountroot- fail-hooks. d/ for clues.
Good luck to all who stumble here.