[plug] cannot get system to run init on bootup

[Paul Dean]

Hya,

Nothing, just comment it out. This will how ever test your kernel and
modules to make sure it is all built properly.

If this fails, can you get to "single" mode? If so force your kernel to not
load the ext3 module and run your fs as ext2 (edit fstab).

If you can't get to single mode then try a rescue disk, RH 8 & 9 have a very
good and comprehensive tool selection rescue, runs direct from cd.

HTH


Thanks...


Paul.

## Remember: Live your life as if you are on a stage before the whole of
creation.





> -----Original Message-----
> From: Jon Miller [mailto:jlmiller at mmtnetworks.com.au]
> Sent: Monday, 5 May 2003 12:15
> To: plug at plug.linux.org.au
> Subject: RE: [plug] cannot get system to run init on bootup
>
>
> Cannot write anything to the system anywhere.  The furthest
> the system can boot to freeing the memory after loading EXT3
> file system.  The root filesystem has loaded as ro and
> kjournald started.  The next thing to load is init which
> loads the /etc/rc.d/rc.sysinit script. no matter what I try
> it does not load this.
> If I rim out the ram disk (/boot/initrd-2.4.......) what do I
> load then?
>
>
> Jon L. Miller, MCNE, CNS
> Director/Sr Systems Consultant
> MMT Networks Pty Ltd
> http://www.mmtnetworks.com.au
>
> "I don't know the key to success, but the key to failure
>  is trying to please everybody." -Bill Cosby
>
>
>
> >>> paul at thecave.ws 10:33:21 AM 5/05/2003 >>>
> Hya Jon,
>
> Are you in your lilo|grub conf file trying to run initrd ?
> If so comment it out, for some reasons the ramdisk image
> becomes corrupt and
> can't load in memory.
> The error message usually says some thing like "Unable to
> start init, adjust
> your kernel parameters with root= ..."
>
> This has usually fixed most init boot problems.
>
> HTH
>
>
> Thanks...
>
>
> Paul.
>
> ## Remember: Live your life as if you are on a stage before
> the whole of
> creation.
>
>
>
>
>
>
> > -----Original Message-----
> > From: Jon Miller [mailto:jlmiller at mmtnetworks.com.au]
> > Sent: Monday, 5 May 2003 10:34
> > To: plug at plug.linux.org.au
> > Subject: Re: [plug] cannot get system to run init on bootup
> >
> >
> > Tried it this morning and it returned a lot of garbage then
> > the prompt.  This leads me to think that maybe init is
> > corrupt.  Is there a way to install another init file if the
> > file system is ro?
> >
> > Jon
> >
> > Jon L. Miller, MCNE, CNS
> > Director/Sr Systems Consultant
> > MMT Networks Pty Ltd
> > http://www.mmtnetworks.com.au
> >
> > "I don't know the key to success, but the key to failure
> >  is trying to please everybody." -Bill Cosby
> >
> >
> >
> > >>> jhs_bkk at yahoo.com 8:10:44 PM 3/05/2003 >>>
> > On Saturday 03 May 2003 06:39 pm, Jon Miller wrote:
> > > I've tried the linux init=/bin/bash and this works okay. I
> > had a look
> > > around and everything looks okay.  All data looks to be
> intact, etc.
> >
> > >From that bash prompt, what happens if you exec /sbin/init?
> >
> > Just a guess.
> >
> > --
> > GPG: 03EE 9EB8 E500 874A F509  7B95 9B9A 84A1 26E9 4F79
> > http://www.ece.utexas.edu/~jhs/public_key.gpg
> >
> >
> >
>
>
>
>
>
>