Hallo alle zusammen,
habe eine neue Boot-Platte in meinen Rechner eingebaut. Eine Quantum Fireball 6,4 MB. Nach der Installation von Sarge soll das System von dieser Platte neu booten. Bei lilo erscheint allerdings nur 09 09 09 09 09 ... usw. Damit wird dann der ganze Bildschirm gefüllt. Mit grub erhalte ich den Fehlercode 15. Die Installation von Sarge klappt allerdings problemlos, keine Fehlermeldungen. Auch als zweite Platte im System funktioniert Sie einwandfrei.
Hat jemand eine Ahnung woran das liegen kann? Vielleicht eine spezielle Bootoption?
grub oder lilo startet nicht von Quantum Platte
- Snoopy
- Beiträge: 4297
- Registriert: 17.11.2003 18:26:56
- Lizenz eigener Beiträge: MIT Lizenz
- Wohnort: Rh.- Pflz.
hi
09 09 09 .... ?
oder 99 99 99 ...
auszug aus
09 09 09 .... ?
oder 99 99 99 ...
auszug aus
Code: Alles auswählen
man lilo
Code: Alles auswählen
[...]
BOOT ERRORS
The boot process takes place in two stages. The first stage loader is a single ector, 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 beween 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.
[...]