no i chrooted directly after installation, from live environment, and there was no /etc/crypttab, even after reinstalling cryptsetup, I thought it might be deprecated, and tried to boot without it - without success, then I thought, info of the encrypted lvm now goes somewhere else, but couldn't find out where - obiously.
I installed old crypttab then - which brought me a fresh crypttab and added my encrypted lvm to it.
I didn't remember, that it was only one line in it, thought it was more complex - would have created it myself if i would have remembered it.
A lot of manuals refer to this file, and I think people might get confused if this has to be created by themselves. I think it's no problem to ship this file with the cryptsetup package, even if it's just saying:
# <target name> <source device> <key file> <options>
Isn't it common to provide empty config files? I think it is.
no i chrooted directly after installation, from live environment, and there was no /etc/crypttab, even after reinstalling cryptsetup, I thought it might be deprecated, and tried to boot without it - without success, then I thought, info of the encrypted lvm now goes somewhere else, but couldn't find out where - obiously.
I installed old crypttab then - which brought me a fresh crypttab and added my encrypted lvm to it.
I didn't remember, that it was only one line in it, thought it was more complex - would have created it myself if i would have remembered it.
A lot of manuals refer to this file, and I think people might get confused if this has to be created by themselves. I think it's no problem to ship this file with the cryptsetup package, even if it's just saying:
# <target name> <source device> <key file> <options>
Isn't it common to provide empty config files? I think it is.