http://bugzilla.opensuse.org/show_bug.cgi?id=1096072 http://bugzilla.opensuse.org/show_bug.cgi?id=1096072#c5 --- Comment #5 from Antonio Larrosa <alarrosa@suse.com> --- Thanks for the idea. I didn't know about those generators nor that they could be masked. I tried running "systemctl daemon-reload" but that returns inmediately, so I have to reboot each time I want to test the generators. After trying to mask a few of them, having no luck, masking a few more, having no luck, and then going one by one... I noticed something strange. I masked all generators and the delay was gone. The system booted up fine. Then I removed the mask for systemd-gpt-auto-generator (or said another way, I only enabled the systemd-gpt-auto-generator) and the delay returned. I masked it again and the delay was gone. Then I removed the mask for systemd-debug-generator and the delay returned again. I masked it again and the delay was fixed once more. Then I removed the mask for systemd-cryptsetup-generator and that one didn't influence the delay. The system boots up fine if only systemd-cryptsetup-generator is enabled. I removed the mask for systemd-hibernate-resume-generator (so only systemd-cryptsetup-generator and this one are enabled) and the delay returned... Does that behaviour say anything to you? I'll continue testing one by one and try to find out the set of generators that seem to introduce the delay if any of them is enabled, but the process is slow. I guess there's no way to get a shell at that point of the boot process, is it? -- You are receiving this mail because: You are on the CC list for the bug.