Kaj pomeni: L 40 40 40 40 ...

Zdravo!

Pojavil se mi je eden problem, ki ga nikakor ne razumem. Za server imam enega starega pentiuma, in na SCSI disku linuxe. To še kar deluje, samo so linuxsi malo zjebani. Zdaj ko pa želim nove nastavit na navaden disk, se pa je stvar zakomplicirala. Če bootam iz CD-ROMa, mi med bootanjem zmrzne in ne naredi nič. Potem sem pa preko mojega računalnika nastavil na disk OS ga priklopil na server in zagnal. Ko bi moralo zagnti sistem na disku, pa mi je začelo pisati tole:

L 40 40 40 40 40 40 ...

Tako mi 40 piše v neskončno!

Če keri ve kaj bi bilo narobe, mi naj prosim pomaga!!

Hvala

Dean: Tle imaš copy/paste iz man lilo:

BOOT ERRORS
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 second 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:

00 no error
01 invalid disk command
02 address mark not found
03 disk write-protected
04 sector not found
06 floppy disk removed
08 DMA overrun
0A bad sector flag
0B bad track flag
20 controller failure
40 seek failure (BIOS)
40 cylinder>1023 (LILO)
99 invalid second stage index sector (LILO)
9A no second stage loader signature (LILO)
AA drive not ready
FF sense operation failed

Error code 40 is generated by the BIOS, or by LILO during the conversion of a linear (24-bit) disk address to a geometric
(C:H:S) address. On older systems which do not support lba32 (32-bit) addressing, this error may also be generated. Errors 99
and 9A usually mean the map file (-m or map=) is not readable, likely because LILO was not re-run after some system change, or
there is a geometry mis-match between what LILO used (lilo -v3 to display) and what is actually being used by the BIOS (one of
the lilo diagnostic disks, available in the source distribution, may be needed to diagnose this problem).

When the second stage loader has received control from the first stage, it prints the letter "L", and when it has initialized
itself, including verifying the "Descriptor Table" - the list of kernels/others to boot - it will print the letter "O", to form
the full word "LILO", in uppercase.

All second stage loader error messages are English text, and try to pinpoint, more or less successfully, the point of failure.