Bug 1085784
| Summary: | Logical volume detection failure in 3.13.8 | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Adam Huffman <bloch> | ||||
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> | ||||
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 20 | CC: | gansalmon, itamar, jmcasanova, jonathan, kernel-maint, madhu.chinakonda, mchehab, michele, simon.fayer05 | ||||
| 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: | 2014-04-28 12:29:53 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: | |||||||
| Attachments: |
|
||||||
I confirm the same behavior of my desktop system that is configured with a RAID. I reproduced it with the following kernels: kernel-3.13.8-200.fc20.x86_64 kernel-3.13.9-200.fc20.x86_64 kernel-3.13.10-200.fc20.x86_64 I have no problems with the previous version. kernel-3.13.7-200.fc20.x86_64 Can you verify that it is not due to a newer version of dracut that is not including some needed modules? Is this raid software or via hw raid card? (lspci please) thanks, Michele (In reply to Michele Baldessari from comment #2) > Can you verify that it is not due to a newer version of dracut that is not > including some needed modules? It was possible related, today I received after a yum update the dracut-037-11.git20140402.fc20.x86_64 Then I regenerated the the initramfs with dracut -f initramfs-3.13.10-200.fc20.x86_64.img 3.13.10-200.fc20.x86_64 Reboot and this kernel now completes the boot process.. I've tried the same with the previous not-working kernel again 3.13.9-200.fc20.x86_64 and it solved the problem again. After checking, it seems that in my case it was related to https://bugzilla.redhat.com/show_bug.cgi?id=1084766 > > Is this raid software or via hw raid card? (lspci please) I'm using Raid Software *** This bug has been marked as a duplicate of bug 1084766 *** |
Created attachment 884474 [details] rdsosreport from the bad kernel, when booting has failed Description of problem: This week we had a bad sector on a disk on a particular machine, meaning that we had to reboot into the vendor diagnostics (because the machine wouldn't boot). Once the disk was fixed, the machine still wouldn't boot. It wasn't finding the root logical volume. I was able to get around this by manually starting the MD device backing some of the LVs and activating them all. However, the names were all scrambled i.e. when I mounted the rootvol LV, a different LV was actually mounted. When I rebooted into the previous kernel (3.13.7), they were detected normally. Version-Release number of selected component (if applicable): kernel-3.13.8-200.fc20.x86_64 How reproducible: Every time Steps to Reproduce: 1. Boot system 2. 3. Actual results: System drops to dracut emergency shell Expected results: System boots normally Additional info: