Kernel Panic - Unable to mount root fs on unknown block (0,0)

Your prompt above referenced the higher 5.15.0-67...
Are you booted into the .56 kernel and the .67 is installed?

Yes, is that not how its supposed to be?

It looks almost as if your .67 kernel is incompletely built...
Can you try:

sudo apt install linux-headers-5.15.0-67-generic linux-modules-5.15.0-67-generic linux-modules-extra-5.15.0-67-generic linux-image-5.15.0-67-generic

Reboot and then try the above procedure...


None have upgraded

1 Like

Same thing after all that, it cannot find the files needed :roll_eyes:

What about

update-initramfs -u -k 5.15.0-56-generic


Just ignore previous lines

Ok, now run

update-grub

Or if in Non-Root:

sudo update-grub

Done, then what?

Reboot and test...

1 Like

Shoot, same kernel panic from .67

Roll back to the 56 kernel:
Boot with the Grub menu and select Advanced Options for Zorin
From here, select the 56 kernel to boot from

Ok, I'm in it, now what?

If everything is working, you can set the .56 as your default boot:

Ok, cool, so does this mean I'm stuck with 56 until I find a solution? And also what if there's an update, do you think it would have the same problem too?

These two questions blend into each other. I think it is likely that the next update will help resolve this issue. So after then ext update, remove the .67 kernel and then boot into the next Later kernel that the update brings.
If it works, great. If not, you can just fall back to the .56

Unless the later kernels have something you need; then having the Latest kernel is not only not necessary... But can even be Worse. Earlier stable kernels tend to perform better.

2 Likes

Alright thank you for the help mate, I guess I'll just wait for now, but if I find a solution, I will report back for anyone with the same problem. :grin:

What is the solution? I also want to know. :grin:

Roll back to previously working kernel, then set it as default kernel to boot up.

1 Like

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.