Hi,
On Wed, Oct 27, 2004 at 08:37:49PM +1000, Andrew Pollock wrote:
> On Wed, Oct 27, 2004 at 05:53:31AM -0400, Matthew P McGuire wrote:
> >
> > Overall the installtion of the box using the daily build was not a
> > problem. I used the daily build to try out the RAID support recently
> > added to partman. Everything worked absolutely great after I figured
> > out one small catch with /boot partition. It appears that when using
> > software RAID it is necessary to have the /boot part on at least one
> > partition outside of the array so that grub or lilo can be installed.
> > Without knowing this I went through a number of trial and error
> > configurations until I had the array set up correctly. Initially I
> > mistakenly tried to make the RAID array bootable using the interface.
> > This failed on all partition attempts. It occurred to me that a boot
> > block on the RAID didn't make sense, so it may be wise to remove the
> > ability to flag the /dev/md devices as bootable. As a result the /boot
> > partition was necessary. I would recommend adding a dialog that the
> > /boot partition is necessary for root raid installations. This will
> > help other new users of the RAID installation tools to avoid these
> > mistakes.
> >
>
> You can boot from a RAID volume. I think there's currently a bug with
> lilo-installer, where it doesn't quite get it right...
The problem is not lilo or grub AFAIK.
In my installation-repport(#275999) I mentionned how to solve this
issue:
1) add md and raid1 into /etc/mkinitrd/modules
md
raid1
2) change ROOT on /etc/mkinitrd.conf
ROOT=/dev/md0
3) run mkinitrd -o /boot/initrd.img-2.6.8-raid
4) modify /boot/grub/menu.lst to specify to use the initrd you
created
Cheers,
--
Pierre Machard
<pmachard@debian.org> http://debian.org
GPG: 1024D/23706F87 : B906 A53F 84E0 49B6 6CF7 82C2 B3A0 2D66 2370 6F87
Attachment:
signature.asc
Description: Digital signature