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

• Next message: Juri Haberland: "Re: Can't boot from /dev/md0 (RAID-1)"
• Previous message: Juri Haberland: "Re: Can't boot from /dev/md0 (RAID-1)"
• In reply to: Juri Haberland: "Re: Can't boot from /dev/md0 (RAID-1)"
• Next in thread: Juri Haberland: "Re: Can't boot from /dev/md0 (RAID-1)"
• Reply: Juri Haberland: "Re: Can't boot from /dev/md0 (RAID-1)"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

> 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.
-
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/

• Next message: Juri Haberland: "Re: Can't boot from /dev/md0 (RAID-1)"
• Previous message: Juri Haberland: "Re: Can't boot from /dev/md0 (RAID-1)"
• In reply to: Juri Haberland: "Re: Can't boot from /dev/md0 (RAID-1)"
• Next in thread: Juri Haberland: "Re: Can't boot from /dev/md0 (RAID-1)"
• Reply: Juri Haberland: "Re: Can't boot from /dev/md0 (RAID-1)"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Sun Jun 30 2002 - 22:00:14 EST