LILO Boot Problems

LILO Boot Problems

Post by Daniel Guellm » Wed, 12 Jun 2002 16:16:35



Hi @ll,

I have a tricky problem with the lilo boot configuration. First the
enviroment:
Compaq Professional WKS 5000
- 2GB SCSI HDD (ID 0)
- Yamaha CDWriter (ID 5)
- additionally a Promise Fasttrak 66 with two 60GB IDE HDD
- i use the fasttrak controller only as IDE Controller not to RAID the
drives

I installed the SuSE Linux 8.0 Pro with a root-partition on the SCSI
Drive. The disk connected to the promise controller used as hda and
hdc. I force the Lilo-bootloader to use the SCSI-Disc as 0x81 (see
lilo.conf). But what ever I do it stops at "LIL".

Any suggestions?

Regards Daniel!

For better understanding here some important logs:

lilo.log:

LILO version 22.1, Copyright (C) 1992-1998 Werner Almesberger
Development beyond version 21 Copyright (C) 1999-2001 John Coffman
Released 31-Oct-2001 and compiled at 20:50:13 on Mar 25 2002.
MAX_IMAGES = 27

raid_setup returns offset = 00000000
Reading boot sector from /dev/sda
Warning: /dev/sda is not on the first disk
Merging with /boot/boot.b
Device 0x0802: BIOS drive 0x81, 65 heads, 1019 cylinders,
               62 sectors. Partition offset: 44330 sectors.
Secondary loader: 18 sectors.
Device 0x0802: BIOS drive 0x81, 65 heads, 1019 cylinders,
               62 sectors. Partition offset: 44330 sectors.
Mapping message file /boot/message
Device 0x0802: BIOS drive 0x81, 65 heads, 1019 cylinders,
               62 sectors. Partition offset: 44330 sectors.
Message: 161 sectors.
Boot image: /boot/vmlinuz
Device 0x0802: BIOS drive 0x81, 65 heads, 1019 cylinders,
               62 sectors. Partition offset: 44330 sectors.
Setup length is 10 sectors.
Mapped 1887 sectors.
Mapping RAM disk /boot/initrd
Device 0x0802: BIOS drive 0x81, 65 heads, 1019 cylinders,
               62 sectors. Partition offset: 44330 sectors.
RAM disk: 1135 sectors.
Added linux *
    <dev=0xe1,hd=10,cyl=41,sct=148>
    "ro root=802"

Boot image: /boot/vmlinuz.suse
Device 0x0802: BIOS drive 0x81, 65 heads, 1019 cylinders,
               62 sectors. Partition offset: 44330 sectors.
Setup length is 10 sectors.
Mapped 1887 sectors.
Mapping RAM disk /boot/initrd.suse
Device 0x0802: BIOS drive 0x81, 65 heads, 1019 cylinders,
               62 sectors. Partition offset: 44330 sectors.
RAM disk: 1134 sectors.
Added failsafe
    <dev=0xe1,hd=10,cyl=41,sct=181>
    "ro root=802 ide=nodma apm=off acpi=off"

Boot image: /boot/memtest.bin
Device 0x0802: BIOS drive 0x81, 65 heads, 1019 cylinders,
               62 sectors. Partition offset: 44330 sectors.
Setup length is 4 sectors.
Mapped 151 sectors.
Added memtest86
    <dev=0xe1,hd=10,cyl=42,sct=22>
    "ro"

/boot/boot.0800 exists - no backup copy made.
Map file size: 40448 bytes.
Writing boot sector.
---------------------------------------------------------------

Output of dmesg:

reiserfs: checking transaction log (device 08:02) ...
Using r5 hash to sort names
ReiserFS version 3.6.25
FAT: bogus logical sector size 0
cramfs: wrong magic
reiserfs: checking transaction log (device 08:02) ...
Using r5 hash to sort names
ReiserFS version 3.6.25
VFS: Mounted root (reiserfs filesystem) readonly.
change_root: old root has d_count=14
Trying to unmount old root ... okay
Freeing unused kernel memory: 120k freed
md: Autodetecting RAID arrays.
 [events: 0000001e]
 [events: 0000001e]
 [events: 0000001e]
 [events: 0000001e]
md: autorun ...
md: considering hda1 ...
md:  adding hda1 ...
md:  adding hdc1 ...
md: created md0
md: bind<hdc1,1>
md: bind<hda1,2>
md: running: <hda1><hdc1>
md: hda1's event counter: 0000001e
md: hdc1's event counter: 0000001e
md: RAID level 1 does not need chunksize! Continuing anyway.
md: raid1 personality registered as nr 3
md0: max total readahead window set to 124k
md0: 1 data-disks, max readahead per data-disk: 124k
raid1: device hda1 operational as mirror 0
raid1: device hdc1 operational as mirror 1
raid1: raid set md0 active with 2 out of 2 mirrors
md: updating md0 RAID superblock on device
md: hda1 [events: 0000001f]<6>(write) hda1's sb offset: 20972736
md: hdc1 [events: 0000001f]<6>(write) hdc1's sb offset: 20972736
md: considering hda2 ...
md:  adding hda2 ...
md:  adding hdc2 ...
md: created md1
md: bind<hdc2,1>
md: bind<hda2,2>
md: running: <hda2><hdc2>
md: hda2's event counter: 0000001e
md: hdc2's event counter: 0000001e
md: raid0 personality registered as nr 2
md1: max total readahead window set to 496k
md1: 2 data-disks, max readahead per data-disk: 248k
raid0: looking at hda2
raid0:   comparing hda2(39053888) with hda2(39053888)
raid0:   END
raid0:   ==> UNIQUE
raid0: 1 zones
raid0: looking at hdc2
raid0:   comparing hdc2(39053888) with hda2(39053888)
raid0:   EQUAL
raid0: FINAL 1 zones
raid0: zone 0
raid0: checking hda2 ... contained as device 0
  (39053888) is smallest!.
raid0: checking hdc2 ... contained as device 1
raid0: zone->nb_dev: 2, size: 78107776
raid0: current zone offset: 39053888
raid0: done.
raid0 : md_size is 78107776 blocks.
raid0 : conf->smallest->size is 78107776 blocks.
raid0 : nb_zone is 1.
raid0 : Allocating 8 bytes for hash.
md: updating md1 RAID superblock on device
md: hda2 [events: 0000001f]<6>(write) hda2's sb offset: 39053888
md: hdc2 [events: 0000001f]<6>(write) hdc2's sb offset: 39053888
md: ... autorun DONE.
Adding Swap: 217612k swap-space (priority 42)
attempt to access beyond end of device
08:01: rw=0, want=131076, limit=22134
reiserfs_read_super: unable to read bitmap
isapnp: Scanning for PnP cards...
isapnp: Card 'ESS ES1868 Plug and Play AudioDrive'
isapnp: 1 Plug & Play card detected total
VFS: Disk change detected on device fd(2,0)

------------------------------------------------

content of /var/log/boot.msg

Inspecting /boot/System.map-2.4.18-4GB
Loaded 12771 symbols from /boot/System.map-2.4.18-4GB.
Symbols match kernel version 2.4.18.
Loaded 91 symbols from 9 modules.
klogd 1.4.1, log source = ksyslog started.
<4>Linux version 2.4.18-4GB (r...@Pentium.suse.de) (gcc version 2.95.3
20010315 (SuSE)) #1 Wed Mar 27 13:57:05 UTC 2002
<6>BIOS-provided physical RAM map:
<4> BIOS-e801: 0000000000000000 - 000000000009f000 (usable)
<4> BIOS-e801: 0000000000100000 - 0000000008000000 (usable)
<4>Scanning bios EBDA for MXT signature
<4>On node 0 totalpages: 32768
<4>zone(0): 4096 pages.
<4>zone(1): 28672 pages.
<4>zone(2): 0 pages.
<4>Building zonelist for node : 0
<4>Kernel command line: initrd=initrd ramdisk_size=65536 manual=1
BOOT_IMAGE=linux SuSE=,1102200020,2236A5FC., vga=0x0311 expert=0
<6>Initializing CPU#0
<4>Detected 199.441 MHz processor.
<4>Console: colour dummy device 80x25
<4>Calibrating delay loop... 398.13 BogoMIPS
<4>Memory: 125488k/131072k available (1389k kernel code, 5196k
reserved, 406k data, 120k init, 0k highmem)
<4>Dentry-cache hash table entries: 16384 (order: 5, 131072 bytes)
<4>Inode-cache hash table entries: 8192 (order: 4, 65536 bytes)
<4>Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
<4>Buffer-cache hash table entries: 8192 (order: 3, 32768 bytes)
<4>Page-cache hash table entries: 32768 (order: 5, 131072 bytes)
<7>CPU: Before vendor init, caps: 0000fbff 00000000 00000000, vendor =
0
<6>CPU: L1 I cache: 8K, L1 D cache: 8K
<6>CPU: L2 cache: 256K
<7>CPU: After vendor init, caps: 0000fbff 00000000 00000000 00000000
<6>Intel machine check architecture supported.
<6>Intel machine check reporting enabled on CPU#0.
<7>CPU:     After generic, caps: 0000fbff 00000000 00000000 00000000
<7>CPU:             Common caps: 0000fbff 00000000 00000000 00000000
<4>CPU: Intel Pentium Pro stepping 09
<6>Checking 'hlt' instruction... OK.
<4>POSIX conformance testing by UNIFIX
<4>mtrr: v1.40 (20010327) Richard Gooch (rgo...@atnf.csiro.au)
<4>mtrr: detected mtrr type: Intel
<4>PCI: PCI BIOS revision 2.10 entry at 0xe07c4, last bus=1
<4>PCI: Using configuration type 1
<4>PCI: Probing PCI hardware
<3>Unknown bridge resource 2: assuming transparent
<6>Limiting direct PCI/PCI transfers.
<6>Linux NET4.0 for Linux 2.4
<6>Based upon Swansea University Computer Society NET3.039
<4>Initializing RT netlink socket
<6>apm: BIOS version 1.1 Flags 0x02 (Driver version 1.16)
<4>mxt_scan_bios: enter
<4>Starting kswapd
<4>kinoded started
<5>VFS: Diskquotas version dquot_6.5.0 initialized
<5>ACPI: APM is already active, exiting
<6>vesafb: framebuffer at 0x40800000, mapped to 0xc880d000, size 2048k
<6>vesafb: mode is 640x480x16, linelength=1280, pages=2
<6>vesafb: protected mode interface info at c000:7b53
<6>vesafb: scrolling: redraw
<6>vesafb: directcolor: size=0:5:6:5, shift=0:11:5:0
<6>Looking for splash picture..... no good signature found.
<4>Console: switching to colour frame buffer device 80x30
<6>fb0: VESA VGA frame buffer device
<6>Detected PS/2 Mouse Port.
<4>pty: 256 Unix98 ptys configured
<6>Serial driver version 5.05c (2001-07-08) with HUB-6 MANY_PORTS
MULTIPORT SHARE_IRQ SERIAL_PCI SERIAL_ACPI enabled
<6>ttyS00 at 0x03f8 (irq = 4) is a 16550A
<6>Real Time Clock Driver v1.10e
<4>block: 128 slots per queue, batch=32
<4>RAMDISK driver initialized: 16 RAM disks of 65536K size 1024
blocksize
<6>Uniform Multi-Platform E-IDE driver Revision: 6.31
<4>ide: Assuming 33MHz system bus speed for PIO modes; override with
idebus=xx
<4>PDC20262: IDE controller on PCI bus 00 dev 48
<4>PDC20262: chipset revision 1
<4>PDC20262: not 100%% native mode: will probe irqs later
<4>PDC20262: (U)DMA Burst Bit ENABLED Primary MASTER Mode Secondary
MASTER Mode.
<4>    ide0: BM-DMA at 0x2040-0x2047, BIOS settings: hda:pio, hdb:pio
<4>    ide1: BM-DMA at 0x2048-0x204f, BIOS settings: hdc:pio, hdd:pio
<4>PCI_IDE: unknown IDE controller on PCI bus 00 device a1, VID=0e11,
DID=ae33
<3>PCI: Device 00:14.1 not available because of resource collisions
<4>PCI_IDE: (ide_setup_pci_device:) Could not enable device.
<4>hda: Maxtor 4W060H4, ATA DISK drive
<4>hdc: Maxtor 96147U8, ATA DISK drive
<4>ide0 at 0x2018-0x201f,0x202a on irq 3
<4>ide1 at 0x2020-0x2027,0x202e on irq 3
<4>blk: queue c031ece4, I/O limit 4095Mb (mask 0xffffffff)
<4>hda: failed write cache flush, disabling ordered write support
<6>hda: 120103200 sectors (61493 ...

read more »

 
 
 

LILO Boot Problems

Post by Eric Moor » Wed, 12 Jun 2002 18:48:14


Quote:> I have a tricky problem with the lilo boot configuration. First the
> enviroment:
> Compaq Professional WKS 5000
> - 2GB SCSI HDD (ID 0)
> - Yamaha CDWriter (ID 5)
> - additionally a Promise Fasttrak 66 with two 60GB IDE HDD - i use the
> fasttrak controller only as IDE Controller not to RAID the drives

> I installed the SuSE Linux 8.0 Pro with a root-partition on the SCSI
> Drive. The disk connected to the promise controller used as hda and hdc.
> I force the Lilo-bootloader to use the SCSI-Disc as 0x81 (see
> lilo.conf). But what ever I do it stops at "LIL".

You boot from sda?
Then force the SCSI disc as 0x80 instead of 0x81.

You have a lilo.conf in that logging-mess somewhere??
<stripped information overkill>

Eric

 
 
 

LILO Boot Problems

Post by johninsd at san dot rr dot co » Thu, 13 Jun 2002 01:02:33




>I have a tricky problem with the lilo boot configuration. First the
>enviroment:
>Compaq Professional WKS 5000
>- 2GB SCSI HDD (ID 0)
>- Yamaha CDWriter (ID 5)
>- additionally a Promise Fasttrak 66 with two 60GB IDE HDD
>- i use the fasttrak controller only as IDE Controller not to RAID the
>drives

>I installed the SuSE Linux 8.0 Pro with a root-partition on the SCSI
>Drive. The disk connected to the promise controller used as hda and
>hdc. I force the Lilo-bootloader to use the SCSI-Disc as 0x81

Are you sure what the device codes actually are?

The bios assigns the device codes; you just have to tell LILO what they are:

disk = /dev/hda    bios = 0x80
disk = /dev/hdc    bios = 0x8?
disk = /dev/sda    bios = 0x8?

The lilo source distribution contains two diagnostic disks:

make floppy1
make floppy2

The shorter diagnostic on floppy1 will nail down the actual device codes.

--John

LILO source code at http://brun.dyndns.org/pub/linux/lilo

 
 
 

LILO Boot Problems

Post by nob.. » Thu, 13 Jun 2002 02:21:15


It was my impression (experience) that most PC BIOS will always boot of first
IDE drive when one is present, so you must put LILO on the MBR of the first
IDE disk, even if you want to boot off the SCSI disk only. I've seen some BIOS
have option to work around this, but I've yet to see it actually work. Maybe
this is something you are aware of and newer PC BIOS / versions of LILO can
get around this?

On Tue, 11 Jun 2002 16:02:33 GMT, johninsd at san dot rr dot com




>>I have a tricky problem with the lilo boot configuration. First the
>>enviroment:
>>Compaq Professional WKS 5000
>>- 2GB SCSI HDD (ID 0)
>>- Yamaha CDWriter (ID 5)
>>- additionally a Promise Fasttrak 66 with two 60GB IDE HDD
>>- i use the fasttrak controller only as IDE Controller not to RAID the
>>drives

>>I installed the SuSE Linux 8.0 Pro with a root-partition on the SCSI
>>Drive. The disk connected to the promise controller used as hda and
>>hdc. I force the Lilo-bootloader to use the SCSI-Disc as 0x81

>Are you sure what the device codes actually are?

>The bios assigns the device codes; you just have to tell LILO what they are:

>disk = /dev/hda    bios = 0x80
>disk = /dev/hdc    bios = 0x8?
>disk = /dev/sda    bios = 0x8?

>The lilo source distribution contains two diagnostic disks:

>make floppy1
>make floppy2

>The shorter diagnostic on floppy1 will nail down the actual device codes.

>--John

>LILO source code at http://brun.dyndns.org/pub/linux/lilo

--
Steve S.


remove spaces, NOSPAM and replace dot for . before replying

 
 
 

LILO Boot Problems

Post by Ian Northeas » Thu, 13 Jun 2002 05:44:28



> It was my impression (experience) that most PC BIOS will always boot of first
> IDE drive when one is present, so you must put LILO on the MBR of the first
> IDE disk, even if you want to boot off the SCSI disk only. I've seen some BIOS
> have option to work around this, but I've yet to see it actually work. Maybe
> this is something you are aware of and newer PC BIOS / versions of LILO can
> get around this?

I have a MB which is about 2 years old - an Abit BX6 - with an Adaptec
2940UW SCSI controller with two disks attached plus an IDE disk. My Lilo
version is also fairly old - 0.20. This boots fine from SCSI. All that
is necessary is to set the PC BIOS to boot off SCSI, set the SCSI BIOS
to boot off the correct disk, and put:

boot=/dev/sda
disk=/dev/sda
        bios=0x80

in lilo.conf. LILO is on the MBR of sda. The MBR on hda is actually a
Windows one, which I use from VMware with raw disk.

Originally the system had no IDE disks at all, and then it was not
necessary to have the "disk=" bit in lilo.conf. With the IDE disk
present, Lilo does not consider sda to be the "first disk" without this
setting.

Regards, Ian

 
 
 

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

Hi,
I installed redhat 3.0.3 on my second eide hard drive. Initially I put
lilo on a floppy and it was working fine. Today I decided to reinstall
lilo on my first hard drive (master). When rebooted it could not start
windows 95. The following list tells what I did to recover and what did
not work in order.
1. boot dos from floppy
   fdisk /mbr did not work
   sys c: gave invalid media type error.
   using fdisk I viewed the partition tabel and the system was UNKNOWN

2. boot with lilo floppy to linux
   mount -t msdos /dev/hda /mnt
   ls /mnt
   gave invalid file type error.

3. I tried lilo -u but no luck.
   same problems as above: both linux and dos could not read the c drive

4. I copied boot.0300 to /dev/hda
   now linux could see some files but with weird names in my c drive

5. I rebooted without floppy and I got invalid system disk error.

Now the situation is linux can see some files with weird names and dos
gives invalid media type error.

Any help will be appreciated.

Hulya K. Kuzucu Eraslan    
Department of Economics      
University of Minnesota      
http://www.econ.umn.edu/~eraslan                          

2. Solaris 7 11/99 release

3. win95 & linux (lilo) boot problems

4. Programming raw sockets

5. LILO BOOT Problem on Intel Endeavor MB

6. Firewall questions

7. LILO/Boot problem solved!

8. Blank screen / authentication problem ? Please help

9. LILO, boot problems

10. LILO boot problem

11. lilo boot problem: hangs on LI

12. LILO BOOT PROBLEM

13. Need Help with LILO Boot Problem