Fedora 16 Kernel upgrade broke system - kernel panic and unable to boot
FedoraThis forum is for the discussion of the Fedora Project.
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.
Fedora 16 Kernel upgrade broke system - kernel panic and unable to boot
Hi All,
I've already posted the following problem on the Fedora Forums and didn't get a reply, so have decided to come back to LQ and try here in the hope someone can help
Well, I thought it would never happen to me, but I installed a kernel update 3 days ago and its borked my system - and as luck would have it, this is my pride-and-joy "production" machine... BAH.
On rebooting, I just got the message:
Quote:
Kernel Panic - not synching: VFS: Unable to mount root fs on unknown-block (0,0)
I had two old kernels available, but discovered I couldn't now boot from either of those either - I got the blue lines to indicate the OS was loading, but then at the end they froze. Checking the verbose output showed it was sticking at:
Quote:
Started LSB: Automatically install DKMS modules for new kernels (OK)
I burnt a copy of the DVD .ISO and booted off that into rescue mode... so far so good. I discovered there was an incomplete yum transaction pending. Running a quick
Code:
yum-complete-transaction
fixed that bit, but I was still unable to boot.
I was able to get an ethernet connection working, and ran yum-update and yum-upgrade much installed another new kernel, but still no joy. I tried running
Code:
yum reinstall kernel
for each of my three kernels in turn, but that told me that the kernel wasn't available.
I've tried a few things, and have ended up uninstalling both newer kernels, leaving me with just the one last known-good kernel. I checked that the initrd /boot/initramfs-kernel-version.img existed for the kernel version I was tying to boot in /boot/, but that all looked in order (I tried running dracut --force anyway).
At some point (I can't remember exactly where, and I'm not at the machine at the moment) I got this output that seems to show what the problem is:
Quote:
E: FATAL: Could not load /lib/modules/3.1.0-7.fc16.x86_64/modules.dep:
No such file or directory
find: @/lib/modes/3/1/0-7.fc16.x86_64/@ : No such file or directory
So - my question is this - how do I reload (or rebuild?) that particular kernel module? Or is my system completely borked? I have to confess I'm rapidly reaching the outer limits of my Fedora knowledge on this one, and most fixes I've read assume the ability to choose a working kernel at the grub boot screen, which I don't have...
Help!
TIA,
itsjustarumour
Last edited by itsjustarumour; 05-08-2012 at 01:18 PM.
I've already posted the following problem on the Fedora Forums and didn't get a reply, so have decided to come back to LQ and try here in the hope someone can help
You may have seen this by now, but just in case...
Your problem reminds me of one I had some time back, but now I can't find any reference to it to see the solution would help, sorry.
If I do track anything down that is useful, I'll let you know.
Post the solution if you find it.
Looking at those kernel levels, they're not the latest anyway. I have 3.3.2-6, 3.3.0-4 and 3.2.10-3 - and I'm not too sure when I last accepted an update.
Normally (for Fedora) I'd reckon the VFS message indicates a broken initrd. Dracut will presumably only load modules for the current environment - where did you run it from ?.
Might be worth checking the UUIDs (from the liveCD in need) as suggested.
My thought is to boot from a live CD, chroot to the borked installation, back up any existing initramfs file (just in case, you know...), run dracut to regenerate the initramfs file, then reboot the system.
Your problem reminds me of one I had some time back, but now I can't find any reference to it to see the solution would help, sorry.
If I do track anything down that is useful, I'll let you know.
Post the solution if you find it.
Cheers,
Terry
Thanks Terry, I just saw that. Theres a couple of suggestions there now so I'll see how I get on, and will post up here if I get things sorted.
Looking at those kernel levels, they're not the latest anyway. I have 3.3.2-6, 3.3.0-4 and 3.2.10-3 - and I'm not too sure when I last accepted an update.
Normally (for Fedora) I'd reckon the VFS message indicates a broken initrd. Dracut will presumably only load modules for the current environment - where did you run it from ?.
Might be worth checking the UUIDs (from the liveCD in need) as suggested.
Thanks for the tip syh00, I'll add that to my "things to try" list!
Btw - when I ran dracut, I'd used the DVD .ISO to go into rescue mode (the Fedora 16 CDR doesn't contain this functionality, have to use the DVD), done a "chroot /mnt/sysimage" and then run dracut from there.
Last edited by itsjustarumour; 05-08-2012 at 12:43 PM.
My thought is to boot from a live CD, chroot to the borked installation, back up any existing initramfs file (just in case, you know...), run dracut to regenerate the initramfs file, then reboot the system.
Thanks for the tip RockDoctor, but that didn't fix things in my case...
Will post back with any updates. Glad for the help on this forum!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.