[Bug 287879] Re: cryptsetup does not understand UUID= in fstab and conf.d/resume

[Steve Langasek]

On Fri, Feb 12, 2016 at 10:45:17PM -0000, Andri Möll wrote:
> Even though this seems to be fixed, I'm still seeing UUID= mountpoints
> failing in Ubuntu 14.04.03 when that mountpoint is on a LVM logical
> volume.

Use of UUID= for LVM volumes is unsupported because a UUID is not guaranteed
to be a unique identifier in the face of snapshotting.  Use the devmapper
path instead.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to cryptsetup in Ubuntu.
https://bugs.launchpad.net/bugs/287879

Title:
  cryptsetup does not understand UUID= in fstab and conf.d/resume

Status in cryptsetup package in Ubuntu:
  Fix Released
Status in cryptsetup package in Debian:
  Fix Released

Bug description:
  Binary package hint: cryptsetup

  Hello,

  When UUID= syntax is used in /etc/fstab or  /etc/initramfs-
  tools/conf.d/resume, cryptsetup is not correctly set up in initrd. The
  file conf/conf.d/cryptroot in the initrd is lacking the appropriate
  entries and booting hangs with "Waiting for root filesystem..." .

  If /dev/mapper/[name] is used instead of UUID= in either file, the
  correct entries end up in conf/conf.d/cryptroot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/287879/+subscriptions