Up: Map installer warnings and
Previous: Map installer warnings and
- Boot sector of device_name doesn't have a boot signature
- Boot sector of device_name doesn't have a LILO signature
The sector from which LILO should be uninstalled doesn't appear to be a
LILO boot sector.
- Can't put the boot sector on logical partition number
An attempt has been made to put LILO's boot sector on the current
root file system partition which is on a logical partition. This usually
doesn't have the desired effect, because common MBRs can only boot
primary partitions. This check can be bypassed by explicitly
specifying the boot partition with the -b option or by setting
the configuration variable boot.
- Checksum error
The descriptor table of the map file has an invalid checksum. Refresh
the map file immediately !
- Device 0xnumber: Configured as inaccessible.
There is a disk section entry indicating that the device is
from the BIOS. You should check carefully that all files LILO tries to
access when booting are on the right device.
- Device 0xnumber: Got bad geometry sec/hd/cyl
The device driver for your SCSI controller does not support geometry
detection. You have to specify the geometry explicitly (see section
- Device 0xnumber: Invalid partition table, entry number
The 3D and linear addresses of the first sector of the specified partition
don't correspond. This is typically caused by partitioning a disk with
a program that doesn't align partitions to tracks and later using
PC/MS-DOS or OS/2 on that disk. LILO can attempt to correct the problem,
see page .
- device_name is not a valid partition device
The specified device is either not a device at all, a whole disk, or
a partition on a different disk than the one in whose section its
- device_name is not a whole disk device
Only the geometry of whole disks (e.g. /dev/hda, /dev/sdb,
etc.) can be redefined when using disk sections.
- DISKTAB and DISK are mutually exclusive
You cannot use a disktab file and disk geometry definitions in the
configuration file at the same time. Maybe /etc/disktab was
accidentally used, because that's the default for backward-compatibility.
You should delete /etc/disktab after completing the transition to
- Duplicate entry in partition table
A partition table entry appears twice. The partition table has to be
fixed with fdisk.
- Duplicate geometry definition for device_name
A disk or partition geometry definition entry for the same device appears
twice in the configuration file. Note that you mustn't write a partition
section for the whole disk -- its start sector is always the first
sector of the disk.
- First sector of device doesn't have a valid boot signature
The first sector of the specified device does not appear to be a valid
boot sector. You might have confused the device name.
- geo_comp_addr: Cylinder number beyond end of media (number)
A file block appears to be located beyond the last cylinder of the disk.
This probably indicates an error in the disk geometry specification (see
sections 3.4 and 3.4.3) or a file system
- geo_comp_addr: Cylinder number is too big (number >
Blocks of a file are located beyond the 1024th cylinder of a hard disk.
LILO can't access such files, because the BIOS limits cylinder numbers to
the range 0 1023. Try moving the file to a different place,
partition that is entirely within the first 1024 cylinders of the disk.
- Hole found in map file (location)
The map installer is
confused about the disk organization. Please report this error.
- item doesn't have a valid LILO signature
The specified item has been located, but is not part of LILO.
- item has an invalid stage code (number)
The specified item has probably been corrupted. Try re-building
- item is version number. Expecting versionnumber.
The specified entity is either too old or too new. Make sure all parts
of LILO (map installer, boot loaders and chain loaders) are from the
- Kernel name is too big
The kernel image (without the setup
code) is bigger than 512 kbytes. LILO would overwrite itself when trying
to load such a kernel. Try removing some unused drivers and compiling
the kernel again. With recent (compressed) kernels, the reason for this
error is most likely that the kernel image is damaged or that it
contains trailing ``junk'', e.g. as the result of copying an entire boot
floppy to the hard disk.
- LOCK and FALLBACK are mutually exclusive
Since lock and fallback both change the default command line,
they can't be reasonably used together.
- Map path is not a regular file.
This is probably the result of an attempt to omit writing a map file, e.g.
with -m /dev/null. The -t option should be used to accomplish
- Must specify LOADER for BIOS device number
When booting an operating system from any device than the first hard or
floppy disk, specifying the chain loader (option loader in the
image section) is now mandatory.
- Must specify SECTORS and HEADS together
It is assumed that disks with a ``strange'' number of sectors will also
have a ``strange'' number of heads. Therefore, it's all or nothing.
- No geometry variables allowed if INACCESSIBLE
If a device is configured as inaccessible (see section
its disk section must not contain any geometry variables.
- No image image is defined
The command line specified either with the -R option or with
fallback does not contain the name of a valid image. Note that
optional images which have not been included in the map file are not
considered as valid.
- Partition entry not found
The partition from which an other
operating system should be booted isn't listed in the specified
partition table. This either means that an incorrect partition
table has been specified or that you're trying to boot from a
logical partition. The latter usually doesn't work. You can bypass
this check by omitting the partition table specification (e.g.
omitting the variable table).
- REWRITE-TABLE requires
One of the many restrictions surrounding the rewrite-table
option was not met. Please read section 3.3.3 carefully.
- Sorry, don't know how to handle device number
LILO uses files that are located on a device for which
there is no easy way to determine the disk geometry. Such devices have
to be explicitly described, see section 3.4.
- This LILO is compiled READONLY and doesn't support
If LILO is not allowed to write to the disk at boot time (see section
4.1.5), options like lock and fallback are unavailable.
- Timestamp in boot sector of device differs from date of file
The backup copy of the boot sector does not appear to be an ancestor of
the current boot sector. If you are absolutely sure that the boot sector
is indeed correct, you can bypass this check by using -U instead
- Trying to map files from your RAM disk.
Please check -r option or ROOT environment variable.
Most likely, you or some installation script is trying to invoke
LILO in a way that some of the files is has to access reside on the
RAM disk. Normally, the ROOT environment variable should be set
to the mount point of the effective root device if installing
LILO with a different root directory. See also sections 3.1.2
- VGA mode presetting is not supported by your kernel.
Your kernel sources appear to be very old ('93 ?). LILO may work on
your system if you remove the vga option.
- write item: error_reason
The disk is probably full or mounted read-only.
Up: Map installer warnings and
Previous: Map installer warnings and
Sun Jun 9 03:44:19 EDT 1996