Comment 5 for bug 499488

Interestingly, my latest boot attempt showed this output:

cryptsetup: lvm device name (/dev/disk/by-uuid/2010ede2-fff3-4f15-bc79-1d397a414ac6) does not begin with /dev/mapper/
Unlocking the disk /dev/disk/by-uuid/2010ede2-fff3-4f15-bc79-1d397a414ac6 (vda1_crypt)
Enter passphrase:
Key slot 0 unlocked.
File descriptor 3 left open
  Volume group "ubuntu" not found
udevd-work[185]: inotify_add_watch(6, /dev/mapper/vda1_crypt, 10) failed: No such file or directory

udevd-work[322]: open /dev/null failed: No such file or directory

mountall: Could not connect to Plymouth
fsck from util-linux-ng 2.16
fsck from util-linux-ng 2.16
udevd[352]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in /lib/udev/rules.d/56-hpmud_support.rules:10

/dev/mapper/ubuntu-root: clean, 135622/923888 files, 694797/3694592 blocks
/dev/vda5: clean, 166/124496 files, 31658/248976 blocks
init: ureadahead-other main process (370) terminated with status 4
 * vda1_crypt (running)... [ OK ] * vda1_crypt (running)...

Note the error message about the failure to find the Volume group
"ubuntu" while still being able to boot successfully. Maybe the lvm
initramfs scripts needs to use watershed somewhere?

--
Gruesse/greetings,
Reinhard Tartler, KeyID 945348A4