Bug 702985 - Boot delay Job dev-disk-by\x2duuid-... timing out
Summary: Boot delay Job dev-disk-by\x2duuid-... timing out
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: systemd
Version: 15
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Lennart Poettering
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-08 20:39 UTC by Mark van Rossum
Modified: 2011-05-11 14:50 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-05-11 14:25:56 UTC
Type: ---

Attachments (Terms of Use)
output of udevadm info --query=all --name=/dev/sda3 (2.83 KB, text/plain)
2011-05-08 20:39 UTC, Mark van Rossum 		no flags Details
grub config (1.66 KB, application/octet-stream)
2011-05-08 20:42 UTC, Mark van Rossum 		no flags Details
fstab (1012 bytes, text/plain)
2011-05-08 20:43 UTC, Mark van Rossum 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Mark van Rossum 2011-05-08 20:39:29 UTC 
Created attachment 497679 [details]
output of udevadm info --query=all --name=/dev/sda3

Description of problem:

On a fully updated F15 system (with updates-testing) I recently started to see long delays in booting.
dmesg ouput:

 60.169130] udev[459]: renamed network interface wlan0 to wlan1
[  234.161067] systemd[1]: Job dev-disk-by\x2duuid-26ad1e84\x2d5f11\x2d4fa5\x2dad13\x2d18cff828b570.device/start timed out.
[  234.162487] systemd[1]: Job cryptsetup.target/start failed with result 'dependency'.
[  234.163834] systemd[1]: Job dev-mapper-luks\x2d26ad1e84\x2d5f11\x2d4fa5\x2dad13\x2d18cff828b570.device/start failed with result 'dependency'.
[  234.166607] systemd[1]: Job cryptsetup@luks\x2d26ad1e84\x2d5f11\x2d4fa5\x2dad13\x2d18cff828b570.service/start failed with result 'dependency'.
[  234.166649] systemd[1]: Job dev-disk-by\x2duuid-26ad1e84\x2d5f11\x2d4fa5\x2dad13\x2d18cff828b570.device/start failed with result 'timeout'.


Similar to bug 692248, but my boot partition is simply /dev/sda3, not a /dev/md device.

My partition is not encrypted via Luks, but does have hardware disk encryption (FDE).
Comment 1 Mark van Rossum 2011-05-08 20:42:31 UTC 
Created attachment 497680 [details]
grub config
Comment 2 Mark van Rossum 2011-05-08 20:43:05 UTC 
Created attachment 497681 [details]
fstab
Comment 3 Lennart Poettering 2011-05-11 14:25:56 UTC 
So the timeout happens because you seem to have some entries in /etc/cryptsetup. If you don't use dm-crypt (i.e. LUKS), then you should not list any devices in there.
Comment 4 Mark van Rossum 2011-05-11 14:50:42 UTC 
Turned out to be an old 
/etc/crypttab 
file
Note You need to log in before you can comment on or make changes to this bug.