Post-update error: "end kernel panic not syncing vfs unable to mount fs on unknown-block(0,0)"
Linux - KernelThis forum is for all discussion relating to the Linux kernel.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Post-update error: "end kernel panic not syncing vfs unable to mount fs on unknown-block(0,0)"
Hi.
I'm on Debian 10 Stable. I recently did an update (about 3 weeks since the previous one). I was using a backported kernel.
Perhaps the update went awry?
The laptop (it's a secondary PC) keeps shutting off and rebooting itself.
I can boot from a live USB. I can also enter the Grub menu and select the oldest kernel, then unlock the system (I'm using LUKS). It then asks me to put in the sudo password to become root. I tried removing some kernels to save space in /boot. I can get a GUI for root (not for my normal user) by entering startx - the WiFi is not available though.
I'm wondering what's the best fix or should I just reinstall the whole OS?
Thanks.
Last edited by linustalman; 05-03-2021 at 07:49 AM.
This error means your kernel cannot access HDD controller and any disks connected to it.
You get this error if your kernel relies on initramfs and it is unavailable. For instance, kernel upgrade was interrupted and did not complete properly, then you get this error.
You need to reinstall kernel, not OS. And while at it pay close attention to what it is doing, take notes if you see any errors or anomalies. You have CLI root access working, this is enough to fix it.
This error means your kernel cannot access HDD controller and any disks connected to it.
You get this error if your kernel relies on initramfs and it is unavailable. For instance, kernel upgrade was interrupted and did not complete properly, then you get this error.
You need to reinstall kernel, not OS. And while at it pay close attention to what it is doing, take notes if you see any errors or anomalies. You have CLI root access working, this is enough to fix it.
Hi Emerson.
So I could just find an ethernet cable and connected to my wifi router, via it and the laptop will pick up the network while I'm in the root CLI?
If this was a botched install you already should have all .deb files downloaded and no net connection is necessary. Why don't you try it.
Edit: often problems like this occur when running out of disk space or inodes.
Ok.
Is my command from post #3 correct if I cannot reinstall from the .deb files?
If I go the .deb files offline route - what command(s) would be required?
What version of kernel you built it for, the one you are running? (My Debian experience is rusty, I believe by default it builds for running kernel, not what you want.)
What version of kernel you built it for, the one you are running? (My Debian experience is rusty, I believe by default it builds for running kernel, not what you want.)
The only kernel that I can get anywhere with is by booting with 5.10.0-0.bpo.3-amd64. It's the oldest kernel on my system.
Yes, I understand that, but you need to rebuild the initramfs for your failing kernel, that's the idea. BTW, you can use your old kernel for normally operating your Debian, just edit the Grub line when at Grub menu and remove the part what puts it in single user mode.
Yes, I understand that, but you need to rebuild the initramfs for your failing kernel, that's the idea. BTW, you can use your old kernel for normally operating your Debian, just edit the Grub line when at Grub menu and remove the part what puts it in single user mode.
There was no mention of single user mode. Just 'ro' and 'quiet' the end of the line.
I connected the laptop to my wireless modem-router via an Ethernet cable. I went into the oldest kernel. I entered my root password and tried to update and ping - no joy. I then dropped to my user account on the terminal with 'su myusername' - still no joy -- both cases returned some issue with DNS. With Debian 11 out soon, I may just leave this be and wait for Bullseye or just install something like Peppermint 10.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.