[SOLVED] Kernel panic after hung update

[sidebrnz]

I use yumex to update my desktop every morning. Today's included a new kernel: 3.3.7-1.fc16.i686 to be exact. Late in the process, my computer hung completely. The mouse wouldn't move, the second hand on my desktop clock froze and it didn't respond to anything. Eventually I used the reset button, rebooted to a CLI and used yum-complete-transaction to finish things off. When I rebooted into the new kernel, it failed with this error message:

[ 1.444880] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown block (0,0)

There were several other messages after that, but this looked like the important one. I tried booting a second time just to be sure, with the same results. I'm now booted into the previous kernel, which works just fine.

Checking /boot/grub2/grub.cfg I find that the newest entry doesn't have a line for initrd and that there isn't an initramfs-3.3.7-1.fc16.i686 in /boot. I know that it's possible to boot without one, although doing it causes grubby to fail when it tries to update grub.cfg. I don't have time right now to use dracut to generate one and get it listed, but I will either tonight or tomorrow. In the mean time, does anybody here have any other suggestions? Last, would it be better to use dracut, or have yum remove that kernel then install it again?

[SlowJet]

Yes, boot up in old kerenl and rpm -e kernel-3.3.7-1
then yum install kernel-3.3.7-1

I've had two or three kernes that failed to make an initramfs the first time.
It is a very intense process and some of the code is not up to the job, same as cheap hardware.

kernel-3.3.7-1 is the only choise for now anyway as the several previous ones have problems.
But kernel-3.3.7.n is not offically complete There may be a couple more or a .7.n-1 before it is pushed to updates.
So do the initial updates then install the kernel, then
when the newer 337 or 338 happens, install that one and wait on 34 to get sysnc the same way.
It will be one 34 series for a long time.

SJ

[sidebrnz]

Interesting: rpm claims that kernel-3.3.7-1.fc16 isn't installed, but yum list installed kernel says it is. However, yum remove kernel-3.3.7-1.fc16 found it and is now removing it along with the appropriate kmod-nvidia. Will report back later if needed.

[jims]

Not to be too inquisitive, but if kernel 3.3.7-1 is not 'complete', does anyone have an idea why it might be in the updates? I've just spent three+ hours cleaning up the mess from the failed update and getting it reinstalled.

[george_toolan]

What do you mean?

3.3.7-1.fc16.x86_64 seems to be working as far as I can tell ;-)

[BBQdave]

Originally Posted by george_toolan

What do you mean?

3.3.7-1.fc16.x86_64 seems to be working as far as I can tell ;-)

Not working with my Realtek wireless card, did not test much further, as I rebooted into Kernel Linux 3.3.6.

[sidebrnz]

OK, I finally had time to reboot, and everything came up fine. Color this thread [SOLVED]