On Fri, May 24, 2019 at 08:53:02AM -0000, Xavier Gnata wrote: > Because I followed an old and probably outdated documentation.
I'm afraid that documentation was probably not old, but simply broken. I've been using LUKS full-disk encryption on Ubuntu since 2007 and that has never been the way to configure cryptsetup. > Should I remove the lines in /etc/default/grub and in > /etc/initramfs-tools/conf.d/cryptroot completely? I believe that is the correct change to make. You should of course be mindful that this could make your newly-generated initramfs unbootable for unforeseen reasons, and be prepared to boot to your backup kernel with an initramfs that has not been updated for the change to /etc/initramfs-tools/conf.d/cryptroot. > My current /etc/crypttab read: CryptDisk > UUID=c9deed35-610e-4328-b8e7-079e95d43f76 none luks,retry=1,lvm=lvm-vg Is > it correct? It seems that retry=1 is also an outdated option... 'lvm=' is not a documented option in crypttab(5), I expect this to also be autodetected without needing to specify any option. But as a first step I would suggest changing only the first two files and leaving your crypttab as-is, even though it can probably be simplified. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1804314 Title: Wrong WARNING Option 'hash' missing in crypttab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1804314/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
