http://bugzilla.suse.com/show_bug.cgi?id=942940 http://bugzilla.suse.com/show_bug.cgi?id=942940#c20 --- Comment #20 from Thomas Blume <thomas.blume@suse.com> --- (In reply to Alexander Nolting from comment #19)

Created attachment 650227 [details] journal_after_updating_systemd-udev-dracut.txt

cryptsetup fails, because it fails to find the backend device (sda3): -->-- Oct 05 17:58:48 linux-gwd0 systemd[1]: dev-disk-by\x2did-ata\x2dSamsung_SSD_840_Series_S14GNEAD229172E\x2dpart3.device: Job dev-disk-by\x2did-ata\x2dSamsung_SSD_840_Series_S14GNEAD229172E\x2 dpart3.device/start timed out. Oct 05 17:58:48 linux-gwd0 systemd[1]: Timed out waiting for device dev-disk-by\x2did-ata\x2dSamsung_SSD_840_Series_S14GNEAD229172E\x2dpart3.device. -- Subject: Unit dev-disk-by\x2did-ata\x2dSamsung_SSD_840_Series_S14GNEAD229172E\x2dpart3.device has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit dev-disk-by\x2did-ata\x2dSamsung_SSD_840_Series_S14GNEAD229172E\x2dpart3.device has failed. -- -- The result is timeout. Oct 05 17:58:48 linux-gwd0 systemd[1]: Dependency failed for Cryptography Setup for cr_home. -- Subject: Unit systemd-cryptsetup@cr_home.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit systemd-cryptsetup@cr_home.service has failed. --<-- The weird thing is that the start job for the device runs only 6 seconds before: -->-- Oct 05 17:58:42 linux-gwd0 systemd[1]: dev-disk-by\x2did-ata\x2dSamsung_SSD_840_Series_S14GNEAD229172E\x2dpart3.device: Installed new job dev-disk-by\x2did-ata\x2dSamsung_SSD_840_Series_S14GNEAD229172E\x2dpart3.device/start as 129 --<-- We have a default device timeout of 90 seconds, so it shouldn't fail after only 6 seconds. I will try to reproduce the problem. Can you provide the /etc/fstab and /etc/crypttab entries for your home mount? I assume that you didn't play with the default systemd settings. If you did, please describe exactly what you have changed. -- You are receiving this mail because: You are on the CC list for the bug.