[plug] cannot get system to run init on bootup
Paul Dean
paul at thecave.ws
Mon May 5 10:33:21 WST 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
>
>
>
More information about the plug
mailing list