Hi, I saw the same after converting to systemd as init: Delay until some systemd script times out.
In the hope this helps someone seeing the same issue, this are my observations: In my case the reason was that somehow the UUID of the swap device changed, so that systemd was simply waiting for the wrong device. The UUID changed when I migrated to systemd, however the very first reboot was still fast. (though I did not boot to X this time has I had to recompile the nvidia stuff) After I changed to the new UUID, the system boots as expected. Maybe this helps someone with the same isssue.. I don't know why the UUID changed in the first place. The upgrade also included a kernel update. (linux-image-amd64:amd64 3.14+57 -> 3.14+59) (timeline to back that up with information) Last reboot with sysv: Aug 14 09:55:20 mordor kernel: [ 0.000000] Initializing cgroup subsys cpuset (..) Aug 14 09:55:20 mordor kernel: [ 25.798452] Adding 16775164k swap on /dev/mapper/cryptswap. Priority:-1 extents:1 across:16775164k First reboot with systemd as init: Aug 14 11:37:36 mordor kernel: [ 0.000000] Initializing cgroup subsys cpuset (..) Aug 14 11:37:36 mordor kernel: [ 26.772168] Adding 16775164k swap on /dev/mapper/cryptswap. Priority:-1 extents:1 across:16775164k (proof that this is systemd:) Aug 14 11:37:37 mordor systemd[1]: Starting Authenticate and Authorize Users to Run Privileged Tasks... Second reboot: Aug 14 11:51:42 mordor kernel: [ 0.000000] Initializing cgroup subsys cpuset (..) Aug 14 11:51:44 mordor systemd[1]: Expecting device dev-disk-by\x2duuid-918c7c50\x2d17ed\x2d4e21\x2d9026\x2d6aedacaec283.device... Aug 14 11:53:14 mordor systemd[1]: Job dev-disk-by\x2duuid-918c7c50\x2d17ed\x2d4e21\x2d9026\x2d6aedacaec283.device/start timed out. Aug 14 11:53:14 mordor systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-918c7c50\x2d17ed\x2d4e21\x2d9026\x2d6aedacaec283.device. Aug 14 11:53:14 mordor systemd[1]: Dependency failed for /dev/disk/by-uuid/918c7c50-17ed-4e21-9026-6aedacaec283. My setup: -> LUKS crytped root sda4_crypt UUID=xxxxxxxxx-xxx-xxxx-xxxx-xxxxxxxxx9d2 none luks -> LUKS crypted swap with derived key from root device cryptswap UUID=xxxxxxxxx-xxx-xxxx-xxxx-xxxxxxxxxdc3 sda4_crypt luks,keyscript=/lib/cryptsetup/scripts/decrypt_derived,swap the relevant fstab line: UUID=xxxxxxxxx-xxx-xxxx-xxxx-xxxxxxxxx283 none swap defaults 0 0 (resume kernel-param -- however resume not yet tested after migration:) resume=/dev/mapper/cryptswap ls -la /dev/disk/by-uuid/ lrwxrwxrwx 1 root root 10 Aug 14 13:11 xxxxxxxxx-xxx-xxxx-xxxx-xxxxxxxxx1b2 -> ../../dm-1 lrwxrwxrwx 1 root root 10 Aug 14 13:11 xxxxxxxxx-xxx-xxxx-xxxx-xxxxxxxxx9d2 -> ../../sda4 lrwxrwxrwx 1 root root 10 Aug 14 13:11 xxxxxxxxx-xxx-xxxx-xxxx-xxxxxxxxx5c0 -> ../../dm-0 lrwxrwxrwx 1 root root 10 Aug 14 13:11 xxxxxxxxx-xxx-xxxx-xxxx-xxxxxxxxxdc3 -> ../../sda3 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
