Description of problem: My /etc/crypttab contains this lines: luks-root /dev/md/root none luks-home /dev/md/home none luks-swap /dev/md/swap none But the initramfs created by dracut creates the luks devices of "luks-UUID", which makes swap not work. There is a workaround to change /dev/md/swap to UUID=xxx in /etc/fstab, but dracut should respect the crypttab anyway. Version-Release number of selected component (if applicable): dracut-041-10.fc22.1.x86_64 Additional info: crypttab inside init ramdisk contains correct records: # lsinitrd /boot/initramfs-4.0.4-300.fc22.x86_64.img -f /etc/crypttab root /dev/md/root none swap /dev/md/swap none
What is your kernel command line?
I tried many different kernel command lines. You tell me, which command line to use, if I want dracut to open my /dev/md127 as /dev/mapper/luks-root and /dev/md126 as /dev/mapper/luks-swap.
hmm.. # lsinitrd /boot/initramfs-4.0.4-300.fc22.x86_64.img -f /etc/crypttab root /dev/md/root none swap /dev/md/swap none versus: My /etc/crypttab contains this lines: luks-root /dev/md/root none luks-home /dev/md/home none luks-swap /dev/md/swap none so, there is "root" versus "luks-root" ??
It is just a typo (result of trying so many ways). Originally, I had in my crypttab: root /dev/md/root none swap /dev/md/swap none home /dev/md/home none and initrd contained: root /dev/md/root none swap /dev/md/swap none (it is probably because dracut does not need home) Later I changed it to: luks-root /dev/md/root none luks-swap /dev/md/swap none luks-home /dev/md/home none and initrd contained: luks-root /dev/md/root none luks-swap /dev/md/swap none The point is, that dracut stores /etc/crypttab in initrd correctly, but it is being ignored during boot. And the question remains the same: how to make dracut use given crypttab to decrypt filesystems?
I will try to reproduce the issue the next days and debug to see what is going wrong.
Ok, I was able to boot, if I removed any "rd.luks.uuid=" options from the kernel command line, as long as /etc/crypttab in the real root and the initrd are in sync.
Also make sure /etc/mdadm.conf is correct and in sync. Adding rd.md.uuid=... options to the kernel cmdline helps also. # dracut --print-cmdline gives you a hint, how those rd.md.uuid=... options should look like. Also, I will fix dracut to better cope with the situation hopefully.
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.