RE: [Linux-ia64] Re: kernel panic on root mount / EFI cant see

From: Jared Egolf <>
Date: 2001-11-17 08:47:43
Thank-you for your reply, it has given me several more
options to think about.  Unfortunately, I misspoke and I've
only been working with Redhat 7.1, and in the past 7.0.  I
got confused with some of our 32-bit machines where we have
moved to 7.2.  I checked anyway and it wasn't an issue with
ext3 being setup.

As you mentioned below, I'm highly suspicious of the
Microsoft tools getting first crack at the machine.  Did
you have to resort to anything special to remove trace of
them from either the harddrive or the EFI bios setup?  We
are hoping that we won't have to flash the bios to remove
settings, but if it comes to that...

Thank-you for your help,
Jared Egolf

From: "Cook, Steven C" <>
Subject: RE: [Linux-ia64] Re: kernel panic on root mount /
EFI cant see /boot/efi partition!
Date: Fri, 16 Nov 2001 08:57:31 -0800

> From: Bill Nottingham []
> Sent: Thursday, November 15, 2001 19:15
> Jared Egolf ( said: 
> > Using Redhat 7.2 and in the past 7.1, I cannot
> > the /boot/efi partition with such a type definition
> > EFI will recognize the file-system and thus use it for
> > booting purposes.
> Really? It should allow you to set as an EFI system
> or any of the various DOS filesystem types, which all
> in testing here.

We're also having no problems with the EFI partition
configured to type 
(Win32 VFAT).  We have, however, run into problems using
fdisk & format utilities, so in our lab, only use the Linux
fdisk/disk druid utilities to create the partition.
> > Unfortunately, whenever I rebuild a kernel, (currently
> > attempting with 2.4.14, but also tried 2.4.10 and have
> > tested on the BigSur), the kernel panics without being
> > capable of mounting the root partition.  This occurs
> > with the default configuration of the kernel and I
> > the two problems may be linked.
> This sounds like you did not make an initrd that contains
> the proper SCSI adapter module, or (alternatively) did
> compile it in statically. Alternatively, you may not
> have the filesystem type compiled in; did you install
> to an ext3 filesystem?

This sounds like the problem I had when I first installed
7.2 - every 
I built panicked, because I hadn't applied the ext3 patches
to the kernel sources.  As soon as I put that support
in (and 
it in my configuration), the kernel panics went away.  Not
sure if this 
what is plaguing you, but wanted to share that the symptoms
are similar
(although this only happened to me in 7.2, as 7.1 didn't
have the ext3
support built in.

--steve cook--

Do You Yahoo!?
Find the one for you at Yahoo! Personals
Received on Fri Nov 16 13:47:56 2001

This archive was generated by hypermail 2.1.8 : 2005-08-02 09:20:06 EST