LILO Boot Failure Problem

LILO Boot Failure Problem

Post by Edward Siewic » Thu, 18 Jun 1998 04:00:00



Hi.  I was working through some boot-time issues on a server after upgrading
to the 2.0.34 kernel.  After a couple rounds of reboots, I get a*
system at

LILO boot:
Loading linux...

Three dots, that's all.  Same result even with newly dd'd boot.img and
supp.img off of sunsite (rh5.1).  It's apparently a hardware failure of some
sort.  Anybody have any suggestions as to what to start swapping out first?
Memory?  Possibly dead SCSI adapters?  What's going on in the kernel loading
at this point?

Edward Siewick
--
  ESiewick.a.DigiPro com             DigiPro Digital Productions, LLC
  Voice:  703-522-8465                   3100 North Quincy Street
  Fax:    703-522-8417                  Arlington, *ia  22207

 
 
 

LILO Boot Failure Problem

Post by Udo Kno » Fri, 19 Jun 1998 04:00:00


Hi Edward,

I've experienced similar problems with an IDE hd in a notebook (see my posting a
view lines above). So far I've found out the following:

- so far LILO has loaded its second stage boot loader (normally in /boot/boot.b
in your Linux root partition) successfully
- it is now going to load the compressed kernel image
- if you see a newline after the dots, then loading has been completed and LILO
tries to jump into the bootstraper of the kernel

In any case LILO has problems in reading the kernel image from disk. This is
most likely a problem in the way LILO loads the image from disk (e.g. because
LILO does not get along with the hd geometry information it gets from the BIOS).

I suggest to try some of the following:
- play with the compact/linear options in lino.conf
- try LOADLIN
- update your system BIOS (or the BIOS of your host adapter, if you use a SCSI
hd)
- exchange your hd controller

Good luck!

Udo


> Hi.  I was working through some boot-time issues on a server after upgrading
> to the 2.0.34 kernel.  After a couple rounds of reboots, I get a*
> system at

> LILO boot:
> Loading linux...

> Three dots, that's all.  Same result even with newly dd'd boot.img and
> supp.img off of sunsite (rh5.1).  It's apparently a hardware failure of some
> sort.  Anybody have any suggestions as to what to start swapping out first?
> Memory?  Possibly dead SCSI adapters?  What's going on in the kernel loading
> at this point?

> Edward Siewick
> --
>   ESiewick.a.DigiPro com             DigiPro Digital Productions, LLC
>   Voice:  703-522-8465                   3100 North Quincy Street
>   Fax:    703-522-8417                  Arlington, *ia  22207


 
 
 

1. LILO boot failure

Hi all

This is my LILO configuration:
---------------------
boot=/dev/hda
map=/boot/map
install=/boot/boot.b
prompt
timeout=50
message=/boot/message
default=linux

image=/boot/vmlinuz-2.4.2-2
        label=linux
        initrd=/boot/initrd-2.4.2-2.img
        read-only
        root=/dev/hdd5

other=/dev/hda1
        optional
        label=dos
----------------------

Each time I try to run /sbin/lilo I get error (Bios Drive 0x82) and the MBR
of first disk (Windows 98) become corrupted (fdisk /mbr to fix it again).My
only chance to boot up the system, is from the diskette.I got the following
configuration:

IDE 0 Master (Windows 98 ) 10Gbyte
IDE 1 Master (Linux RH 7.1) 3 Gbyte
IDE 1 Slave CD_ROM

Thnx for the help
Any suggestions is appreciated.
Claudio



2. imagemap problems

3. lilo + raid + kernel-2.4.x failure to boot

4. Loops in a here document in csh

5. "LI" boot failure *after* running \sbin\lilo

6. Looking for a graphics program for X

7. Dual boot Debian and XP "boot failure" using XP boot loader

8. Mounting PC filesystems onto a Linux system via NFS

9. Problem while booting linux through LILO or boot-disk

10. Lilo boot problem: doesn't boot dos (invalid media type)

11. Lilo dual boot setup problem; booting win from hdg

12. Win95 boot problems on multi-boot LILO system

13. LILO saved boot file /boot/boot.0301