Public bug reported: Binary package hint: cryptsetup
Ubuntu Jaunty amd64, cryptsetup 2:1.0.6-7ubuntu1, initramfs-tools 0.92bubuntu18, udev 136-4 I have an encrypted root so the initrd has to decrypt it during boot. Previously, initrds generated with initramfs-tools had a conf/conf.d/cryptroot file containing information parsed from /etc/crypttab relating to the device containing the root filesystem. This file is not being generated after the update from 2:1.0.6-6ubuntu2.1 -> 2:1.0.6-7ubuntu1. I tracked it down to the file /usr/share/initramfs-tools/hooks/cryptroot which is called by mkinitramfs/update-initramfs. The code here looks in /etc/fstab to find the root device (UUID=<uuid> in my case). It then tries to determine the relevant device node by looking at /dev/disk/by-uuid/<uuid>, which points to /dev/md-<number>. I'm guessing this used to point to /dev/mapper/<name> instead because the code ignores UUIDs which do not point to /dev/mapper/<name>. Changing /dev/disk/by-uuid/ab1bfbaf-30f7-4319-bdc0-ab45fd007b5c -> ../../dm-5 to /dev/disk/by-uuid/ab1bfbaf-30f7-4319-bdc0-ab45fd007b5c -> ../../mapper/root fixes the issue and this was not necessary before the update. I noticed udev rules have changed some in the last update. Could that be the source of the issue? ** Affects: cryptsetup (Ubuntu) Importance: Undecided Status: New ** Tags: cryptroot cryptsetup initrd -- initrd does not contain conf/conf.d/cryptroot file for encrypted root https://bugs.launchpad.net/bugs/317442 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs