| Summary: | 4.3.3-303.fc23.x86_64: kernel panic on boot: 'not syncing: VFS: Unable to mount root fs on unknown block (0,0)' | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | reescf | ||||
| Component: | grubby | Assignee: | Peter Jones <pjones> | ||||
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 23 | CC: | bcl, gansalmon, itamar, jonathan, kernel-maint, madebr, madhu.chinakonda, mchehab, pjones, reescf | ||||
| Target Milestone: | --- | Flags: | jwboyer:
needinfo?
(reescf) |
||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2016-12-20 18:19:31 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: | |||||
| Attachments: |
|
||||||
|
Description
reescf
2016-01-30 17:57:46 UTC
95% of the time this is because your grub.cfg is missing the line to load the initramfs or the initramfs file itself is corrupted or incomplete. Each kernel stanza should have both the linux and initrd lines included in it to load the corresponding files. Please attach your grub.cfg file. Also, please attach the output of 'ls -l /boot/initramfs*' As a side note, if you find yourself having to regenerate the grub.cfg file after a kernel install, that is a sign of your userspace setup being broken. How it is broken I have no idea, but it should not be necessary to run grub2-mkconfig by hand. Created attachment 1120579 [details]
/boot/efi/EFI/fedora/grub.cfg
I just installed kernel 4.3.4-200.fc22 and am facing the same kernel panic. (screenshot at http://share.pho.to/A0lCh since sysctl -b -1 does not show anything). My root filesystem is btrfs. Booting 4.2.8-200 works. I am using it now. # ls -l /boot/initramfs* -rw-rw-r--. 1 root root 46570611 May 26 2015 /boot/initramfs-0-rescue-dc2e42bdbf274fd4ab4fc03989cafb0b.img -rw-r--r--. 1 root root 19292643 Dec 18 07:03 /boot/initramfs-4.2.7-200.fc22.x86_64.img -rw-r--r--. 1 root root 19305332 Dec 27 15:26 /boot/initramfs-4.2.8-200.fc22.x86_64.img -rw-r--r--. 1 root root 19373400 Feb 2 20:20 /boot/initramfs-4.3.4-200.fc22.x86_64.img Attached, you can find /boot/efi/EFI/fedora/grub.cfg I noticed my grub.cfg did not have the initrdefi line. Running grub2-mkconfig to regenerate the grub.cfg makes the panic disappear. This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '23'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 23 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |