| Summary: | 80 second delay after home.mount | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Ryan Rix <ry> | ||||||||||
| Component: | systemd | Assignee: | Lennart Poettering <lpoetter> | ||||||||||
| Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||
| Priority: | unspecified | ||||||||||||
| Version: | 15 | CC: | johannbg, lpoetter, metherid, mschmidt, notting, plautrba | ||||||||||
| Target Milestone: | --- | ||||||||||||
| Target Release: | --- | ||||||||||||
| Hardware: | Unspecified | ||||||||||||
| OS: | Unspecified | ||||||||||||
| Whiteboard: | |||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||
| Doc Text: | Story Points: | --- | |||||||||||
| Clone Of: | Environment: | ||||||||||||
| Last Closed: | 2011-05-17 15:58:18 UTC | Type: | --- | ||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||
| Documentation: | --- | CRM: | |||||||||||
| Verified Versions: | Category: | --- | |||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||
| Attachments: |
|
||||||||||||
Created attachment 499016 [details]
/etc/fstab
Please attach: - /etc/crypttab - the output of "dmesg" after booting with "log_buf_len=1M systemd.log_level=debug systemd.log_target=kmsg" Created attachment 499268 [details]
/etc/crypttab
Created attachment 499269 [details]
dmesg output
[ 104.860601] systemd[1]: Job dev-disk-by\x2duuid-771b3e17\x2dd4c3\x2d42ad\x2da85e\x2da8e39f6b0a14.device/start timed out. Your crypttab has: luks-771b3e17-d4c3-42ad-a85e-a8e39f6b0a14 UUID=771b3e17-d4c3-42ad-a85e-a8e39f6b0a14 none But no disk with that UUID appears during boot. If no such disk exists, remove the line from crypttab. Your fstab does not mention the disk. Huh, I wonder where that came from, then, probably a previous disk layout...I guess I should probably jsut reinstall at some point. Removing that line did indeed fix that part of my boot. Now on to file bugs for the rest of it. thanks Michal! |
Created attachment 499015 [details] output of systemd-analyze plot Description of problem: There is an 80 second delay after home.mount is Started Version-Release number of selected component (if applicable): [rrix@stinkpad ~]$ rpm -qa|grep systemd systemd-units-26-1.fc15.x86_64 systemd-26-1.fc15.x86_64 systemd-sysv-26-1.fc15.x86_64 wine-systemd-1.3.19-1.fc15.noarch How reproducible: Update from Fedora 15 using preupgrade from 14, then do a complete yum upgrade to the listed version and boot the machine Actual results: 80 second delay between Starting /home... and Started /home. and Starting Cryptography Setup for luks-771b3e17-d4c3-42ad-a85e-a8e39f6b0a14 ^[[1;31maborted^[[0m because a dependency failed. Is echo'd shortly after those 80 seconds are up. That lucks is my / directory, though, and it appears to come up just fine? o.O Expected results: Boot proceeds normally Additional info: Attaching various documentation