Description of problem: During startup the system stops with "A startup job is running". Usually it appears to be waiting for one or more filesystems to mount, although sometimes another job hangs as well. Version-Release number of selected component (if applicable): How reproducible: This occurs most of the time. In one instance the boot actually failed due to a timeout and offered to drop to a shell; normally it just takes a long time to boot. Occasionally things go smoothly and I get a login screen in a reasonable time. Steps to Reproduce: 1. Boot the system Actual results: Boot process repeatedly hangs on "A startup job is running", stays there for long periods of time, and it takes up to several minutes to boot. Expected results: Additional info:
Hardware is a 2013 MacBook Air, configured to boot using EFI. Filesystems are encrypted ext4 in LVM volumes.
This is possibly related to Bug 1060548, which pertains to difficulties I had during installation for the same system.
This is most likely a device you configured in crypttab or fstab not showing up. Please follow http://freedesktop.org/wiki/Software/systemd/Debugging/ to figure out which device specifically is not showing up.
Ok, I got that to work. It looks like it's my swap device that didn't show up (this time at least).
Tried another boot and it looks like all devices showed up this time. Since the system sometimes boots just fine and only occasionally times out completely, I'm not surprised that things come up normal. But how is it that it times out and offers a shell but doesn't list any systemd jobs running?
Tried it again, it doesn't time out nor offer a shell, and with log-level set to debug I see it repeatedly attempting to start gdm, timing out, and then trying to restart gdm.
After several more attempts, I see the swap device failing to come up again (shown in the output from systemctl list-jobs). It obviously doesn't fail this way every time but I haven't seen any other disks or services implicated (except gdm, but I imagine gdm is failing because something else is missing).
Created attachment 866851 [details] Output from dmesg I've attached the output from dmesg after the boot timed out and dropped to a shell. At the same time I ran systemctl list-jobs and got the following: 208 swap.target start waiting 209 dev-mapper-luks\x2d9...7e\x2d45fd\x2da7b5\x2d76da7a1bd448.swap start waiting 210 dev-mapper-luks\x2d9...\x2d45fd\x2da7b5\x2d76da7a1bd448.device start running
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.