Hoary Kernel Upgrade Resulted to Kernel Panic on Boot

Jojo Paderes jojo.paderes at gmail.com
Mon Aug 22 02:11:10 UTC 2005


Just to make my system work (without the hassle of reconfiguring or
upgrading the whole system), I copied the following system files under
/boot from another Ubuntu Hoary workstation:

config-2.6.10-5-386
initrd.img-2.6.10-5-386
System.map-2.6.10-5-386
vmlinuz-2.6.10-5-386

Make sure the following sysmlinks under / are pointed to the right
/boot system files:

initrd.img -> boot/initrd.img-2.6.10-5-386
vmlinuz -> boot/vmlinuz-2.6.10-5-386


On 8/22/05, volvoguy <volvoguy at gmail.com> wrote:
> On 8/21/05, Jojo Paderes <jojo.paderes at gmail.com> wrote:
> 
> > For Hoary users who are about to upgrade their kernel image, BEWARE of
> > this (unconfirmed) bug:
> >
> > http://bugzilla.ubuntu.com/show_bug.cgi?id=13155
> >
> > I'm encountering this annoying error (again) after upgrading my kernel
> > image just last Aug 20, 2005 using the Hoary repository:
> >
> > Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
> >
> > Any tips on how to solve this?
> 
> Oh, I'LL confirm it. :o) So far it appears to me that everything to do
> with this last kernel upgrade was botched from the start. I don't get
> a kernel panic - just "unknown filesystem" or "can't mount filesystem"
> or something along those lines. In my case Ubuntu is on an IDE drive
> with a Reiser FS (although there IS a SATA drive in the machine, it's
> not used with Linux at all).
> 
> I mentioned it in the thread that I started, but since you're
> acknowledging this issue and have a bug filed, I'll mention it again
> here. It's been my experience in the past that whenever a kernel was
> upgraded via Synaptic, that the old kernel was left in place (and left
> in grub's menu.lst) for this very issue - if the new kernel didn't
> work, you could aways boot the old one. For some reason this upgrade
> replaced my older kernel instead of just adding to the list.
> 
> So ironically I have a dead Hoary (aka stable) system that hasn't been
> powered on in several days because of the new kernel, a laptop that
> won't accept any version of Hoary or Breezy, but an ancient desktop
> machine running an up-to-date Breezy is the only working box I have at
> the moment. :o)
> 
> As an attempt to fix my main machine, I *just* booted up with the
> Hoary live cd and hope to copy over an older kernel to see if that
> changes anything. One question I had though - If Grub is saying that
> it can't even access the filesystem on the drive, is it the kernel's
> fault or Grub's? Seems to me that if the drive can't be mounted or
> read, that the kernel isn't even in the equation yet. Comments?
> 
> 
> 
> --
> Aaron
> 
> Ubuntu SVG Artwork - www.volvoguy.net/ubuntu
> -------------------------------------------------------------------------------
> Art, like morality, consists of drawing the line somewhere. ~ G.K. Chesterton
> 
> --
> ubuntu-users mailing list
> ubuntu-users at lists.ubuntu.com
> http://lists.ubuntu.com/mailman/listinfo/ubuntu-users
> 


-- 
http://jojopaderes.blogspot.com

"In preparing for battle I have always found that plans are useless,
but planning is indispensable." - Eisenhower




More information about the ubuntu-users mailing list