After setting up Raid1 I can boot to disk2 (wd1) but not
> to Disk0 (wd0).  It seems to be a common problem based on what I've found on
> the internet but I have not found much in the way of a solution.

When you try to boot from wd0 does it say:

  NetBSD IEEE 1275 Bootblock
  .Inode not directory
  Fast Data Access MMU Miss

?  If so, that is a known problem, which is caused by a buglet in the forth
boot blocks.  If one upgrades a non-raidframe disk layout to raidframe, then
part of the non-raidframe layout is still present on the disk.  The boot
blocks read this old information but cannot read the FFS information, because
that part has been overwritten by the raidframe layout.

The fix is to teach the boot blocks to read the disklabel of the disk, check
to see if the type is raid and, if so, apply an offset to read the file
system information.  I've done this for sparc (boot blocks are in C) but
my forth knowledge is lacking, so I haven't (yet) been able to do this for
sparc64.  Is there anyone who'd like to volunteer? ;-)

J

-- 
  My other computer also runs NetBSD    /        Sailing at Newbiggin
        http://www.netbsd.org/        /   http://www.newbigginsailingclub.org/