[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: How do you repair a bad LILO?



Thanks, Shaya. I did that and that's when it told me that lilo.conf didn't
exist. At this point I suspected that the absence of lilo.conf might
indicated that the problems with my filesystem were more severe than I
thought so I did a reinstall ... however, is there a way to run without
lilo.conf being present? I mean, create a new one?

Thanks!

Jen

----- Original Message -----
From: "Shaya Potter" <spotter@cs.columbia.edu>
To: "jennyw" <jennyw@dangerousideas.com>
Cc: "Debian User List" <debian-user@lists.debian.org>
Sent: Sunday, November 25, 2001 9:37 PM
Subject: Re: How do you repair a bad LILO?


> boot off the cd like that they told you (or floppy)
>
> then login as root
>
> run /sbin/lilo by hand, that should reinstall lilo for you.
>
> shaya
>
> On Mon, 2001-11-26 at 00:25, jennyw wrote:
> > I reinstalled Debian 2.2. After installing the base system, it rebooted
fine
> > to finish the rest of the install. I logged in and used it for a bit
then
> > decided to reboot again. This time it hung after showing "LIL-". I asked
on
> > #debian on IRC and folks said this meant I had a bad LILO MBR. Someone
> > suggested that I try typing "rescue root=/dev/hda1" at the boot:
prompt. I
> > tried this booting off of the install CD and it ended up loading my
Debian
> > install just fine, but it doesn't seem to fix the problem when I reboot.
> >
> > I then booted off a boot floppy and tried to run lilo. It said that
there
> > was no lilo.conf file. I did a search on the filesystem for lilo.conf
and
> > there is no file anywhere ... At this point I'm reinstalling (again!),
but
> > I'd like to know how to fix this problem for the future.
> >
> > Thanks!
> >
> > Jen
> >
> >
> >
> > --
> > To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
> > with a subject of "unsubscribe". Trouble? Contact
listmaster@lists.debian.org
> --
> spotter@{cs.columbia.edu,yucs.org}
> http://yucs.org/~spotter/
>
>
>
>



Reply to: