Bug 1310041 - start job for missing device time out
Summary: start job for missing device time out
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: systemd
Version: 23
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: systemd-maint
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-19 10:15 UTC by Paul DeStefano
Modified: 2016-05-10 17:57 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-05-10 17:57:51 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
debug boot log (dmesg) as described in systemd debugging document (253.52 KB, text/plain)
2016-02-19 10:15 UTC, Paul DeStefano
no flags Details

Description Paul DeStefano 2016-02-19 10:15:20 UTC
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):
systemd-222-14.fc23.x86_64

How reproducible:
Every boot

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.

Actual results:
Start up is delayed 1m30s until job fails.

Expected results:
Job shouldn't exist/get created at boot.

Additional info:
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

Comment 1 Paul DeStefano 2016-05-10 17:57:51 UTC
This turned out to be a bad encrypted swap configuration.  See Bug 1304995.  After I changed /etc/crypttab, this bogus device start job disappeared.


Note You need to log in before you can comment on or make changes to this bug.