LILO saying "L 40 40 40 40 40 40..."

LILO saying "L 40 40 40 40 40 40..."

Post by Cruinn » Fri, 04 Apr 2003 06:30:33



Hello everybody,

I've just installed Debian Woody on an old 486 to set myself a firewall,
and when it starts, lilo only says:

L 40 40 40 40 40 40 40 40 40 40 40 40 .... (...and lots of "40"'s more)

I have to start with a boot disk. The boot disk uses SYSLINUX and works
fine.

I've read somewhere that that error code (40) means that there's a hard
disk geometry problem, but I think that geometry is OK as it is
perfectly auto-detected by the system BIOS (exactly as the label on the
disk says).

The disk is using LBA and LILO is set with the "lba32" flag.

I don't have a /boot partition, but LILO is supposed to work fine with
LBA disk's, isn't it?

What can that error exactly mean?

Thanks a lot.

Cruinne.

 
 
 

LILO saying "L 40 40 40 40 40 40..."

Post by Robert Helle » Fri, 04 Apr 2003 09:00:07


  Cruinne <cruinne_YOU_KNOW_WHAT_mundo-r.com>,
  In a message on Wed, 02 Apr 2003 23:30:33 +0200, wrote :

C> Hello everybody,
C>
C>
C> I've just installed Debian Woody on an old 486 to set myself a firewall,
C> and when it starts, lilo only says:
C>
C> L 40 40 40 40 40 40 40 40 40 40 40 40 .... (...and lots of "40"'s more)
C>
C> I have to start with a boot disk. The boot disk uses SYSLINUX and works
C> fine.
C>
C> I've read somewhere that that error code (40) means that there's a hard
C> disk geometry problem, but I think that geometry is OK as it is
C> perfectly auto-detected by the system BIOS (exactly as the label on the
C> disk says).

Means nothing.

C>
C> The disk is using LBA and LILO is set with the "lba32" flag.
C>
C> I don't have a /boot partition, but LILO is supposed to work fine with
C> LBA disk's, isn't it?

*IF* the BIOS supports it.  An old '486's BIOS won't support lba32...
You need a /boot partition (wholy under the 1024th cylinder).

C>
C> What can that error exactly mean?
C>
C> Thanks a lot.
C>
C> Cruinne.
C>
C>            

 
 
 

LILO saying "L 40 40 40 40 40 40..."

Post by e.. » Fri, 04 Apr 2003 11:19:10




> I've just installed Debian Woody on an old 486 to set myself a firewall,
> and when it starts, lilo only says:

> L 40 40 40 40 40 40 40 40 40 40 40 40 .... (...and lots of "40"'s more)

> I have to start with a boot disk. The boot disk uses SYSLINUX and works
> fine.

> I've read somewhere that that error code (40) means that there's a hard
> disk geometry problem,

'0x40   "Seek failure". This might be a media problem. Try booting again.',
according to /usr/share/doc/lilo-21.4.4/README .  Check out the "linear",
and "lba32" directives.  Make sure everything lilo uses (/boot/map,
/boot/boot.b, /boot/message, maybe others I've forgotten) is available at
boot time.

Quote:> The disk is using LBA and LILO is set with the "lba32" flag.

My BIOS is set to LBA (was 'Auto', but I set it to LBA to test it), and
I have "linear" in /etc/lilo.conf .

Quote:> I don't have a /boot partition, but LILO is supposed to work fine with
> LBA disk's, isn't it?

I don't have one either.

--

LEO:  Now is not a good time to photocopy your *and staple
it to your boss' face, oh no.  Eat a bucket of banana pudding
and wash it down with a gallon of strawberry Quik.  -- Weird Al

 
 
 

LILO saying "L 40 40 40 40 40 40..."

Post by Chris Co » Fri, 04 Apr 2003 14:20:15



> Hello everybody,

> I've just installed Debian Woody on an old 486 to set myself a firewall,
> and when it starts, lilo only says:

> L 40 40 40 40 40 40 40 40 40 40 40 40 .... (...and lots of "40"'s more)

...snip...

> What can that error exactly mean?

Can't tell you "exactly".. but I get this when using Ghost (the normal
PC variety) to copy Linux onto platforms.  Usually just laying down a
new boot record (LILO, never tried grub for this) fixes the problem for
me.

Boot the system up and re-run lilo.  If you're grub based, you might
have a grub-install utility (but I've never tried that).

 
 
 

LILO saying "L 40 40 40 40 40 40..."

Post by Centurio » Fri, 04 Apr 2003 17:26:56


Quote:"Cruinne" wrote...
> Hello everybody,

> I've just installed Debian Woody on an old 486 to set myself a
firewall,
> and when it starts, lilo only says:

> L 40 40 40 40 40 40 40 40 40 40 40 40 .... (...and lots of "40"'s
more)

> What can that error exactly mean?

According to the LILO manual a boot error of "L xx xx xx.." where xx is
some number is due to the drive geometry being wrong or misreported by
the BIOS.

My hardware is an ASUS A7V running two ATA100 drives as masters one on
each of the ATA100 controller channels.  I also have a PCI SCSI
controller for a third hard drive, scanner and CD-RW.  The 2 onboard IDE
controllers are disabled in BIOS.  The BIOS boot order is ATA100/SCSI
then Onboard IDE then Floppy last is network.  So my BIOS reports the
drives in the following order if present:
ATA100-1 Master  0x80
ATA100-1 Slave   0x81
ATA100-2 Master  0x82
ATA100-2 Slave   0x83
SCSI-ID0         0x84
...
etc. incrementing 0x8? by one for each SCSI ID.

For my machine Linux interpreted 0x80 as /dev/hde because it could still
interrogate the standard IDE controllers even though they were disabled
and the BIOS was not reporting any drives present during boot.
(/dev/hda -> /dev/hdd are the onboard IDE controller drives).

I could boot the Debian installtion OK, even Knoppix had no problems.
But as soon as I tried booting using LILO after a normal install, it all
went pear-shaped.  Sound familiar?

OK.  It's easily fixed :-)  Just needs a little info-gathering and
lilo.conf tweaking first.

Your BIOS is not telling LILO the truth about the hard drives.

1. Boot using a rescue floppy or Knoppix etc.

2. Run "hdparm -g /dev/hd?" on each of your hard drives (you need to
know which one is on which controller).  In my case /dev/hdg and
/dev/hde.  /dev/hde is the first device (or 0x80) and /dev/hdg is the
second (or 0x81).

3. Copy the drive geometry down: it is displayed as
cylinders/heads/sectors.

4. Edit lilo.conf and add the following for each drive on your ATA100 co
ntroller:
disk=/dev/hde
     drive=0x80
     cylinders=xxxxxx
     heads=yyyyy
     sectors=zzzzz

(where x/y/z is the c/h/s returned by hdparm).

5. Repeat for other drives.

6. Run "lilo" and that's it :-)

Below is a copy of my lilo.conf file to compare.

HTH

--James

# /etc/lilo.conf - See: `lilo(8)' and `lilo.conf(5)',
# ---------------       `install-mbr(8)', `/usr/share/doc/lilo/',
#                       and `/usr/share/doc/mbr/'.

# +---------------------------------------------------------------+
# |                        !! Reminder !!                         |
# |                                                               |
# | Don't forget to run `lilo' after you make changes to this     |
# | conffile, `/boot/bootmess.txt', or install a new kernel.  The |
# | computer will most likely fail to boot if a kernel-image      |
# | post-install script or you don't remember to run `lilo'.      |
# |                                                               |
# +---------------------------------------------------------------+

# Support LBA for large hard disks.
#
lba32

# Overrides the default mapping between harddisk names and the BIOS'
# harddisk order. Use with caution.
disk=/dev/hde
    bios=0x80
    cylinders=2495
    heads=255
    sectors=63

disk=/dev/hdg
    bios=0x81
    cylinders=58168
    heads=16
    sectors=63

# Specifies the boot device.  This is where Lilo installs its boot
# block.
boot=/dev/hde

# Specifies the device that should be mounted as root. (`/')
#
root=/dev/hdg3

# Installs the specified file as the new boot sector
# You have the choice between: bmp, compat, menu and text
# Look in /boot/ and in lilo.conf(5) manpage for details
#
install=/boot/boot-menu.b

# Specifies the location of the map file
#
map=/boot/map

# Specifies the number of deciseconds (0.1 seconds) LILO should
# wait before booting the first image.
#
delay=20

prompt
timeout=150
vga=6

# Boot up Linux by default.
#
default=Linux

image=/vmlinuz
      label=Linux
      initrd=/boot/initrd.debinstall
      read-only
      append="apm=power-off vga=6"

image=/vmlinuz.old
      label=LinuxOLD
      read-only
      optional

# If you have another OS on this machine to boot, you can uncomment the
# following lines, changing the device name on the `other' line to
# where your other OS' partition is.
other=/dev/hde1
      label="Win2000-Pro"

 
 
 

LILO saying "L 40 40 40 40 40 40..."

Post by Tauno Voipi » Fri, 04 Apr 2003 23:09:44



Quote:> Hello everybody,

> I've just installed Debian Woody on an old 486 to set myself a firewall,
> and when it starts, lilo only says:

> L 40 40 40 40 40 40 40 40 40 40 40 40 .... (...and lots of "40"'s more)

> I have to start with a boot disk. The boot disk uses SYSLINUX and works
> fine.

> I've read somewhere that that error code (40) means that there's a hard
> disk geometry problem, but I think that geometry is OK as it is
> perfectly auto-detected by the system BIOS (exactly as the label on the
> disk says).

> The disk is using LBA and LILO is set with the "lba32" flag.

> I don't have a /boot partition, but LILO is supposed to work fine with
> LBA disk's, isn't it?

> What can that error exactly mean?

It means that the disk was not able to seek to the desired cylinder.

In an old 486, it's very probable that you're having the 1024 cylinder
boundary problem. When booting, LILO (and all other boot loaders) have to
use the BIOS disk drivers to read the disk till the kernel is in and started
up - there are no other disk drivers in the whole system before the kernel
is running. If the BIOS is so old that it has the cylinder limit problem,
all bootable material must be on cylinders 0 to 1023. The Linux file tree is
organised so that the bootable material is in the directory /boot.

Build the disk again, partitioning:

 - at the very beginning 8 to 16 Mbytes primary partition for /boot
 - next, the primary FAT partition for DOS/Windows, if required
 - the rest of disk into an extended partition:
    - other DOS / Windows disks as logical disks
    - Linux swap as a logical disk
    - other Linux partitions as logical disks, including /

If you like to have FAT32 logical disks, change the extended partition type
to 0x0f.

Please note that there must be only one primary Microsoft partition, if any.
Also, there may be only one extended partition to enclose the logical disks.
Other layouts will confuse the Microsoft systems badly.

For a Linux-only setup, just leave the Microsoft partitions out.

HTH

Tauno Voipio

 
 
 

LILO saying "L 40 40 40 40 40 40..."

Post by Edwin Johns » Fri, 04 Apr 2003 23:10:37


On Wed, 02 Apr 2003 23:30:33 +0200, Cruinne


> Hello everybody,

> I've just installed Debian Woody on an old 486 to set myself a firewall,
> and when it starts, lilo only says:

> L 40 40 40 40 40 40 40 40 40 40 40 40 .... (...and lots of "40"'s more)

If you know the hd parameters such as sectors, cylinders, ldz, etc., you
might try setting them in the bios manually, rather than using the auto
feature. Bios is probably not configuring the hd as it needs to be, at least
the problem I had with an older 486 machine. If you can go back to a known,
operating system with same type of drive you might get the figures from the
bios.

...Edwin

--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

~        http://www.shreve.net/~elj       ~
~                                         ~
~ "Once you have flown, you will walk the ~
~ earth with your eyes turned skyward,    ~
~ for there you have been, there you long ~
~ to return." -- da Vinci                 ~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

 
 
 

LILO saying "L 40 40 40 40 40 40..."

Post by Cruinn » Fri, 04 Apr 2003 23:32:46


Ok. Thanks to all.

Finally, it was a problem of the old-486 BIOS not completely supporting
the 1024 cylinder problem, although it told me to have LBA enabled for
that disk...

I made a /boot partition and everything is ok now.

Thank you very much.

Cruinne.


> Hello everybody,

> I've just installed Debian Woody on an old 486 to set myself a firewall,
> and when it starts, lilo only says:

> L 40 40 40 40 40 40 40 40 40 40 40 40 .... (...and lots of "40"'s more)

> I have to start with a boot disk. The boot disk uses SYSLINUX and works
> fine.

> I've read somewhere that that error code (40) means that there's a hard
> disk geometry problem, but I think that geometry is OK as it is
> perfectly auto-detected by the system BIOS (exactly as the label on the
> disk says).

> The disk is using LBA and LILO is set with the "lba32" flag.

> I don't have a /boot partition, but LILO is supposed to work fine with
> LBA disk's, isn't it?

> What can that error exactly mean?

> Thanks a lot.

> Cruinne.

 
 
 

LILO saying "L 40 40 40 40 40 40..."

Post by johninsd at san dot rr dot co » Sat, 05 Apr 2003 02:57:12


Tauno got it exactly right.

"lba32" says use LBA addressing, if available.  If the BIOS does not support
LBA (32-bit) addressing, then you can still have the 1024 cylinder limit.

Re-partitioning is one way to solve the problem, with /boot a separate
partition below cylinder 1024.

The other solution of the problem is to get a BIOS extender, such as EZ-BIOS
(Maxtor MaxBlast), or Disk Manager.  These extenders add the LBA bios support.

--John

On Thu, 03 Apr 2003 16:32:46 +0200, Cruinne


>Ok. Thanks to all.

>Finally, it was a problem of the old-486 BIOS not completely supporting
>the 1024 cylinder problem, although it told me to have LBA enabled for
>that disk...

>I made a /boot partition and everything is ok now.

>Thank you very much.

>Cruinne.


>> Hello everybody,

>> I've just installed Debian Woody on an old 486 to set myself a firewall,
>> and when it starts, lilo only says:

>> L 40 40 40 40 40 40 40 40 40 40 40 40 .... (...and lots of "40"'s more)

>> I have to start with a boot disk. The boot disk uses SYSLINUX and works
>> fine.

>> I've read somewhere that that error code (40) means that there's a hard
>> disk geometry problem, but I think that geometry is OK as it is
>> perfectly auto-detected by the system BIOS (exactly as the label on the
>> disk says).

>> The disk is using LBA and LILO is set with the "lba32" flag.

>> I don't have a /boot partition, but LILO is supposed to work fine with
>> LBA disk's, isn't it?

>> What can that error exactly mean?

>> Thanks a lot.

>> Cruinne.

 
 
 

1. Lilo "L 40 40 40 40 40 40..."

Greetings,

I have set up a Linux From Scratch system on a 1.2Gb Maxtor hard drive. It
works fine on my two Athlon systems, but when I put the drive in my Pentium
100, the system results in "L 40 40 40 40 40 40..." before showing the Lilo
menu.

My Lilo.conf contains the "lba32" entry which should mean this would work,
but it doesn't.

Any ideas?

Regards,
Jon

2. Problem compiling Linux 0.99pl12

3. Lilo spits "L 40 40 40 40"...

4. rsync and permissions

5. Linux LILO Booting L 40 40 40...

6. XDMCP security

7. AMD 386/40 + ULSI 387/40 crashes intermittantly

8. IP aliasing already in the stock kernel?

9. Option "AutoRepeat" "300 40"

10. segmentation fault with 1.3.40, nmbd 1.2.13-1.3.40

11. HP 4MP cannot got "40 ERROR" using serial.