LILO at stops at "LI" stage (4 IDE & 1 SCSI drives)
manuchao
started facing what I hope is a more simple challenge -- the boot
process stops at the "LI" stage. I've been reading about that and have
tried a number of different things but I have not been able to find a
solution to my problem.
I have a total of 5 drives (4 IDE and 1 SCSI), as reported by BIOS and
seen in the output of dmesg:
First Controller:
Primary IDE drive (drive 0): /dev/hda
Secondary IDE drive (drive 1): /dev/hdb
Second Controller:
Primary IDE drive (CD-ROM drive) /dev/hdc
Secondary IDE drive (drive 3): /dev/hdd
And, of course:
SCSI drive (ID 6, LUN 0): /dev/sda
The question is -- how do I force the boot partition of the SCSI drive
(/dev/sda1) to be the primary boot device? (The other drives do not
have a system partition, those contain data only). I had intitally
placed the boot record on the MBR of /dev/hda but somehow it got
corrupted in the process. If possible, I'd prefer to not have to use
the MBR of any of the other drives, but the SCSI disk.
Based on what I've read so far I assume that the BIOS addresses for
the 5 drives would be something like (I'm not sure about the last 3):
0x80 /dev/hda
0x81 /dev/hdb
0x82 /dev/hdc (CD-ROM)
0x83 /dev/hdd
0x84 /dev/sda
Here is my lilo.conf file:
------------------------
prompt
timeout=50
boot=/dev/sda
default=linux
map=/boot/map
install=/boot/boot.b
restricted
password=*****
message=/boot/message
linear
image=/boot/vmlinuz-2.4.18-14
label=linux
root=/dev/sda1
initrd=/boot/initrd-2.4.18-14.img
read-only
append="root=LABEL=/"
------------------------
When I run "lilo -v -v -v -b /dev/sda" I get some errors which seem to
indicate that the boot partition (/dev/sda) resides on drive 0x82.
Hmmm, how can it be if the addresses mentioned above are correct? I've
tried adding the following 2 lines right after "linear" but it won't
help:
disk=/dev/sda
bios=0x82 (tried 0x81, 0x83, 0x84 as well)
Can anyone shed some light on a) the correct BIOS addresses and b) the
correct parameters for lilo.conf? Again, I only have 1 Linux system
partition and it's located on /dev/sda1.
I'd really appreciate your help on this. Thanks.
-- Manu
Eric Moors
> When I run "lilo -v -v -v -b /dev/sda" I get some errors which seem to
> indicate that the boot partition (/dev/sda) resides on drive 0x82. Hmmm,
> how can it be if the addresses mentioned above are correct? I've tried
> adding the following 2 lines right after "linear" but it won't help:
>
> disk=/dev/sda
> bios=0x82 (tried 0x81, 0x83, 0x84 as well)
>
Then there's only one left to try ;-)
> Can anyone shed some light on a) the correct BIOS addresses and b) the
> correct parameters for lilo.conf? Again, I only have 1 Linux system
> partition and it's located on /dev/sda1.
Depends on your BIOS. I guess sda is 0x80, as that's the one you haven't
tried yet. And the fact that you're booting from sda, also indicates this.
IIRC LILO nowadays comes with a floppy that can detect the BIOS codes for
you. Try that one too if 0x80 fails
Eric
Markus Kossmann
^^^^^^^^^^^^^^^^
You are writing lilos first stage bootcode to the MBR of /dev/sda. Thats
makes sense only if you did switch your motherboard BIOS to "boot from
SCSI" In that case your SCSI disk becomes bios device 0x80 and you will
have to add disk=/dev/sda bios=0x80 to lilo.conf.
If your motherboard BIOS doesn't provide the "boot from SCSI" option you
have to use /dev/hda as bootdevice and your SCSI disk is bios device 0x83 (
the CDROM doesn't count as harddisk).In that case you also need to use
lilos disk=/bios= option to get lilo right.
--
Markus Kossmann markus....@inka.de
manuchao
The strange thing is that when I select "Symbios Support" (or SCSI) as
the primary boot device in the BIOS I only see the CD-ROM drive being
detected. The detection process also takes a lot longer when the SCSI
drive is the primary device. Not sure why.
I will try uplugging all the IDE devices and see if I can get lucky as
you did.
-- Manu
Andy McFadden <fad...@fadden.com> wrote in message news:<1ADma.5571$JX2.3...@typhoon.sonic.net>...
> In comp.os.linux.setup Markus Kossmann <markus....@inka.de> wrote:
> >> After successfully adding/configuring a SCSI drive on my Linux box I
> >> started facing what I hope is a more simple challenge -- the boot
> >> process stops at the "LI" stage. I've been reading about that and have
> >> tried a number of different things but I have not been able to find a
> >> solution to my problem.
>
> Don't know if this applies to your situation, but I'm going to throw
> this into the ring:
>
> On one of my systems I found that I had to remove the IDE hard drive, boot
> into Linux, run LILO on the SCSI drive, and only then attach the IDE drive.
> Apparently the LILO installer was seeing the IDE hard drive and configuring
> the world in strange ways. Without the IDE drive present it wrote the
> correct LILO config, and it continued to work even after I added the IDE
> drive back in.
johninsd at san dot rr dot com
receive device codes.
Yes, when the SCSI device is selected in the BIOS as the boot device, it will
be device 0x80, and will require:
disk=/dev/sda bios=0x80
in the config file for versions of LILO earlier than 22.5. The present
release (22.5.1) should not need the disk= section.
Sounds like you are booting okay now.
--John
manuchao
situation. I discovered something interesting after I disabled ALL the
IDE devices in the BIOS and disconnected them from the IDE
controllers.
Again, only the SCSI and floppy drives were online this time around.
Check this out:
///// lilo.conf /////
prompt
timeout=50
boot=/dev/sda
disk=/dev/sda
bios=0x80
default=linux
map=/boot/map
install=/boot/boot.b
restricted
password=******
message=/boot/message
linear
image=/boot/vmlinuz-2.4.18-14
label=linux
root=/dev/sda1
initrd=/boot/initrd-2.4.18-14.img
read-only
append="root=LABEL=/"
///// output of command "lilo -v -v -v" /////
LILO version 21.4-4, Copyright (C) 1992-1998 Werner Almesberger
'lba32' extensions Copyright (C) 1999,2000 John Coffman
Reading boot sector from /dev/sda
Merging with /boot/boot.b
Device 0x0801: BIOS drive 0x80, 133 heads, 1017 cylinders,
62 sectors. Partition offset: 62 sectors.
Secondary loader: 11 sectors.
Device 0x0801: BIOS drive 0x80, 133 heads, 1017 cylinders,
62 sectors. Partition offset: 62 sectors.
Mapping message file /boot/message
Device 0x0801: BIOS drive 0x80, 133 heads, 1017 cylinders,
62 sectors. Partition offset: 62 sectors.
Message: 46 sectors.
Boot image: /boot/vmlinuz-2.4.18-14
Device 0x0801: BIOS drive 0x80, 133 heads, 1017 cylinders,
62 sectors. Partition offset: 62 sectors.
Setup length is 10 sectors.
Mapped 2200 sectors.
Mapping RAM disk /boot/initrd-2.4.18-14.img
Device 0x0801: BIOS drive 0x80, 133 heads, 1017 cylinders,
62 sectors. Partition offset: 62 sectors.
RAM disk: 328 sectors.
Added linux *
<dev=0xc0,hd=8,cyl=136,sct=166>
"ro root=801 BOOT_FILE=/boot/vmlinuz-2.4.18-14 root=LABEL=/"
/boot/boot.0800 exists - no backup copy made.
Map file size: 17408 bytes.
Writing boot sector.
///// output of command "strings /boot/map" /////
Glinux
******
!"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~
ro root=801 BOOT_FILE=/boot/vmlinuz-2.4.18-14 root=LABEL=/
Strange -- even though I'm only using the SCSI hard disk (/dev/sda) it
is being seen somehow as disk 0x81, not 0x80, as one would expect.
I'm saying this because of the references to "Device 0x0801" in the
output of "lilo -v -v -v" as well as the reference to "root=801" in
/boot.map.
Any thoughts?
johninsd at san dot rr dot com <bitb...@hotmail.com> wrote in message news:<ghuo9v433ig6pprlg...@4ax.com>...
Timothy Murphy
> Strange -- even though I'm only using the SCSI hard disk (/dev/sda) it
> is being seen somehow as disk 0x81, not 0x80, as one would expect.
> I'm saying this because of the references to "Device 0x0801" in the
> output of "lilo -v -v -v" as well as the reference to "root=801" in
> /boot.map.
>
> Any thoughts?
I didn't see any mention of 0x81 in your post.
Are you confusing 0801 with 081?
Are you sure you haven't solved your problem?!
--
Timothy Murphy
e-mail: t...@birdsnest.maths.tcd.ie
tel: +353-86-233 6090
s-mail: School of Mathematics, Trinity College, Dublin 2, Ireland
johninsd at san dot rr dot com
Yes. root=801 means "root=/dev/sda1". 0801(16) is the major/minor device
number of partition sda1.
--John
manuchao
read the whole article I posted? about 81 lines don't show, unless you
click on "Read the rest of this message... (81 more lines)". There,
you'll see "Device=0x801" and "root=801". What is that? The root
partition (/dev/sda1)??
I would assume that the command "lilo" would re/create the boot code
on the MBR of the boot device (/dev/sda), correct? It looks like the
MBR does not contain the appropriate code. When I attempt to boot off
/dev/sda I eventually get the typical "No system found, Insert disk in
drive A:" error.
Timothy Murphy <t...@birdsnest.maths.tcd.ie> wrote in message news:<TqSna.9210$pK2....@news.indigo.ie>...
Timothy Murphy
>>///// lilo.conf /////
>>prompt
>>timeout=50
>>boot=/dev/sda
>>disk=/dev/sda
>> bios=0x80
>>default=linux
>>map=/boot/map
>>install=/boot/boot.b
>>restricted
>>password=******
>>message=/boot/message
>>linear
>>
>>image=/boot/vmlinuz-2.4.18-14
>> label=linux
>> root=/dev/sda1
>> initrd=/boot/initrd-2.4.18-14.img
>> read-only
>> append="root=LABEL=/"
>>
I use grub rather than lilo,
so I may be off-beam,
but I would try
(1) Omit the bios=0x80 --
I don't think it can do any harm,
but it won't do any good either.
(2) Try lba in place of linear.
(3) Omit the restricted and password lines
until you have things working.
(4) Omit the append line.
I take it that /dev/sda1 _is_ your / partition,
(as shown in /etc/fstab for example).
(5) If /etc/fstab contains "label" lines,
I'd be inclined to replace them with the actual drives.
The labelling could have got confused with all the disk-changes.
(6) Don't forget to run /sbin/lilo after any changes to lilo.conf .
FlyingDutchMan
devices via onboard IDE of which hda contain'd RedHat Linux 8 & 1 device via
PCI Promise Ultra133TX2 which contained WinXP on hde). In my case the
problem was linked to the boot-sequence defined in BIOS. Normally I would
boot via "SCSI"-option in my BIOS; this means via PCI Promise card to WinXP.
When I wanted to boot to Red Hat Linux 8 I or changed the boot-up setting in
BIOS to "IDE, or I would use a Linux boot disk.
In case I;
* booted via Linux boot disc while having "SCSI" boot in my BIOS defined,
* then created mbr with "lilo -v" on hda,
* then rebooted while having changed to "IDE" boot in my BIOS,
I got the same problem. Try recreating the mbr with proper setting in BIOS.
That should solve it as far as I can remember.
Other issue which might be a problem (as this problem occured to me about 6
months ago so it is kinda difficult to exactly remember the issue) is DMA.
Try booting with key "ide=nodma" as I also had problems with recognition of
the higher DMA-modes of the drive mounted to the PCI Promise Ultra133TX2
(UDMA-133 drive).
I hope this help you further.
"manuchao" <manu_...@yahoo.com> schreef in bericht
news:97bc4c4d.0304...@posting.google.com...