hi
I hope this is not OT - didn't find any LILO mailing list. after trying
virtually everything - can anyone help me with a tip?
Running 2.4.19-pre10-ac2, RedHat 7.3 (LILO version 21.4-4), I have root on
/dev/md0 on RAID-1 on /dev/hda1 and /dev/hdb1. I've tried the howto at
http://www.tldp.org/HOWTO/mini/Boot+Root+Raid+LILO-3.html#ss3.1, but it still
doesn't help me. lilo just tells me "L 99 99 99 99 ..." some half a page, and
then stops.I'm trying. All the time it prints this, it seems to be searching
the floppy for some reason.
The lilo.conf suggested by the above HOWTO, is this
# lilo.conf.hda - primary ide master
disk=/dev/md0
bios=0x80
sectors=63
heads=16
cylinders=39770
partition=/dev/md1
start=63
boot=/dev/hda
map=/boot/map
install=/boot/boot.b
image=/boot/bzImage
root=/dev/md0
read-only
label=LinuxRaid
sector/head/cylinder is corrected to the actual data reported from 'fdisk
-ul'.
When trying to set. boot=/dev/hdm (which is the first drive on the on-board
chipset), lilo installs, and I get LI instead of L 99 99 ... Same result with
LBA32.
I also have another box with Linux, running SuSE 7.2 (LILO version 21.7-5)
with RAID-1 on two drives. Here everything works fine
thanks for all help
roy
--
Roy Sigurd Karlsbakk, Datavaktmester
Computers are like air conditioners.
They stop working when you open Windows.
> Hi,
> I had this once and resolved it with adding a "default" line to the
> lilo.conf:
> default = LinuxRaid
>
> Also have boot=/dev/md0, not boot=/dev/hda.
hm
I keep getting this one..
[root@jumbo root]# lilo
boot = /dev/hda, map = /boot/map.0301
Added linux2419rc1 *
Added linux2418
Added linux-orig
Fatal: Duplicate geometry definition for /dev/md0
Any ideas?
thanks
roy
--
Roy Sigurd Karlsbakk, Datavaktmester
Computers are like air conditioners.
They stop working when you open Windows.
In article <[email protected]> you wrote:
> hi
>
> I hope this is not OT - didn't find any LILO mailing list. after trying
> virtually everything - can anyone help me with a tip?
>
> Running 2.4.19-pre10-ac2, RedHat 7.3 (LILO version 21.4-4), I have root on
> /dev/md0 on RAID-1 on /dev/hda1 and /dev/hdb1. I've tried the howto at
> http://www.tldp.org/HOWTO/mini/Boot+Root+Raid+LILO-3.html#ss3.1, but it still
> doesn't help me. lilo just tells me "L 99 99 99 99 ..." some half a page, and
> then stops.I'm trying. All the time it prints this, it seems to be searching
> the floppy for some reason.
>
> The lilo.conf suggested by the above HOWTO, is this
>
> # lilo.conf.hda - primary ide master
> disk=/dev/md0
> bios=0x80
> sectors=63
> heads=16
> cylinders=39770
> partition=/dev/md1
> start=63
> boot=/dev/hda
> map=/boot/map
> install=/boot/boot.b
>
> image=/boot/bzImage
> root=/dev/md0
> read-only
> label=LinuxRaid
Hi,
I had this once and resolved it with adding a "default" line to the
lilo.conf:
default = LinuxRaid
Also have boot=/dev/md0, not boot=/dev/hda.
Cheers,
Juri
--
Juri Haberland <[email protected]>
Roy Sigurd Karlsbakk wrote:
>> Hi,
>> I had this once and resolved it with adding a "default" line to the
>> lilo.conf:
>> default = LinuxRaid
>>
>> Also have boot=/dev/md0, not boot=/dev/hda.
>
> hm
>
> I keep getting this one..
>
> [root@jumbo root]# lilo
> boot = /dev/hda, map = /boot/map.0301
> Added linux2419rc1 *
> Added linux2418
> Added linux-orig
> Fatal: Duplicate geometry definition for /dev/md0
>
> Any ideas?
Hm, I'm no lilo nor raid expert, but I'd suggest to strip down the
lilo.conf to the defaults. E.g. I have:
prompt
timeout=50
default=linux
boot=/dev/md2
map=/boot/map
install=/boot/boot.b
message=/boot/message
image=/boot/vmlinuz
label=linux
read-only
root=/dev/md0
> Hm, I'm no lilo nor raid expert, but I'd suggest to strip down the
> lilo.conf to the defaults. E.g. I have:
> prompt
> timeout=50
> default=linux
> boot=/dev/md2
> map=/boot/map
> install=/boot/boot.b
> message=/boot/message
>
> image=/boot/vmlinuz
> label=linux
> read-only
> root=/dev/md0
hm...
still gave me 'LI'
I beleive it might be because LILO need to be installed on the first drive
BIOS finds (/dev/hdm). I might try to address it as 0x80? Do you think
that'll help?
--
Roy Sigurd Karlsbakk, Datavaktmester
Computers are like air conditioners.
They stop working when you open Windows.
Roy Sigurd Karlsbakk wrote:
>> Hm, I'm no lilo nor raid expert, but I'd suggest to strip down the
>> lilo.conf to the defaults. E.g. I have:
>> prompt
>> timeout=50
>> default=linux
>> boot=/dev/md2
>> map=/boot/map
>> install=/boot/boot.b
>> message=/boot/message
>>
>> image=/boot/vmlinuz
>> label=linux
>> read-only
>> root=/dev/md0
>
> hm...
> still gave me 'LI'
> I beleive it might be because LILO need to be installed on the first drive
> BIOS finds (/dev/hdm). I might try to address it as 0x80? Do you think
> that'll help?
I assume the onboard IDE stuff (hdm) is something like a Promise
controller. If so you should be able set the boot order to boot from the
normal IDE chipset (hda/hdb). If doesn't help I'd suggest that you ask
on the linux-raid mailing list.
Cheers,
Juri
Roy Sigurd Karlsbakk wrote:
>> I assume the onboard IDE stuff (hdm) is something like a Promise
>> controller. If so you should be able set the boot order to boot from the
>> normal IDE chipset (hda/hdb). If doesn't help I'd suggest that you ask
>> on the linux-raid mailing list.
>
> The on-board is a VIA controller. see from lspci
>
> 00:0c.0 Unknown mass storage controller: Promise Technology, Inc. 20268 (rev
> 02)
> 00:0d.0 Unknown mass storage controller: Promise Technology, Inc. 20268 (rev
> 02)
> 00:0e.0 RAID bus controller: CMD Technology Inc PCI0649 (rev 02)
> 00:11.1 IDE interface: VIA Technologies, Inc. Bus Master IDE (rev 06)
So you have your two raid drives connected to the VIA controller, right?
Then have a look into the BIOS setup and see, if there's something that
might affect the boot order...
> and - as for linux-raid, see below:
>
> ----- The following addresses had permanent fatal errors -----
> <[email protected]>
> (reason: 550 5.1.1 <[email protected]>... User unknown)
No wonder, vger.rutgers.edu ceased to exist ~2 years ago. Use
vger.kernel.org instead ;)
Juri
> I assume the onboard IDE stuff (hdm) is something like a Promise
> controller. If so you should be able set the boot order to boot from the
> normal IDE chipset (hda/hdb). If doesn't help I'd suggest that you ask
> on the linux-raid mailing list.
The on-board is a VIA controller. see from lspci
00:0c.0 Unknown mass storage controller: Promise Technology, Inc. 20268 (rev
02)
00:0d.0 Unknown mass storage controller: Promise Technology, Inc. 20268 (rev
02)
00:0e.0 RAID bus controller: CMD Technology Inc PCI0649 (rev 02)
00:11.1 IDE interface: VIA Technologies, Inc. Bus Master IDE (rev 06)
and - as for linux-raid, see below:
----- The following addresses had permanent fatal errors -----
<[email protected]>
(reason: 550 5.1.1 <[email protected]>... User unknown)
--
Roy Sigurd Karlsbakk, Datavaktmester
Computers are like air conditioners.
They stop working when you open Windows.
> > The on-board is a VIA controller. see from lspci
> >
> > 00:0c.0 Unknown mass storage controller: Promise Technology, Inc. 20268
> > (rev 02)
> > 00:0d.0 Unknown mass storage controller: Promise Technology, Inc. 20268
> > (rev 02)
> > 00:0e.0 RAID bus controller: CMD Technology Inc PCI0649 (rev 02)
> > 00:11.1 IDE interface: VIA Technologies, Inc. Bus Master IDE (rev 06)
>
> So you have your two raid drives connected to the VIA controller, right?
> Then have a look into the BIOS setup and see, if there's something that
> might affect the boot order...
I have 4 drives connected to each controller, that is, 2 drives per channel.
None are RAID controllers - just stupid ATA controllers.
point isn't to change bootorder - just to make bloody LILO work.
See fstab, jumbo-dmesg.txt, mdstat and raidtab in http://karlsbakk.net/bugs/
for more info
thanks
roy
--
Roy Sigurd Karlsbakk, Datavaktmester
Computers are like air conditioners.
They stop working when you open Windows.
> What about:
>
> disk=/dev/hda
> bios=0x80
> boot=/dev/hda
>
> map=/boot/map.hda
> install=/boot/boot.b.hda
> backup=/boot/boot.b.rs.hda
>
> prompt
> timeout=50
> linear
>
> image=/boot/bzImage-2.4.19-pre7
> label=2.4.19-pre7
> root=/dev/md1
> read-only
It doesn't work. Still LI only.
Any other ideas
--
Roy Sigurd Karlsbakk, Datavaktmester
Computers are like air conditioners.
They stop working when you open Windows.
see below for my original post
I've uploaded some files to http://karlsbakk.net/bugs/ that may help to
explain the problem. Still - I can't boot from nothing but floppy.
thanks
roy
On Sunday 30 June 2002 14:19, Roy Sigurd Karlsbakk wrote:
> hi
>
> I hope this is not OT - didn't find any LILO mailing list. after trying
> virtually everything - can anyone help me with a tip?
>
> Running 2.4.19-pre10-ac2, RedHat 7.3 (LILO version 21.4-4), I have root on
> /dev/md0 on RAID-1 on /dev/hda1 and /dev/hdb1. I've tried the howto at
> http://www.tldp.org/HOWTO/mini/Boot+Root+Raid+LILO-3.html#ss3.1, but it
> still doesn't help me. lilo just tells me "L 99 99 99 99 ..." some half a
> page, and then stops.I'm trying. All the time it prints this, it seems to
> be searching the floppy for some reason.
>
> The lilo.conf suggested by the above HOWTO, is this
>
> # lilo.conf.hda - primary ide master
> disk=/dev/md0
> bios=0x80
> sectors=63
> heads=16
> cylinders=39770
> partition=/dev/md1
> start=63
> boot=/dev/hda
> map=/boot/map
> install=/boot/boot.b
>
> image=/boot/bzImage
> root=/dev/md0
> read-only
> label=LinuxRaid
>
> sector/head/cylinder is corrected to the actual data reported from 'fdisk
> -ul'.
>
> When trying to set. boot=/dev/hdm (which is the first drive on the on-board
> chipset), lilo installs, and I get LI instead of L 99 99 ... Same result
> with LBA32.
>
> I also have another box with Linux, running SuSE 7.2 (LILO version 21.7-5)
> with RAID-1 on two drives. Here everything works fine
>
> thanks for all help
>
> roy
--
Roy Sigurd Karlsbakk, Datavaktmester
Computers are like air conditioners.
They stop working when you open Windows.
my system has 4 disks, but /dev/md0 is a RAID1 for /boot. (/dev/md1 is a
RAID5 and LVM is on top of it...) anyhow, this is what works for me.
i've even pulled out a disk and it still boots.
btw, you really don't want to put two drives on an IDE controller. not
just for performance reasons -- if a master drive fails it can easily
prevent access to the slave... so you'll have a two disk failure on your
hands. or maybe this is just urban legend and i'm spreading it further ;)
-dean
lba32
boot=/dev/md0
root=/dev/arctic/root
install=/boot/boot-text.b
map=/boot/map
prompt
timeout=150
raid-extra-boot=/dev/hde,/dev/hdg,/dev/hdi,/dev/hdk
password=XXXXXXXX
serial=0,38400n8
append="console=tty0 console=ttyS0,38400n8"
default=linux
image=/boot/vmlinuz
initrd=/boot/initrd-lvm-2.4.19-pre3-ac1.gz
label=linux
restricted
read-only
On Sunday 30 June 2002 23:46, Michael wrote:
> > I hope this is not OT - didn't find any LILO mailing list. after
> > trying virtually everything - can anyone help me with a tip?
>
> The problem you're having is not with raid but with LILO in general.
> I don't remember the specifics, but I've experienced the same thing
> and it was an error in how I used lilo or the version of the boot
> record -- something strange like that. Raid is not part of the
> problem.
>
> Read the docs that come with the LILO distribution in the source. The
> man page does not have as much info. You may also be suffering from
> differing version of the MBR -- a major source of pain and suffering.
I've read the fscking manual - all I can find - for both grub and lilo, and
I've tried all possible configurations I can think of.
point is - I beleive there's a BIOS/linux misunderstanding somewhere
roy
--
Roy Sigurd Karlsbakk, Datavaktmester
Computers are like air conditioners.
They stop working when you open Windows.
On Mon, Jul 01, 2002 at 12:07:07PM +0200, Roy Sigurd Karlsbakk wrote:
...
>
> I've read the fscking manual - all I can find - for both grub and lilo, and
> I've tried all possible configurations I can think of.
>
> point is - I beleive there's a BIOS/linux misunderstanding somewhere
Did you try the raid-extra-boot option for LILO ? I really don't
know if this is the problem you are seeing, but it's worth a shot I
think.
--
................................................................
: [email protected] : And I see the elder races, :
:.........................: putrid forms of man :
: Jakob ?stergaard : See him rise and claim the earth, :
: OZ9ABN : his downfall is at hand. :
:.........................:............{Konkhra}...............:
hi
trying this:
--
boot=/dev/md0
map=/boot/map
install=/boot/boot.b.hda
backup=/boot/boot.b.rs.hda
prompt
timeout=50
lba32
raid-extra-boot=/dev/hda,/dev/hdb
...
with lilo-21.4-4 (standard with rh73) it won't accept the raid-extra-boot
option
and
with lilo-22.3.1, it won't accept (i beleive boot=/dev/md0)
[root@jumbo lilo-22.3.1]# lilo
Warning: using BIOS device code 0x80 for RAID boot blocks
Fatal: Filesystem would be destroyed by LILO boot sector: /dev/md0
thanks
roy
On Sunday 30 June 2002 20:57, dean gaudet wrote:
> my system has 4 disks, but /dev/md0 is a RAID1 for /boot. (/dev/md1 is a
> RAID5 and LVM is on top of it...) anyhow, this is what works for me.
> i've even pulled out a disk and it still boots.
>
> btw, you really don't want to put two drives on an IDE controller. not
> just for performance reasons -- if a master drive fails it can easily
> prevent access to the slave... so you'll have a two disk failure on your
> hands. or maybe this is just urban legend and i'm spreading it further ;)
>
> -dean
>
> lba32
> boot=/dev/md0
> root=/dev/arctic/root
> install=/boot/boot-text.b
> map=/boot/map
> prompt
> timeout=150
> raid-extra-boot=/dev/hde,/dev/hdg,/dev/hdi,/dev/hdk
>
> password=XXXXXXXX
>
> serial=0,38400n8
> append="console=tty0 console=ttyS0,38400n8"
>
> default=linux
>
> image=/boot/vmlinuz
> initrd=/boot/initrd-lvm-2.4.19-pre3-ac1.gz
> label=linux
> restricted
> read-only
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
Roy Sigurd Karlsbakk, Datavaktmester
Computers are like air conditioners.
They stop working when you open Windows.
On Mon, Jul 01, 2002 at 01:30:18PM +0200, Roy Sigurd Karlsbakk wrote:
> hi
>
> trying this:
> --
> boot=/dev/md0
> map=/boot/map
> install=/boot/boot.b.hda
> backup=/boot/boot.b.rs.hda
> prompt
> timeout=50
> lba32
> raid-extra-boot=/dev/hda,/dev/hdb
> ...
>
> with lilo-21.4-4 (standard with rh73) it won't accept the raid-extra-boot
> option
Ok - I use it with LILO 22.2 here, it's on Debian, and it's the only box
where I ever needed that option.
My lilo.conf:
----------8<--------
lba32
boot=/dev/md0
raid-extra-boot=/dev/sda,/dev/sdb
root=/dev/md1
disk=/dev/sda
bios=0x80
disk=/dev/sdb
bios=0x81
install=/boot/boot-menu.b
delay=20
default=Linux
image=/boot/vmlinuz
label=Linux
read-only
----------8<--------
The following is from a standard RedHat 7.3 system with LILO 21.4.4-14:
----------8<-----8<-----
boot=/dev/md3
map=/boot/map
install=/boot/boot.b
message=/boot/message
prompt
timeout=40
linear
default=2.4.18
image=/boot/vmlinuz-2.4.18
label=2.4.18
read-only
root=/dev/md2
----------8<-----8<-----
Both systems are SCSI-only though.
The following is an IDE-only RedHat 7.2 with LILO 21.4.4.14
----8<-----8<------------
boot=/dev/md0
map=/boot/map
install=/boot/boot.b
prompt
timeout=50
message=/boot/message
linear
default=linux
image=/boot/vmlinuz
label=linux
read-only
root=/dev/md1
----8<-----8<------------
Perhaps you could change the lba32 option into linear ? I'm really
shooting in the mist here - LILO tends to "just work", and ignorance is
bliss ;)
--
................................................................
: [email protected] : And I see the elder races, :
:.........................: putrid forms of man :
: Jakob ?stergaard : See him rise and claim the earth, :
: OZ9ABN : his downfall is at hand. :
:.........................:............{Konkhra}...............:
> Perhaps you could change the lba32 option into linear ? I'm really
> shooting in the mist here - LILO tends to "just work", and ignorance is
> bliss ;)
It still won't work. It doesn't seem to like boot=/dev/md0. see below
roy
[root@jumbo root]# lilo
Warning: LINEAR is deprecated in favor of LBA32: LINEAR specifies 24-bit
disk addresses below the 1024 cylinder limit; LBA32 specifies 32-bit disk
addresses not subject to cylinder limits on systems with EDD bios
extensions;
use LINEAR only if you are aware of its limitations.
Warning: using BIOS device code 0x80 for RAID boot blocks
Fatal: Filesystem would be destroyed by LILO boot sector: /dev/md0
[root@jumbo root]#
--
Roy Sigurd Karlsbakk, Datavaktmester
Computers are like air conditioners.
They stop working when you open Windows.
Roy Sigurd Karlsbakk wrote:
>> I assume the onboard IDE stuff (hdm) is something like a Promise
>> controller. If so you should be able set the boot order to boot from the
>> normal IDE chipset (hda/hdb). If doesn't help I'd suggest that you ask
>> on the linux-raid mailing list.
>
> The on-board is a VIA controller. see from lspci
>
> 00:0c.0 Unknown mass storage controller: Promise Technology, Inc. 20268 (rev
> 02)
> 00:0d.0 Unknown mass storage controller: Promise Technology, Inc. 20268 (rev
> 02)
> 00:0e.0 RAID bus controller: CMD Technology Inc PCI0649 (rev 02)
> 00:11.1 IDE interface: VIA Technologies, Inc. Bus Master IDE (rev 06)
What buffles me is that - according to your dmesg output at
http://karlsbakk.net/bugs/dmesg - the disk connected to the onboard VIA
controller are detected as hdm-hdp.
Have you checked you BIOS settings? Some mainboards allow to use
off-board controllers to be used before the on-board ones...
Juri