Bug 859716
Summary: | kernel-3.5.4-1.fc17.x86_64 fails to start storage devices, services | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | josip@icase.edu <jl-icase> |
Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
Status: | CLOSED WORKSFORME | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | urgent | Docs Contact: | |
Priority: | unspecified | ||
Version: | 17 | CC: | gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda, paramsingh258 |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-01-02 17:40:06 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
josip@icase.edu
2012-09-23 13:56:06 UTC
The output of dmesg from a failed kernel-3.5.4-1.fc17.x86_64 boot looks benign up to this point (note the "dependency" complaints): [ 5.631806] EXT4-fs (sdg1): mounted filesystem with ordered data mode. Opts: (null) [ 5.674494] EXT4-fs (sda3): mounted filesystem with ordered data mode. Opts: (null) [ 94.944481] systemd[1]: Job nfs-lock.service/start failed with result 'dependency'. [ 94.944493] systemd[1]: Job rpcbind.service/start failed with result 'dependency'. [ 94.944503] systemd[1]: Job rpcbind.socket/start failed with result 'dependency'. [ 94.944541] systemd[1]: Job cups.socket/start failed with result 'dependency'. By contrast, kernel-3.5.4-1.fc17.x86_64 boot proceeds normally at the equivalent point. Uhm, in "Comment 1", there is a typo: kernel-3.5.3-1.fc17.x86_64 boots normally, kernel-3.5.4-1.fc17.x86_64 fails. It's not booting for i686 either Boot still fails after upgrading to kernel-3.5.4-2.fc17.x86_64 Boot still fails after upgrading to kernel-3.6.1-1.fc17.x86_64 On another computer (AMD, not Intel), kernel-3.6.2-4.fc17.x86_64 also failed to boot. Original kernel-3.3.4-5.fc17.x86_64 boots fine on this AMD machine. Good news: Upgrading to kernel-3.6.3-1.fc17.x86_64 also resulted in normal boot. Progress? I have NOT yet confirmed that this upgrade fixes the original problem on my Intel machine. Stay tuned. I found a fix for my Intel computer -- the problem was that kernel started naming RAID devices differently, so they could not be mounted. In kernel 3.4.x, those devices are symbolic links like /dev/md/FDQN:name, where FDQN is the fully qualified host name. With kernels 3.5.x and 3.6.x, those symbolic links are simply /dev/md/name. Go figure... Changing /etc/fstab to match fixed the boot problem. |