stretch and cryptsetup/luks - boot delay
hello -
i recently upgraded my laptop from wheezy through jessie into stretch.
almost everything Just Worked, which is great!
one lingering problem is that there is a 1min 30sec delay in the boot
after entering my passphrase. it reports:
cryptsetup (sda5_crypt): set up successfully
root: clean, 290656/2932736 files, 3260365/11718656 blocks
but then goes into a delay, displaying "A start job is running" for the
disk-related units. they time out, with `journalctl -alb` showing:
May 24 11:11:53 abezella-laptop systemd[1]: dev-disk-by\x2duuid-08d8147c\x2da06c\x2d4746\x2d827f\x2dd720b1f5d738.device: Job dev-disk-by\x2duuid-08d8147c\x2da06c\x2d4746\x2d827f\x2dd720b1f5d738.device/start timed out.
May 24 11:11:53 abezella-laptop systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-08d8147c\x2da06c\x2d4746\x2d827f\x2dd720b1f5d738.device.
May 24 11:11:53 abezella-laptop systemd[1]: Dependency failed for Cryptography Setup for sda5_crypt.
May 24 11:11:53 abezella-laptop systemd[1]: Dependency failed for Encrypted Volumes.
May 24 11:11:53 abezella-laptop systemd[1]: cryptsetup.target: Job cryptsetup.target/start failed with result 'dependency'.
May 24 11:11:53 abezella-laptop systemd[1]: Dependency failed for dev-mapper-sda5_crypt.device.
May 24 11:11:53 abezella-laptop systemd[1]: dev-mapper-sda5_crypt.device: Job dev-mapper-sda5_crypt.device/start failed with result 'dependency'.
May 24 11:11:53 abezella-laptop systemd[1]: systemd-cryptsetup@sda5_crypt.service: Job systemd-cryptsetup@sda5_crypt.service/start failed with result 'dependency'.
May 24 11:11:53 abezella-laptop systemd[1]: dev-disk-by\x2duuid-08d8147c\x2da06c\x2d4746\x2d827f\x2dd720b1f5d738.device: Job dev-disk-by\x2duuid-08d8147c\x2da06c\x2d4746\x2d827f\x2dd720b1f5d738.device/start failed with result 'timeout'.
May 24 11:11:53 abezella-laptop systemd[1]: dev-mapper-abezella\x2d\x2dlaptop\x2dhome.device: Job dev-mapper-abezella\x2d\x2dlaptop\x2dhome.device/start timed out.
May 24 11:11:53 abezella-laptop systemd[1]: Timed out waiting for device dev-mapper-abezella\x2d\x2dlaptop\x2dhome.device.
May 24 11:11:53 abezella-laptop systemd[1]: Dependency failed for /home.
May 24 11:11:53 abezella-laptop systemd[1]: Dependency failed for Local File Systems.
May 24 11:11:53 abezella-laptop systemd[1]: local-fs.target: Job local-fs.target/start failed with result 'dependency'.
May 24 11:11:53 abezella-laptop systemd[1]: local-fs.target: Triggering OnFailure= dependencies.
May 24 11:11:53 abezella-laptop systemd[1]: home.mount: Job home.mount/start failed with result 'dependency'.
May 24 11:11:53 abezella-laptop systemd[1]: Dependency failed for File System Check on /dev/mapper/abezella--laptop-home.
May 24 11:11:53 abezella-laptop systemd[1]: systemd-fsck@dev-mapper-abezella\x2d\x2dlaptop\x2dhome.service: Job systemd-fsck@dev-mapper-abezella\x2d\x2dlaptop\x2dhome.service/start failed with result 'dependency'.
May 24 11:11:53 abezella-laptop systemd[1]: dev-mapper-abezella\x2d\x2dlaptop\x2dhome.device: Job dev-mapper-abezella\x2d\x2dlaptop\x2dhome.device/start failed with result 'timeout'.
May 24 11:11:53 abezella-laptop systemd[1]: dev-disk-by\x2duuid-cba918f2\x2d3c25\x2d417f\x2d9da9\x2de2b1fafe4aa0.device: Job dev-disk-by\x2duuid-cba918f2\x2d3c25\x2d417f\x2d9da9\x2de2b1fafe4aa0.device/start timed out.
May 24 11:11:53 abezella-laptop systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-cba918f2\x2d3c25\x2d417f\x2d9da9\x2de2b1fafe4aa0.device.
May 24 11:11:53 abezella-laptop systemd[1]: Dependency failed for /boot.
May 24 11:11:53 abezella-laptop systemd[1]: boot.mount: Job boot.mount/start failed with result 'dependency'.
May 24 11:11:53 abezella-laptop systemd[1]: Dependency failed for File System Check on /dev/disk/by-uuid/cba918f2-3c25-417f-9da9-e2b1fafe4aa0.
May 24 11:11:53 abezella-laptop systemd[1]: systemd-fsck@dev-disk-by\x2duuid-cba918f2\x2d3c25\x2d417f\x2d9da9\x2de2b1fafe4aa0.service: Job systemd-fsck@dev-disk-by\x2duuid-cba918f2\x2d3c25\x2d417f\x2d9da9\x2de2b1fafe4aa0.service/start failed with result 'dependency'.
May 24 11:11:53 abezella-laptop systemd[1]: dev-disk-by\x2duuid-cba918f2\x2d3c25\x2d417f\x2d9da9\x2de2b1fafe4aa0.device: Job dev-disk-by\x2duuid-cba918f2\x2d3c25\x2d417f\x2d9da9\x2de2b1fafe4aa0.device/start failed with result 'timeout'.
May 24 11:11:53 abezella-laptop systemd[1]: dev-mapper-abezella\x2d\x2dlaptop\x2dswap_1.device: Job dev-mapper-abezella\x2d\x2dlaptop\x2dswap_1.device/start timed out.
May 24 11:11:53 abezella-laptop systemd[1]: Timed out waiting for device dev-mapper-abezella\x2d\x2dlaptop\x2dswap_1.device.
May 24 11:11:53 abezella-laptop systemd[1]: Dependency failed for /dev/mapper/abezella--laptop-swap_1.
May 24 11:11:53 abezella-laptop systemd[1]: Dependency failed for Swap.
May 24 11:11:53 abezella-laptop systemd[1]: swap.target: Job swap.target/start failed with result 'dependency'.
May 24 11:11:53 abezella-laptop systemd[1]: dev-mapper-abezella\x2d\x2dlaptop\x2dswap_1.swap: Job dev-mapper-abezella\x2d\x2dlaptop\x2dswap_1.swap/start failed with result 'dependency'.
May 24 11:11:53 abezella-laptop systemd[1]: dev-mapper-abezella\x2d\x2dlaptop\x2dswap_1.device: Job dev-mapper-abezella\x2d\x2dlaptop\x2dswap_1.device/start failed with result 'timeout'.
the laptop then boots to emergency mode. if i don't enter emergency
mode but instead continue everything (apparently) works properly, all
devices having become available later in the process. this was working
in wheezy, and i believe that during the upgrade process i booted into
jessie without the delay.
i tried changing the second field of /etc/crypttab to the device path
(/dev/sda5) but that just resulted in that failure having an easier to
parse name. also tried the systemd-cryptsetup-generator but that
didn't change anything obvious (and appears to have been unnecessary).
tried rm'ing /etc/udev/rules.d entries as suggested by some other
posts. no dice, 1m30s delay remains.
any thoughts / anyone else encountered this? finding a lot of similar
complaints for various distributions (and debian bug 758808), but no
presented solution has yet worked.
i'm hoping i'm missing something obvious. thanks in advance!
::::::::::::::
/etc/fstab
::::::::::::::
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# Reduce the amount of journal writes w/the "data=writeback" option.
# This means the ext4 will only journal metadata.
# Setting up and using SSD drives in Fedora Linux - FedoraForum.org
# http://forums.fedoraforum.org/showthread.php?t=277082
/dev/mapper/abezella--laptop-root / ext4 errors=remount-ro,noatime,discard 0 1
# /boot was on /dev/sda1 during installation
UUID=cba918f2-3c25-417f-9da9-e2b1fafe4aa0 /boot ext2 defaults,noatime,discard 0 2
/dev/mapper/abezella--laptop-home /home ext4 defaults,nosuid,nodev,noatime,discard,data=writeback 0 2
/dev/mapper/abezella--laptop-swap_1 none swap sw 0 0
/dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0
tmpfs /tmp tmpfs defaults,noatime,nosuid,nodev 0 0
::::::::::::::
/etc/crypttab
::::::::::::::
sda5_crypt UUID=08d8147c-a06c-4746-827f-d720b1f5d738 none luks,discard
% sudo lsblk -o name,uuid,mountpoint
NAME UUID MOUNTPOINT
sda
├─sda1 cba918f2-3c25-417f-9da9-e2b1fafe4aa0 /boot
├─sda2
└─sda5 08d8147c-a06c-4746-827f-d720b1f5d738
└─sda5_crypt wtoOt9-TlZB-cpyJ-4MsE-lPmN-jPW0-QdWcBA
├─abezella--laptop-swap_1 20ca0381-a08e-42b8-8f87-12308ff10b7b [SWAP]
├─abezella--laptop-root c8a5cd45-6192-48c0-ad74-a07bdba06db1 /
└─abezella--laptop-home 86ba9c52-bcb7-401e-a77e-03216ba541a4 /home
sr0
--
andy <andrew@diatribes.org>
Reply to: