Upgrade to 2.4.16 produces "Kernel panic: No init found"

Upgrade to 2.4.16 produces "Kernel panic: No init found"

[Bob Poortinga]

Hello kernel gurus,

I have searched the list archives and google'd myself silly, but I
can't seem to find a solution to my problem.

I am trying to update my 2.4.3 kernel (Mandrake 8.0 distro) to 2.4.16.
I did a 'make oldconfig' with my old .config file and added ext3 kernel
support in addition to ext2.  My root fs is ext2 (as are all my fs).
The new kernel boots but panics when it tries to mount the root fs.
Here is the error:
--------------------------------------------------------------------
Mounting /proc filesystem
Creating root device
Mounting root filesystem
pivotroot: pivot_root(/sysroot,/sysroot/initrd) failed: 2
Freeing unused kernel memory: 216k freed
Kernel panic: No init found.  Try passing init= option to kernel.
--------------------------------------------------------------------

There are no other errors displayed.  I upgraded a number of packages,
but I might have missed something.  My current versions are:

gcc version 2.96 20000731 (Red Hat Linux 7.1 2.96-98)
GNU ld version 2.11.90.0.8 (with BFD 2.11.90.0.8)
glibc 2.2.4-13
insmod version 2.4.6
mkinitrd 3.2.6-1

My system is a dual PII (300 mhz) with 512mb and AIC-7880 scsi.
Kernel options SMP and 686 have been selected.

Does the 2.4.16 kernel require an ext3 root fs if ext3 support is
compiled in?  I don't want to risk upgrading my root fs to ext3
because then my old kernel will not boot.

Any ideas?

-- 
Bob Poortinga
Technology Service Corp.

Re: Upgrade to 2.4.16 produces "Kernel panic: No init found"

[Joy Almacen]

Bob,

I have a similar problem.  My distro is RH7.1 and running on aCompaq Proliant
6000.
The original install boots fine, but is only running on UP not SMP. I grabbed
the
latest kernel from RH site and the upgraded utilities, SysVinit and all.
I even compiled into the kernel the scsi_mod and sd_mod as well as my
SCSI card driver sym53c8xx but to no avail.  It seems that for this
pivot_root
call wont work if you do not have dev and loop compiled into the kernel.
I will recompile the kernel with both selected to find out if this is true.

So far however, I have tried both:

1. Creating an initrd for my kernel version that has SCSI drivers as modules,

2. Compiling the drivers into the kernel with basically the same results, the
kernel panicking either
it can not mount the root file system( which is still ext2) or no init being
found.

See the docs on initrd fro your kernel  as you amy have to change your
lilo.conf
to pass parameters to the kernel thru "append" depending on whether you have
devfs support enabled or not.

I have been trying to fix this for 3 days now and have , like you had said "
google'd myself silly".

I  will let you know if I get any luck booting.

I would also appreciate it if you can let me know if you have a known fix or
at least the issue that's causing
this.

Thanks,

Joy






vda wrote:

> On Monday 10 December 2001 17:41, Bob Poortinga wrote:
> > Hello kernel gurus,
> >
> > I have searched the list archives and google'd myself silly, but I
> > can't seem to find a solution to my problem.
> >
> > I am trying to update my 2.4.3 kernel (Mandrake 8.0 distro) to 2.4.16.
> > I did a 'make oldconfig' with my old .config file and added ext3 kernel
> > support in addition to ext2.  My root fs is ext2 (as are all my fs).
> > The new kernel boots but panics when it tries to mount the root fs.
> > Here is the error:
> > --------------------------------------------------------------------
> > Mounting /proc filesystem
> > Creating root device
> > Mounting root filesystem
> > pivotroot: pivot_root(/sysroot,/sysroot/initrd) failed: 2
> > Freeing unused kernel memory: 216k freed
> > Kernel panic: No init found.  Try passing init= option to kernel.
>
> Using initrd I guess?
> Please describe your boot process.
>
> Initrd support broke between 2.4.10 and 2.4.12, it does not like romfs and
> minix initrds anymore. I have a testcase.
> --
> vda
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

Re: Upgrade to 2.4.16 produces "Kernel panic: No init found"

[vda]

On Monday 10 December 2001 17:41, Bob Poortinga wrote:
> Hello kernel gurus,
>
> I have searched the list archives and google'd myself silly, but I
> can't seem to find a solution to my problem.
>
> I am trying to update my 2.4.3 kernel (Mandrake 8.0 distro) to 2.4.16.
> I did a 'make oldconfig' with my old .config file and added ext3 kernel
> support in addition to ext2.  My root fs is ext2 (as are all my fs).
> The new kernel boots but panics when it tries to mount the root fs.
> Here is the error:
> --------------------------------------------------------------------
> Mounting /proc filesystem
> Creating root device
> Mounting root filesystem
> pivotroot: pivot_root(/sysroot,/sysroot/initrd) failed: 2
> Freeing unused kernel memory: 216k freed
> Kernel panic: No init found.  Try passing init= option to kernel.

Using initrd I guess?
Please describe your boot process.

Initrd support broke between 2.4.10 and 2.4.12, it does not like romfs and 
minix initrds anymore. I have a testcase.
--
vda

Re: Upgrade to 2.4.16 produces "Kernel panic: No init found"

[Joy Almacen]

Tyler,

I do not have it on my lilo.conf file:

Here's my lilo with both the initrd enabled image and the
image with all my SCSI drivers compiled in.

boot=/dev/sda
map=/boot/map
install=/boot/boot.b
prompt
timeout=50
message=/boot/message
linear
default=linux-up

image=/boot/vmlinuz-2.4.2-2smp
        label=linux
        initrd=/boot/initrd-2.4.2-2smp.img
        read-only
        root=/dev/sda1

image=/boot/vmlinuz-2.4.2-2
        label=linux-up
        initrd=/boot/initrd-2.4.2-2.img
        read-only
        root=/dev/sda1

image=/boot/vmlinuz-2.4.9-12smp
        label=2.4.9smp
        initrd=/boot/initrd-2.4.9-12smp.img
        append="root=/dev/ram0 init=/linuxrc rw"

image=/boot/vmlinuz-2.4.9-12-smp-4th
        label=custom
        read-only
        append="root=/dev/sda1"

With the same results: Kernel panic: can not mount root "sda1"


Thanks in advance.

joy


Tyler BIRD wrote:

> Lilo might be configured to load a initial ramdisk
> check for a initrd=xxx line in lilo.conf and remove it.
>
> Then make sure all drivers including scsi, etc are compiled in and reboot
> pivot_root is a routine that changes the root filesystem that is on the ramdisk
> to the newly mounted filesystem from the hardisk
>
> This will definetly fail if the initrd couldn't be loaded din the first place
>
> >>> Joy Almacen <joy@empexis.com> 12/11/01 06:10AM >>>
> Bob,
>
> I have a similar problem.  My distro is RH7.1 and running on aCompaq Proliant
> 6000.
> The original install boots fine, but is only running on UP not SMP. I grabbed
> the
> latest kernel from RH site and the upgraded utilities, SysVinit and all.
> I even compiled into the kernel the scsi_mod and sd_mod as well as my
> SCSI card driver sym53c8xx but to no avail.  It seems that for this
> pivot_root
> call wont work if you do not have dev and loop compiled into the kernel.
> I will recompile the kernel with both selected to find out if this is true.
>
> So far however, I have tried both:
>
> 1. Creating an initrd for my kernel version that has SCSI drivers as modules,
>
> 2. Compiling the drivers into the kernel with basically the same results, the
> kernel panicking either
> it can not mount the root file system( which is still ext2) or no init being
> found.
>
> See the docs on initrd fro your kernel  as you amy have to change your
> lilo.conf
> to pass parameters to the kernel thru "append" depending on whether you have
> devfs support enabled or not.
>
> I have been trying to fix this for 3 days now and have , like you had said "
> google'd myself silly".
>
> I  will let you know if I get any luck booting.
>
> I would also appreciate it if you can let me know if you have a known fix or
> at least the issue that's causing
> this.
>
> Thanks,
>
> Joy
>
> vda wrote:
>
> > On Monday 10 December 2001 17:41, Bob Poortinga wrote:
> > > Hello kernel gurus,
> > >
> > > I have searched the list archives and google'd myself silly, but I
> > > can't seem to find a solution to my problem.
> > >
> > > I am trying to update my 2.4.3 kernel (Mandrake 8.0 distro) to 2.4.16.
> > > I did a 'make oldconfig' with my old .config file and added ext3 kernel
> > > support in addition to ext2.  My root fs is ext2 (as are all my fs).
> > > The new kernel boots but panics when it tries to mount the root fs.
> > > Here is the error:
> > > --------------------------------------------------------------------
> > > Mounting /proc filesystem
> > > Creating root device
> > > Mounting root filesystem
> > > pivotroot: pivot_root(/sysroot,/sysroot/initrd) failed: 2
> > > Freeing unused kernel memory: 216k freed
> > > Kernel panic: No init found.  Try passing init= option to kernel.
> >
> > Using initrd I guess?
> > Please describe your boot process.
> >
> > Initrd support broke between 2.4.10 and 2.4.12, it does not like romfs and
> > minix initrds anymore. I have a testcase.
> > --
> > vda
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at  http://www.tux.org/lkml/
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

Re: Upgrade to 2.4.16 produces "Kernel panic: No init found"

[Tyler BIRD]

Lilo might be configured to load a initial ramdisk
check for a initrd=xxx line in lilo.conf and remove it.

Then make sure all drivers including scsi, etc are compiled in and reboot
pivot_root is a routine that changes the root filesystem that is on the ramdisk
to the newly mounted filesystem from the hardisk

This will definetly fail if the initrd couldn't be loaded din the first place

>>> Joy Almacen <joy@empexis.com> 12/11/01 06:10AM >>>
Bob,

I have a similar problem.  My distro is RH7.1 and running on aCompaq Proliant
6000.
The original install boots fine, but is only running on UP not SMP. I grabbed
the
latest kernel from RH site and the upgraded utilities, SysVinit and all.
I even compiled into the kernel the scsi_mod and sd_mod as well as my
SCSI card driver sym53c8xx but to no avail.  It seems that for this
pivot_root
call wont work if you do not have dev and loop compiled into the kernel.
I will recompile the kernel with both selected to find out if this is true.

So far however, I have tried both:

1. Creating an initrd for my kernel version that has SCSI drivers as modules,

2. Compiling the drivers into the kernel with basically the same results, the
kernel panicking either
it can not mount the root file system( which is still ext2) or no init being
found.

See the docs on initrd fro your kernel  as you amy have to change your
lilo.conf
to pass parameters to the kernel thru "append" depending on whether you have
devfs support enabled or not.

I have been trying to fix this for 3 days now and have , like you had said "
google'd myself silly".

I  will let you know if I get any luck booting.

I would also appreciate it if you can let me know if you have a known fix or
at least the issue that's causing
this.

Thanks,

Joy






vda wrote:

> On Monday 10 December 2001 17:41, Bob Poortinga wrote:
> > Hello kernel gurus,
> >
> > I have searched the list archives and google'd myself silly, but I
> > can't seem to find a solution to my problem.
> >
> > I am trying to update my 2.4.3 kernel (Mandrake 8.0 distro) to 2.4.16.
> > I did a 'make oldconfig' with my old .config file and added ext3 kernel
> > support in addition to ext2.  My root fs is ext2 (as are all my fs).
> > The new kernel boots but panics when it tries to mount the root fs.
> > Here is the error:
> > --------------------------------------------------------------------
> > Mounting /proc filesystem
> > Creating root device
> > Mounting root filesystem
> > pivotroot: pivot_root(/sysroot,/sysroot/initrd) failed: 2
> > Freeing unused kernel memory: 216k freed
> > Kernel panic: No init found.  Try passing init= option to kernel.
>
> Using initrd I guess?
> Please describe your boot process.
>
> Initrd support broke between 2.4.10 and 2.4.12, it does not like romfs and
> minix initrds anymore. I have a testcase.
> --
> vda
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org 
> More majordomo info at  http://vger.kernel.org/majordomo-info.html 
> Please read the FAQ at  http://www.tux.org/lkml/ 




-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org 
More majordomo info at  http://vger.kernel.org/majordomo-info.html 
Please read the FAQ at  http://www.tux.org/lkml/