Hide Forgot
Created attachment 1226726 [details] Kernel panic messages when booting Fedora (4.8.10-300. fc25.x86_64) 25 Description of problem : Kernel panic - not syncing : VFS : Unable to mount root fs on unknown-block(0,0) Version-Release number of selected component (if applicable): Fedora (4.8.10-300. fc25.x86_64) 25 How reproducible: The problem first occurred after running "dnf upgrade" from the earlier Fedoara version Fedora (4.8.8-300. fc25.x86_64) 25. Every boot with the new 4.8.10 results in hanging , see attachment . Booting with the older 4.8.8 still works well. Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Created attachment 1226727 [details] Boot menu on my PC
99% of the time this is because the corresponding initramfs isn't being loaded for the kernel. Please attach your grub configuration file and the output of 'ls -l /boot/initramfs-*'
Created attachment 1226856 [details] result of 'ls -l /boot/initramfs-*'
Created attachment 1226857 [details] print of '/boot/grub2/grub.cfg'
Yep, you're missing the corresponding initramfs (and the line to load it in grub). This happens from time to time and is likely a dracut issue.
Created attachment 1229661 [details] Selecting 4.8.10-300 fc25 still does not boot. Selecting 4.8.10-330 still does not boot.
Created attachment 1229662 [details] But the new 4.8.11-300 kernel does boot correctly But selecting the new 3.8.11-300 kernel does boot correctly.
Created attachment 1229669 [details] Proof that 4.8.11-300 boots correctly Proof that 4.8.11-300 boots correctly. So the immediate problem is solved so far as i am concerned. --Chrit
Created attachment 1229670 [details] Better view-able boot error messages of 4.8.10-300 fc25
try: # dracut --regenerate-all and attach the output please
Created attachment 1242215 [details] Dracut --regenerate-all output
sorry, add the "--force" option of course.
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. 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 '25'. 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 25 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 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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.