Re: Getting luks dependency problems on boot
2016-09-07 11:01 GMT-03:00 Bruno Wolff III <bruno(a)wolff.to>:
On Wed, Sep 07, 2016 at 10:36:29 -0300,
Martín Marqués <martin.marques(a)gmail.com> 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?
--
Martín Marqués
select 'martin.marques' || '@' || 'gmail.com'
DBA, Programador, Administrador