Lubomir Sedlacik writes:
> On Tue, May 17, 2005 at 11:10:52AM -0600, Greg Oster wrote:
> > rudolf writes:
> > > according to 'man 8 raidctl',
> > >=20
> > > ``Multi-layered RAID devices (such as a RAID 0 set made up of RAID 1
> > > sets) are not supported as root devices or auto-configurable devices
> > > at this point.''
> > >=20
> > > May the patch to init discussed in following thread help with
> > > current situation?
> > >
> > > http://mail-index.netbsd.org/tech-userlevel/2005/05/15/0000.html
> 
> short answer, yes.
> 
> long answer, yes, you will need to create a ramdisk containing all the
> necessary files to configure your RAID sets and mount the file system.
> then embed this md(4) image to your boot kernel and put it on a file
> system on a device accessible by normal bootblocks (either ffs, msdos or
> cd9660).
> 
> > No...  the autoconfiguration bits happen in the kernel long before=20
> > init is run.  Allowing multi-layered RAID stuff for root would likely=20
> > require teaching the bootblocks about RAID 0 sets, and that's quite a=20
> > bit harder than supporting RAID 1 sets.  (Autoconfiguration of=20
> > multi-layer RAID sets could be done with a little work, but there=20
> > hasn't bene a whole lot of demand for it...)
> 
> that's why the chrooting init(8) could be used to boot from an initial
> md(4) within the kernel, do all steps necessary to mount RAID 0 file
> system and then continue multiuser within chroot in this file system.

This would require you to get a kernel from just a RAID 1 or a non-RAID 
partition.... 

> the same trick as i use to have root fs on cgd(4).

As would this, I presume...

Later...

Greg Oster