Kurt Telep on Mon, 30 Aug 1999 00:08:22 -0400 (EDT)


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

Re: [Plug] boot problem: LIL- (SuSE; + NT; possibly from Anti-Virus)


In General, anytime that you're boot sector becomes corrupted in any way, LILO
will
fail to load,  there are howtos that explain what it means when you only get so
much of LILO

The best way to remedy this is to boot from your emergency disk (We all have
one, right?)
and rerun lilo to recreate it's presence in teh MBR.

Later-
Kurt Telep
kt25@drexel.edu




Nick R wrote:

> I had a sort of similar problem. I had to transfer some files from my
> computer to somebody else's, so I popped out my HD and put it in their box.
> It happened a while ago, but I think the LIL was caused by setting the HD I
> popped in to master and booting up. There was no Linux partition because
> that resided on a different HD, so maybe it has to do w/ incorrect entries
> that refer to non-existent partitions. Also, NAV tends to screw around w/
> the MBR. It always used to say that the MBR had been changed and asked about
> fixing it. I always said no.
>
> >From: druid@netreach.net
> >Reply-To: plug@lists.nothinbut.net
> >To: plug@lists.nothinbut.net
> >Subject: [Plug] boot problem: LIL-  (SuSE; + NT; possibly from Anti-Virus)
> >Date: Sun, 29 Aug 1999 21:15:04 -0400
> >
> >
> >I have NT and SuSE 5.3 Linux installed on the same machine
> >(one harddrive).  It boots using the NT loader, and has
> >worked routinely without the least problem.
> >
> >Recently I wanted to boot my machine in Linux, and what
> >comes up is "LIL-" and then there's no response.
> >I haven't explicitly changed anything with the boot mechanism.
> >I believe the problem first arose when I began using Norton
> >Anti-Virus on the NT side (I have since disabled the NAV),
> >though NAV has never given any 'virus alerts'.
> >
> >LILO is installed in my Linux root partition /dev/hda5,
> >and a copy of its boot sector is copied (using 'dd') where
> >NT can find it (in c:\bootsect.lnx).
> >
> >Regarding diagnosis of LILO, SuSE handbook says:
> >   'LIL-'  Data in the map file is invalid.  This can be due
> >         to a faulty disk geometry or to moving /boot/boot.b
> >         without reinstalling LILO.
> >
> >Effort thusfar to repair:
> >  1) I boot Linux from my floppy (meanwhile also for
> >       general purposes);
> >  2) re-edited and verified /etc/lilo.conf
> >  3) run /sbin/lilo  (as root)
> >  4) recopied linux bootsector over to NT as c:\bootsect.lnx
> >      (even though it's irrevelant to the problem, I believe).
> >  5) then I try to reboot Linux (without floppy, of course)
> >       but get same result "LIL-"
> >
> >I've checked various archives near endlessly for clues.
> >One person wrote debian-user@lists.debian.org (4/97) about
> >'LIL-', and the reply was:
> >
> >  "This sounds as if you need to reboot with a floppy, then
> >   run lilo as root. The typical cause of this problem is
> >   rebooting a machine after changing the kernel image but
> >   before re-running lilo. It also happens regularly to one
> >   of our student lab machines, which has a dodgy hard drive."
> >
> >In my case, it sounds like /boot/boot.b may be messed up,
> >but I'm not even sure what all this is (ie, which components
> >are freshly remade when I re-run lilo, and such stuff).
> >
> >Thanks ...
> >
> >druid@netreach.net
> >
> >
> >
> >_______________________________________________
> >Plug maillist  -  Plug@lists.nothinbut.net
> >http://lists.nothinbut.net/mail/listinfo/plug
>
> ______________________________________________________
> Get Your Private, Free Email at http://www.hotmail.com
>
> _______________________________________________
> Plug maillist  -  Plug@lists.nothinbut.net
> http://lists.nothinbut.net/mail/listinfo/plug


_______________________________________________
Plug maillist  -  Plug@lists.nothinbut.net
http://lists.nothinbut.net/mail/listinfo/plug