Red Hat Bugzilla – Bug 1310041
start job for missing device time out
Last modified: 2016-05-10 13:57:51 EDT
Created attachment 1128500 [details]
debug boot log (dmesg) as described in systemd debugging document
Description of problem:
A start job stalls for a device that I cannot find and then times out.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Unknown. I don't know what this device used to be or what happened to it. I also don't understand why there is a start job for it if it doesn't exist.
Start up is delayed 1m30s until job fails.
Job shouldn't exist/get created at boot.
I really tried to figure this out, myself, but I don't understand where this type of device-specific start job comes from or is configured. Sorry, I just don't know systemd very well.h
This turned out to be a bad encrypted swap configuration. See Bug 1304995. After I changed /etc/crypttab, this bogus device start job disappeared.