- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- LILO hangs at prompt with L
Operating System - Linux
1820475
Members
2942
Online
109624
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-09-2001 12:46 AM
тАО07-09-2001 12:46 AM
LILO hangs at prompt with L
Hello,
Having succesfully installed Redhat 6.2, I rebooted the system and logged in without any problems.
At the next reboot, the LILO prompt showed an "L" and the system got no further.
I did not edit the lilo.conf file, nor did I run lilo -v -v, etc.
Normally, if there is a hardware error, then LILO produces the error message L=, where xx is a number refering to a specific hardware error. However, I only see the letter L.
Any ideas?
Peter Bilitch
Having succesfully installed Redhat 6.2, I rebooted the system and logged in without any problems.
At the next reboot, the LILO prompt showed an "L" and the system got no further.
I did not edit the lilo.conf file, nor did I run lilo -v -v, etc.
Normally, if there is a hardware error, then LILO produces the error message L=
Any ideas?
Peter Bilitch
Always on, always connected.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-09-2001 03:19 AM
тАО07-09-2001 03:19 AM
Re: LILO hangs at prompt with L
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-12-2001 09:49 AM
тАО09-12-2001 09:49 AM
Re: LILO hangs at prompt with L
The LILO howto has this information for the error codes.
Output Problem
(nothing) No part of LILO has been loaded. LILO either isn't installed or the partition on which its boot sector is located isn't active.
L The first stage boot loader has been loaded and started, but it can't load the second stage boot loader. The two-digit error codes indicate the type of problem. (See also section ``Disk error codes''.) This condition usually indicates a media failure or a geometry mismatch (e.g. bad disk parameters).
LI The first stage boot loader was able to load the second stage boot loader, but has failed to execute it. This can either be caused by a geometry mismatch or by moving /boot/boot.b without running the map installer.
LIL The second stage boot loader has been started, but it can't load the descriptor table from the map file. This is typically caused by a media failure or by a geometry mismatch.
LIL? The second stage boot loader has been loaded at an incorrect address. This is typically caused by a subtle geometry mismatch or by moving /boot/boot.b without running the map installer.
LIL- The descriptor table is corrupt. This can either be caused by a geometry mismatch or by moving /boot/map without running the map installer.
LILO All parts of LILO have been successfully loaded.
It could be bad disk parameters or a media failure all together.
Output Problem
(nothing) No part of LILO has been loaded. LILO either isn't installed or the partition on which its boot sector is located isn't active.
L The first stage boot loader has been loaded and started, but it can't load the second stage boot loader. The two-digit error codes indicate the type of problem. (See also section ``Disk error codes''.) This condition usually indicates a media failure or a geometry mismatch (e.g. bad disk parameters).
LI The first stage boot loader was able to load the second stage boot loader, but has failed to execute it. This can either be caused by a geometry mismatch or by moving /boot/boot.b without running the map installer.
LIL The second stage boot loader has been started, but it can't load the descriptor table from the map file. This is typically caused by a media failure or by a geometry mismatch.
LIL? The second stage boot loader has been loaded at an incorrect address. This is typically caused by a subtle geometry mismatch or by moving /boot/boot.b without running the map installer.
LIL- The descriptor table is corrupt. This can either be caused by a geometry mismatch or by moving /boot/map without running the map installer.
LILO All parts of LILO have been successfully loaded.
It could be bad disk parameters or a media failure all together.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-12-2001 10:55 AM
тАО09-12-2001 10:55 AM
Re: LILO hangs at prompt with L
Here is some more information as to how to fix the geometry mismatch and so forth.
If incorrect information is returned, booting may fail in several ways, typically with a partial "LILO" banner message. In this document, that is called a "geometry mismatch".
A geometry mismatch can be caused by the system BIOS, the IDE controller, or even just how the drive is configured.
Try booting into linux and running the following command:
/sbin/lilo -v -v
Then compare the output with the error messages in the LILO readme file:
/usr/share/doc/lilo-version-number/README
Depending on your system configuration, the problem may be correctable with using the "linear," "lba32," or "compact" options in /etc/lilo.conf. It is also possible that running LILO outside of the installer may solve the problem, since a running system is more robust than the installer.
Here is a line from /usr/share/doc/lilo-version-number/README
Attempt to set the LINEAR configuration variable or the -l command-line option. If this doesn't help, the entire disk geometry has to be specified explicitly.
This file is quite long so you may want to read it for yourself, but at least this should get you going on figuring out your problem.
If incorrect information is returned, booting may fail in several ways, typically with a partial "LILO" banner message. In this document, that is called a "geometry mismatch".
A geometry mismatch can be caused by the system BIOS, the IDE controller, or even just how the drive is configured.
Try booting into linux and running the following command:
/sbin/lilo -v -v
Then compare the output with the error messages in the LILO readme file:
/usr/share/doc/lilo-version-number/README
Depending on your system configuration, the problem may be correctable with using the "linear," "lba32," or "compact" options in /etc/lilo.conf. It is also possible that running LILO outside of the installer may solve the problem, since a running system is more robust than the installer.
Here is a line from /usr/share/doc/lilo-version-number/README
Attempt to set the LINEAR configuration variable or the -l command-line option. If this doesn't help, the entire disk geometry has to be specified explicitly.
This file is quite long so you may want to read it for yourself, but at least this should get you going on figuring out your problem.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Learn About
News and Events
Support
© Copyright 2025 Hewlett Packard Enterprise Development LP