I have system, where rootfs created on top of lvm on top of LUKS on top of MBR partition. Using =sys-kernel/dracut-023-r4 on boot I see password asking dialog (no other kernel options needed, only rootfs uuid needed. dracut activate LUKS, LVM, MD automatically), enter password, dracut automatically activate LVM volumes and mount rootfs. System boots. On sys-kernel/dracut-024-r4 I don't see password dialog. Dracut "thinking" near 10 seconds, than have timeout and put me inside debug sh (I recommend you to type "bash" and use it). In sh I can manually do cryptsetup luksOpen, detect lvm, mount rootfs. I think problem is inside dracut scripts. Please, while problem is not fixed, add red colored print to end of =sys-kernel/dracut-024-r4 install, than it can't boot from LUKS partitions, to boot from LUKS use =sys-kernel/dracut-023-r4. Reproduced on other systems. [I] sys-kernel/dracut Available versions: (~)014-r3^t (~)018-r3^t (~)019-r6^t (~)022-r6^t (~)023-r4^t [m](~)024-r4^t {debug device-mapper net optimization selinux DRACUT_MODULES="biosdevname bootchart btrfs caps cifs crypt crypt-gpg crypt-loop dmraid dmsquash-live gensplash iscsi livenet lvm mdraid multipath nbd nfs plymouth ssh-client syslog systemd"} Installed versions: 023-r4^t(03:32:33 24.01.2013)(debug device-mapper net optimization -selinux DRACUT_MODULES="bootchart caps crypt crypt-gpg crypt-loop dmraid gensplash lvm mdraid ssh-client syslog -biosdevname -btrfs -cifs -dmsquash-live -iscsi -livenet -multipath -nbd -nfs -plymouth -systemd") Homepage: http://dracut.wiki.kernel.org Description: Generic initramfs generation tool Reproducible: Always Steps to Reproduce: 1. Have system on LUKS. 2. Boot using =sys-kernel/dracut-023-r4. All ok. 3. Boot using =sys-kernel/dracut-024-r4. Can't boot, no password dialog.
Probably this is related to "rd.auto" command line option. Please show the output of command `cat /proc/cmdline` and read this article: http://article.gmane.org/gmane.linux.kernel.initramfs/2963 Amadeusz, maybe ewarn is needed for this?
renesanso, could you confirm that rd.auto solves the problem for you?
Alexander, I have added warning message. + 27 Jan 2013; Amadeusz Żołnowski <aidecoe@gentoo.org> dracut-024-r4.ebuild: + Warn in postinst log if rd.auto option is not set. Rels bug #453836. +
Will test tomorrow.
Sorry for long delay. Yes, it works with rd.auto=1 . Fidex. But 3 questions: 1. Why you don't want to enable rd.auto=1 by default, as in older realises? 2. I have many hardware, connected to my computer, and, when I boot up, it take near 7-10 seconds for dracut to display dmesg output (virtual terminal driver too slow). Can I speed up terminal (as on booted system) or hide this output (but have asked for password)?
(In reply to comment #5) > Sorry for long delay. Yes, it works with rd.auto=1 . Fidex. > > But 3 questions: > 1. Why you don't want to enable rd.auto=1 by default, as in older realises? IMHO initramfs should activate only a minimal set of devices which is critical to boot (/, /usr), and there are options for this: rd.luks.uuid, rd.md.uuid, rd.lvm.lv, etc.. rd.auto is for lazy. :)
Alexander, thanks for finding out the solution for the problem. Closing as INVALID, because it is not a bug, actually.
