> Alex Hunsley wrote:
> >
> > Shaul Karl wrote:
> > >
> > > You might want to enter
> > >
> > > init=/bin/sh
> > >
> > > at the lilo prompt (assuming you have lilo) in order to skip the system
> > > initializations and check that partition manually with the file system
> > > debug/repair tools.
> >
> > Is there some magic way of entering text at the lilo prompt? I've tried
> > typing
> > during the brief pause when it says LILO but no text appears and booting
> > just
> > continues after the pause. Just before it says LILO it says MBR (master boot
> > record I preume), does this have anything to do with it? If I hit a key just
> > after MBR has appeared the text 1FR: appears after it but nothing much
> > else.....
> > thanks
> > alex
>
> Sorry, should have done some reading before posting the above, my bad...
>
> I've read the LILO howto and that says that pressing tab should do the trick,
> or holding down alt or shift when the LILO bit comes up. But neither of these
> action seem to make any difference - the machine continues booting regardless.
>
> thanks
> alex
>
I believe not being able to enter text at the lilo prompt has something
to do with your lilo configuration but I do not know more then that. I
do not know about the MBR thing either.
An alternative strategy might be to boot from a rescue disk and try to
continue from there.
As for the file system debug/repair tools I referred to, I meant e2fsck
and recursively all the other programs that are mentioned in the `See
Also' part of its manpage. If the bad partition is not ext2 then there
should be similar programs for the relevant file system.
When dealing with those programs you might want to compare the output
of a well behaved partition to that of the bad one.
Of course, these programs should be handled with extra care so that you
will not cause damage to a healthy partition.
>
>
> --
> Now playing: nothing at all
>
>
> --
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
>
--
When responding, please quote my entire message.
Shaul Karl <[EMAIL PROTECTED]>
