Hi! I follow the bug report related to the timeout expiration bug in systemd in F-18 (bug #868421), and I noticed that the addition of the initrd.target for F-19 introduces new timeout expiration problems, that come in addition to the one from the systemd bug report. More precisely, I see two new places where a timeout is triggered: - in /usr/lib/dracut/modules.d/99base/dracut-lib.sh:844, the required device units dev-mapper-vg_xxx\x2dlv_yyy_root.device created in the initramfs here have the default 90 seconds timeout, but these devices will appear only after the cryptsetup device is opened, so potentially after a longer delay. - another timeout problem is caused by dracut-initqueue.service, which may wait for the same devices in /usr/lib/dracut/hooks/initqueue/finished/devexist-*.sh, and finally abort ("Could not boot" emergency_shell), when the rd_retry default value is reached. The problem is that the lack of timeout in these two cases should be conditioned by the fact that the underlying device is a cryptsetup one.
dracut-027-10.git20130405.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/dracut-027-10.git20130405.fc19
Package dracut-027-10.git20130405.fc19: * should fix your issue, * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing dracut-027-10.git20130405.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-5009/dracut-027-10.git20130405.fc19 then log in and leave karma (feedback).
dracut-027-18.git20130409.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/dracut-027-18.git20130409.fc19
dracut-027-19.git20130410.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/dracut-027-19.git20130410.fc19
dracut-027-19.git20130410.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.