Bug 2397059 - kernel panic on grub boot: "VFS: Unable to mount root fs on unknown-block(0,0)"
Summary: kernel panic on grub boot: "VFS: Unable to mount root fs on unknown-block(0,0)"
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 42
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-09-20 00:17 UTC by Ross Tyler
Modified: 2026-05-06 14:08 UTC (History)
13 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Ross Tyler 2025-09-20 00:17:18 UTC
1. Please describe the problem:
At grub boot time, I get

KERNEL PANIC!
Please reboot your computer.
VFS: Unable to mount root fs on unknown-block(0,0)

2. What is the Version-Release number of the kernel:
6.16.7-200

3. Did it work previously in Fedora? If so, what kernel version did the issue
   *first* appear?  Old kernels are available for download at
   https://koji.fedoraproject.org/koji/packageinfo?packageID=8 :
The Fedora 42 6.14 kernel works.
The Fedora 41 6.15 kernel works (for Fedora 42).

I think that I first noticed the problem when I updated my Fedora 41 system
to a 6.16 kernel.
I think that kernel would not shutdown properly.
I decided that it was time to upgrade from 41 to 42.

During the upgrade process, the computer would not shutdown.
A force power-cycle resulted in the kernel panic at boot time.
Booting from the old kernels (mentioned above) worked.
I removed the faulty kernel, tried several times to reinstall it, with no luck.
I installed the Fedora 42 6.14 kernel and kept the old Fedora 41 6.15 kernel.
I think that the Fedora 41 6.16 kernel was bad too.

Twice since then, my automatic system updates have tried (and failed) again.
I just keep removing the kernel each time and use an old one.

4. Can you reproduce this issue? If so, please provide the steps to reproduce
   the issue below:
Install this kernel and reboot.

5. Does this problem occur with the latest Rawhide kernel? To install the
   Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by
   ``sudo dnf update --enablerepo=rawhide kernel``:
I have not tried.

6. Are you running any modules that not shipped with directly Fedora's kernel?:
No.

7. Please attach the kernel logs. You can get the complete kernel log
   for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the
   issue occurred on a previous boot, use the journalctl ``-b`` flag.
There is no log.
It does not boot.

Comment 1 Fedora Release Engineering 2026-05-06 14:08:19 UTC
This message is a reminder that Fedora Linux 42 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 42 on 2026-05-13.
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
'version' of '42'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 42 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 Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.


Note You need to log in before you can comment on or make changes to this bug.