On Wed, Sep 7, 2016 at 8:53 AM, Martín Marqués <martin.marques@xxxxxxxxx> wrote: > 2016-09-07 11:01 GMT-03:00 Bruno Wolff III <bruno@xxxxxxxx>: >> On Wed, Sep 07, 2016 at 10:36:29 -0300, >> Martín Marqués <martin.marques@xxxxxxxxx> wrote: >>> >>> Hi all, >>> >>> Dependency failed for Cryptography Setup for luks-..... >>> Dependency failed for Encrypted Volumes >> >> >> Those sound like systemd messages. You probably need to find out which >> dependency failed and that should be a big clueto which update broke things. > > Here's an oversite on my side: > > Warning: crypto LUKS UUID 9fe296b1-8aa9-4cd6-9868-b37e2720407b > > But looking at the /dev/mapper where the device is I see: > > /dev/mapper/luks-263bd743-5d1b-485b-9884-c3eda1a4d880 > > Looking at the /run/initramfs/rdsosreport.txt it's actually finding > the device in the which I see in /dev/mapper, which is the correct > UUID I have in /etc/fstab. > > So what is the UUID 9fe296b1-8aa9-4cd6-9868-b37e2720407b I see in the > output from dracut? # blkid | grep 9fe296b1 # sudo lsinitrd /boot/initramfs-4.7.2-200.fc24.x86_64.img | grep 9fe296b1 If the initramsfs really has any UUID in it, it's a bug. -- Chris Murphy -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://lists.fedoraproject.org/admin/lists/users@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
