Re: Can't boot from /dev/md0 (RAID-1)

Roy Sigurd Karlsbakk
2002-07-01T11:28:08Z

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 majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/