<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2800.1522" name=GENERATOR></HEAD>
<BODY style="MARGIN-TOP: 2px; FONT: 10pt Arial; MARGIN-LEFT: 2px">
<DIV>Yeah, that is what it appeared to happen. </DIV>
<DIV> </DIV>
<DIV>Thanks<BR><BR>>>> freefoote@gmail.com 2:20:44 pm 16/11/2005
>>><BR>Hello...<BR><BR>For what's it's worth, I've had machines do this
before "at random".<BR>For me, it was nothing to do with the disk, just LILO
managed to kill<BR>itself.<BR><BR>To fix it, I used the debian install CD to
boot the system. At the<BR>install CD's LILO prompt, something like "linux
root=/dev/hda1" or<BR>whatever your real root is will do that.<BR><BR>Once
you're booted, log on as root, and then simply reinstall
lilo:<BR>"/sbin/lilo".<BR><BR>(Alternate way of booting system that sometimes
works - use knoppix,<BR>mount the root, chroot to it, and then /sbin/lilo it.
Sometimes this<BR>has other issues, though.)<BR><BR>And then it should
work...<BR><BR>But check your disks anyway, that never hurts. (I say, having
lost one<BR>disk recently and another being a little funny).<BR><BR>Have
fun!<BR><BR>Daniel
Foote.<BR>_______________________________________________<BR>PLUG discussion
list: plug@plug.org.au<BR><A
href="http://www.plug.org.au/mailman/listinfo/plug">http://www.plug.org.au/mailman/listinfo/plug</A><BR>Committee
e-mail: committee@plug.linux.org.au<BR></DIV></BODY></HTML>