Re: Panic booting 2.6.30
From: David Ronis
Date: Fri Jun 19 2009 - 16:20:58 EST
Thanks for the reply.
I don't know how to do this with the crashed kernel, but in 220.127.116.11
the expected /dev/hda? entries are there, while /dev/sda? aren't.
On Fri, 2009-06-19 at 12:55 -0700, Justin Mattock wrote:
> On Fri, Jun 19, 2009 at 12:32 PM, Michael Tokarev<mjt@xxxxxxxxxx> wrote:
> > David Ronis wrote:
> >> I've just upgraded an older machine (a P3 running slackware 11.0) from
> >> 18.104.22.168 to 2.6.30; the build was uneventful. However, on reboot (using
> >> lilo) I get:
> >> VSF: Cannot open root device "hda2" or unknown-block(0,0)
> >> Please append a correct root= boot option; here are the available
> >> partions: <====== nothing shows here...
> >> Kernel-Panic - not syncing.
> >> I had rebooted with and without root=hda2. The old kernel is still
> >> usable.
> >> Lilo.conf looks like:
> > Add large-memory option to lilo.conf
> > /mjt
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> > the body of a message to majordomo@xxxxxxxxxxxxxxx
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at http://www.tux.org/lkml/
> check /dev/hda* to see
> if it renamed itself to /dev/sda*
> (noticed this a few months ago with
> 2.6.17(I think) to 2.6.24)
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/