(Please use "man lilo")
The boot process takes place in two stages. The
first stage loader is a single sector, and is
loaded by the BIOS or by the loader in the MBR.
It loads the multi-sector second stage loader,
but is very space limited. When the first stage
loader gets control, it types the letter "L";
when it is ready to transfer control to the sec-
ond stage loader it types the letter "I". If
any error occurs, like a disk read error, it
will put out a hexadecimil error code, and then
it will re-try the operation. All hex error
codes are BIOS return values, except for the
lilo-generated 40, 99 and 9A. A partial list of
error codes follows:
If the kernel is not located, there are several plausible explanations
I.E. Was the md5sum checked prior to burning the downloaded ISO ?
After verification of drive locations (fdisk -l)
if they are correct, try (use vasm) to re-run the lilo loader install
The lilo install option used was not stated (MBR. dual boot, floppy etc)
To confirm, /etc/lilo.conf may read, & if in doubt, be posted
The content of /etc/fstab must match lilo.conf locations
Larry - Pardon me - but I just must ask:
Why is the very first "suspected cause" you suggest, inevitably advised_
it may be "a faulty hard drive" ?
To the best of my knowledge, there have been none ( of numereous incidents
where original undetermined
glitches were found - the hard drive was the culprit.
Alwasy a remote possibility, but one that results in much wasted efforts to
verify - meanwhile, more logical trouble-shooting has been side-tracked.