Bug 1047541
| Summary: | kernel panic early in boot | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | sean darcy <seandarcy2> | ||||||||
| 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: | 19 | CC: | gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda, michele, seandarcy2 | ||||||||
| 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: | 2014-01-02 01:31:26 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: |
|
||||||||||
Created attachment 843824 [details]
bottom of screen after panic
Created attachment 843826 [details]
early dmesg from kernel-3.11.10-100.fc18.x86_64
Hi Sean,
the panic happens in init/do_mounts.c:mount_block_root() and is explicitely
forced by the kernel because it has not been able to find the specified
root (UUID=0ee4b2cd-0143-4172-9d7f-c1bef74a1150): panic("VFS: Unable to mount root fs on %s", b);
This can happen for different reasons. My first thought would be that the
initrd file is missing some driver or has some other issues (although other
causes are certainly possible).
Could you attach /boot/grub2/grub.cfg and the initrd file under /boot
corresponding to the 3.12.5 kernel?
Thanks,
Michele
You put me on the right path: initramfs-3.12.5-200.fc19.x86_64.img was not installed. I reinstalled the kernel, and all is well. It seems there was some error by fedup on the upgrade. Thanks for the help. sean |
Created attachment 843823 [details] top half of screen after panic Description of problem: kernel panic on boot Version-Release number of selected component (if applicable): kernel-3.12.5-200.fc19.x86_64 How reproducible: boot kernel Steps to Reproduce: 1.boot kernel 2. 3. Actual results: kernel panic. The screen scrolls beyond the beginning of the panic. I'm attaching screen shots of what does show on the console. It's too early in boot for any logging. Expected results: boot Additional info: I've just upgraded to 19 from 18. kernel-3.11.10-100.fc18.x86_64 boots without problems. I've attached two jpeg's of the screen after the panic. Also, I've attached a text file of dmesg from a boot of kernel-3.11.10-100.fc18.x86_64.