Bug 699210
| Summary: | boot hangs at "Starting /dev/disk/by-uuid" | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Bonzo1834 <bz1834> | ||||
| Component: | systemd | Assignee: | Lennart Poettering <lpoetter> | ||||
| Status: | CLOSED WORKSFORME | 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-04-27 00:20:15 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
No device by that uuid showed up. Is this on LVM? Are you sure you have this device? If you check /dev/disk/by-uuid/, do you you the device node symlink there? Indeed, there is no such device in /dev/disk/by-uuid/ (sorry, I could have checked that earlier). Now why would this device appear at boot then? I have formatted one partition with a new filesystem after the F15 install. I guess this creates a new UUID. Could this have something to do with it? Solved, the problem was a wrong swap UUID in fstab. Grepping for the missing UUID in /etc showed that it was present in /etc/fstab and the swap partition: $ cat /etc/fstab ... UUID=ebb03fd1-5a00-4721-94b6-d3693a40c64f swap swap defaults 0 0 ... The swap partition UUID had changed because the partition had been reformatted outside of Fedora 15 during install of a different Linux distribution: $ blkid -t TYPE="swap" /dev/sda7: UUID="7c35c42f-dc57-4e13-b541-8000571175cf" TYPE="swap" In fact, swap wasn't used in Fedora 15 (swapon -s showed no partition). Simply changing the swap UUID in fstab did the trick: $ swapoff -a $ vi /etc/fstab $ swapon -a swapon -s now shows the swap partition and the boot process doesn't hang anymore. Now, could this problem have been better signalled to the user? All /var/log/boot.log says about swap is: Starting Enable all detected swap partitions... Started Enable all detected swap partitions. It also says "Started Relabel all filesystems, if necessary." => does 'relabel' refer to uuid stuff? If so, could the swap partition be relabeled as well? /var/log/messages has messages:Apr 25 09:04:00 a1 kernel: [ 188.421752] systemd[1]: Job dev-disk-by\x2duuid-ebb03fd1\x2d5a00\x2d4721\x2d94b6\x2dd3693a40c64f.swap/start failed with result 'dependency'. So yes, the reference to swap is there. relabel refers to selinux. |
Created attachment 494501 [details] boot.log Description of problem: Boot hangs after message "Starting /dev/disk/by-uuid/..." and after a couple of minutes continues with "aborted because a dependency failed." It doesn't seem to harm the system, everything is working afterwards. Version-Release number of selected component (if applicable): How reproducible: Always (on every boot) Steps to Reproduce: 1. boot machine 2. switch to text (F2) 3. messages are displayed Actual results: system hangs for a couple of minutes Expected results: faster boot process Additional info: The machine is a Dell Latitude E4300 laptop.