Ubuntu :: Kernel Panic After Update/upgrade 22-09-2010
Sep 23, 2010
Yesterday i was prompted by my update manager to update some packages. I really don't remember which but i updated.
After reboot the box now kernel panics. I don't believe i get a ubuntu splash screen, and at this point i can't figure out how to get to my grub, in case a kernel was upgraded and it's possible to boot to different kernel.
i noticed some words like 'mantis', 'oops' and 'dvb_core' was a part of the text i get on the screen.
Can this be because of a dvb* upgrade that breaks something important ?
If needed, i should be able to boot via liveCD, or i could take a picture of the errors.
I have the following strange thing with a RHEL4 installation. Since last week, the system did a reboot and now something is really fucked up. During boot we get the following messages (don't care about 'strange' typo's, my colleague typed it 'blind' from the screen)
Code:
The strange thing is that we never see a 'could not mount blabla' or similar messages. First we thought it was a failing kernel update by plesk, but even after manually updating the kernel with RHN RPM's, still the same message. Booting with rescue mode and then chroot the system works. After that we even can start things like plesk and so on.
We double checked things with another RHEL4 install, and at least two things were odd:
1: the working machine has /dev/dm-0 and /dev/dm-1, the broken one doesn't
2: some files on /dev didn't have group root, but 252
We tried to recreate the /dev/dm-X nodes with [vgmknodes -v], output:
Code:
A fdisk /dev/sda shows: /dev/sda2 XX XXX XXXXX Linux LVM (I removed the numbers because this line is from another machine, but rest was identical)
We have a copy of the boot partition so if one need more info please let me know.
grub.conf:
Code:
last part of init extracted from initrd-2.6.9-78.0.8.ELsmp.img:
Today I upgraded one of my computers with the following command
% yum upgrade
Before the upgrade the computer was running CentOS 5.3 with the versionlock plugin and kernel 2.6.18-128. The update went smoothly (no dependency problems).
If I try to reboot with the new kernel (2.6.18-194), I get the following:
Found volume group VolGroup00 using metadata type lvm2 2 logical groups in VolGroup00 now active mount: error mounting /dev/root on /sysroot as ex3t: No such device setuproot: moving /dev failed: No such file or directory
[Code].....
If I reboot with the previous kernel (2.6.18-128), everything is fine.
After installing the latest updates (dont know which ones) yesterday, I get a kernel panic (LED lights flashing at the keyboard and black screen) when starting X (the login manager). I am running on 64 bit with the proprietary ATI catalyst driver. How can I start in text only mode?
I've been trying to get Ubuntu on my beloved 4 year old Acer desktop that's been chugging like a tank. However, after either a fresh install or upgrade, I would get the following error:"Kernel panic - not syncing: VFS: Unable to mount to root FS on unknown-block(0,0)".I've looked here and there, and one of the issues it would seem is the kernel not recognizing my hard drive if I'm correct. One of the suggestions was to upgrade the kernel however, I have no idea how to do such a thing if I can't get into the OS.
I ran an upgrade to 11.04. It boots fine into KDE, then panics (flashing Caps lock) about a minute later. The Live CD runs fine. Here's the part of my syslog that looks related:
Update manager downloaded and installed latest kernel (Ubuntu, Linux 2.6.31 -16 -generic). When I tried to restart I get the message { 1.661235}Kernel panic - not syncing: VFS: unable to mount root fs on unknown - block(8,38). Everything works fine on previous update.
I have a system that was upgraded from Debian 7 to 8. Unfortunately it is not able to boot from the new kernel 3.16. Only the old 3.2 kernel is able to boot. I could transfer a backup, install it in Virtualbox, redo the upgrade and I can reproduce the error..The last error before "panic" is this line
Code: Select all 59.073579] Freeing unused kernel memory: 216K (ffff8800017ca000 - ffff880001800000) Loading, please wait... [ 59.226154] systemd-udevd[53]: starting version 215 [ 59.326564] random: systemd-udevd urandom read with 4 bits of entropy available Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... /init: .: line 210: can't open '/scripts/init-premount/ORDER' [ 59.552148] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000200
I learned yesterday that doing a massive upgrade on my system while moving was a BAAAD idea.The upgrade process was going along just fine, it was all downloaded and was actually installing that last time I saw it. I unplugged my laptop to move a bookcase out, and completely forgot to plug it back in. After I got back from moving a load, I found my computer was off. I tried to boot up, and I got an error that kind of freaked me out. It reads as follows:
Code:kernel panic not syncing vfs unable to mount root fs on unknown-block(0,0)I'm able to get to grub just fine, and my windows partition loads up just fine, but any of the linux kernels fail similarly when I attempt to load them.I'm sure that I can fix this, I just have no idea how. Probably has something to do with a live cd.
I had 9.10 installed on my IBM Lenovo Thinkpad, x301. I was performing updates as normal, and chose the Upgrade button to upgrade me to 10.04. Everything started fine, but upon reboot, no bueno, Kernel Panic!
The exact message was "Kernel Panic ubuntu - not synching VFS Unable to mount root fs".
I thought this was a grub issue. Since grub2 now is installed... But it was not. I think it ended up being a problem with some of my configuration files.
I have three kernels I tried: 1. 2.6.32-22 2. 2.6.31-21 3. 2.6.31-20
The first threw me into the kernel panic. The second would hang on "init crypto disks" The third would hang on "checking battery state"
I noticed (from reading another thread) that while these are loading up that you can click on alt-ctl-F1 thru F6 and get prompt. (I also had my home directory encrypted, thought that was part of the problem, but it wasnt).
Once I get passed the loging, I am able to poke around. I tried manually start Gnome via "sudo service gdm start", but it failed. Said it was missing a configuration file. Then I tried on "sudo dpkg-reconfigure gdm" and it would not work. Saying some configuration files are missing or broken. It also said something about dpkg --configure -a, I am assuming this configures everything...
So I tried "sudo dpkg --configure -a" And selected 'y' to every option. Which basically installs the package creators default settings, and viola! Works.
Just wanted to share that knowledge for the other stuck in the upgrade hell.
Normally I would just copy my files off and reinstall, but it was encrypted... Another headache. I guess good in case someone stole my laptop.
I have a new acer machine which runs fine on 10.10 mythbuntu desktop livecd. Install seemed fine.
Then I ran an update and on reboot I get a kernel panic error. Research on this reveals it as a very deep subject which can consume many hours, so I opted to reinstall.
This time with ubuntu 10.10. I've tried different CDs, liveusb. Same errors.
So, the question is this - where do I concentrate my efforts - somewhere ubuntu doesn't like this machine, or grub. Does a reinstall overwrite the grub install too? Or do I have a bogus grub install I need to purge before I will get anywhere.
I am running Debian squeeze. A while ago I upgraded my kernel to 2.6.38 from backports. Just now I thought it would be good to upgrade to 2.6.39 from backports. Upgrade went fine, but after rebooting I get a kernel panics rightaway.
"No filesystem could mount root, tried:" "Kernel panics = not syncing: VFA: Unable to mount root fs on unkown-block(0,0)."
This is the first time one of Linux installations halts/panics on booting, so I don't know what to do now. I tried booting the recovery entry from the grub boot menu, but same result.
It appears that I have really messed up my machine. I was trying to get matlab working on FC 11 and I ran into libc.so.6 issues, so I put an older file libc.2.3.1.so in /lib/tls/ directory and created a symbolic link libc.so.6 to see if the application would work. Unfortunately at the same time the system did some updates and the system hung, so I ended up rebooting, but now it gets stuck at boot screen (after grub) with a kernel panic - not syncing: attempted to kill init.I just need a way to get to the directror /lib/tls and delete the link and the older .so file I threw in there. How do I get this accomplished. I cannot get even to a shell from the boot screen.
After update to 5.3 and reboot I got this error. googling for it I found that it is a known bug in kernel REHL 5.3 and there is also a patch for it [URL]. I am very new to linux, so how to apply, or just wait for a new kernel?
I got a notification that there was an upgrade available today in ubuntu 9.10 64, after the update i restarted my system and while booting i encountered this error message:
Kernel panic - not syncing : VFS : Unable to mount root fs on unknown - block (8,17)
does this have something to do with the OS looking at the wrong hd? theres no command prompt to actually do anything and i tried booting in safe mode and had the same problem. Let me know what i can do!
The server runs# uname -r2.6.18-128.4.1.el5However, today I executed yum update kernel*due to security advisory. I was just about to reboot the system when I realized that it runs VMWare Server Instance that will most likely fail to restart after kernel upgrade (I had a hard time fixing it after previous kernel update). Now I want to keep 2.6.18-128.4.1.el5 after reboot.I see that new kernel is scheduled for booting:
I recently upgraded from FC7 to FC10 (Also, the Kernel from 2.6.22.9 to 2.6.27.19).I did the upgrade through Yum (First installed the fc10 rpms, then did yum upgrade).Now the new Kernel won't boot.These are the options in GRUB for the new Kernel
I'm noticing that maybe twice a month the Update Manager is asking me to upgrade my kernel. Currently it's asking me to move to 2.6.32.24.25. Is this the smart thing to do? Are these primarily securtiy updates to the kernel?
I have recompiled a few kernels, but all on 32bit systems so not sure if that has anything to do with it.
Running Arch Linux 64bit, most recent version.
Kernel Output:
Code:
My first thoughts was that it might be my grub bootloader configuration, so had a big play around with that but it didn't fix it. Also made sure support was built for filesystems. However almost all that Fstab mounts are ext3 anyway, and certainly the root and /boot are. Now thinking it may be a memory error so will run a check when I shutdown.
Dell laptop booting from a USB stick with a CentOS 5.5 minimum installation.
Uncompressing Linux...OK, booting the kernel. Red Hat nash version 4.2.1.13 starting sda: assuming drive cache: write through sda: assuming drive cache: write through mount: error 6 mounting ext3 mount: error 2 mounting none switchroot: mount failed: 22 umount /initrd-dev failed: 2 Kernel panic - no syncing: Attempted to kill init!
1. Does minimum installation not drop on a kernel or initrd with ext3 support? I can't imagine that's true, but have to ask.
2. The USB stick is single partition ext3. Maybe there is some limitation specifically related to USB stick booting that requires boot to be FAT16 or FAT32? Except the CentOS 5.5 installer refuses to let me install on either FAT.
3. How can I do the equivalent of lsmod on a linux installation that will not boot? i.e. I have CentOS x86_64 running in VirtualBox, I can plug the USB stick in there, so how do I get information on the USB stick's kernel and initrd if I can't boot from it?
4. Is it possible to rebuild the i386 based initrd on this USB stick, when the computer is not booted from that stick, with a system that's x86_64 based?
System Info: Dell Latitude i686 Laptop which has run CentOS 5.5 and Fedora 12,13,14 in the past, and boots from Fedora 14 Live CD transferred to a USB stick. So I know USB booting is possible on this machine, and this stick.
The process of creating the stick:
CentOS 5.5 i386 on a USB stick. Old Dell i686 laptop which has previously run CentOS 5.5 installed from DVD, and has successfully booted from this same USB stick holding transferred Fedora 12,13,14 Live CDs. CentOS 5.5 was installed onto the USB drive directly by the CentOS 5.5 DVD installer (running virtualized in VirtualBox 4.02 on Mac OS X 10.6.5.). No errors or complaints during installation.
For whatever reason, the installer did not do some things correctly. First Grub wasn't working correctly, I got that sorted out and have the Grub+CentOS splash screen, it finds vmlinuz and the initrd, and then I get a kernel panic.
Ext3 was built into the kernel and that's why I'm getting this message. I do not know how the installer would have dropped a kernel or initrd during instalation that that don't contain such a basic thing that obviously comes in linux kernel 2.6.18-89 EL.
I am running an Hp Pavillion dv6000 with the Broadcom card that never seems to work for Linux. I recently talked with my friend who said he found a way to get it work.following his instructions I opened Synaptic and checked the package bmcwl-kernel-source to be installed.I went through the process of it all and it said it had install successfully. I restarted the computer and when I tried to enter my operating system I got this error "Kernel panic - not syncing : VFS : Unable to mount root fs on unknown - block(8,1)" I have previous versions of Linux on my computer so I can still get in to those if need be but I don't know how to undo what I did or why it isn't working for that matter. Does anyone have any ideas as to why I am getting this error and how I can fix it?
I have one machine where I have several versions installed on different partitions. The base partition (/dev/hda1) is Slack 12.1. On a spare partition (/dev/hdc4) I had installed Slackware64-current. Last week I slackpkg upgraded and installed the 2.6.32.2 kernel, and now that partition will not boot. I know that with the new kernels the hd* designation has been removed, and have already redone that fstab (accessing it from a different boot) to reflect the sd*. Here is the slack64 section of my lilo.conf:
Code: # Linux bootable partition config begins image = /other/spare4/boot/vmlinuz
this is what i did i downloaded the latest stable kernel archive from kernel.org and extracted the archive into the download directory (i don't think that matters though) then i downloaded and installed the ncurses archive (needed for menuconfig) then i opened a terminal and navigated to the directory that was extracted from the archive and issues the floowing commands
after the automatic update this morning and restart I could no longer connect to wifi. The router is visible, along with all the others, but when it tries to connect to it, it doesn't succeed.
This is what have been instaled: Commit Log for Fri Jan 8 10:58:42 2010
After performing the periodic update on 2010-05-26 including libc, libc6 and libgtk2.0 my system fails on boot with the following error message:
Code: run-init: /sbin/init: no such file or directory
Kernel panic - not syncing: Attempted to kill init! If I boot from the 10.04 live CD, all partitions on the hard drive are visible, mountable, and pass all file system checks.
After upgrade from MDV 2009.1 to MDV 2010 a bunch of available kernels that can be selected are listed at boot. I think that these are still installed but I really don't need them listed. I would like to get rid of the list of extras. I've had a look at /boot/grub but I can't figure out what.
This morning I did an update on a current F13 system with NVIDIA Graphics card. System gets to a complete white bar across the screen followed by "FEDORA 13" . This all starts blinking and goes no further.
