Hello,

I've got a server with RAIDframe bootable RAID 1 setup. I initially
installed it with NetBSD 1.6.2 and have therefore a disk layout which
looks this:

# /dev/rwd0d:
type: ESDI
disk: WDC WD1600JB
label: colwyn
flags:
bytes/sector: 512
sectors/track: 63
tracks/cylinder: 16
sectors/cylinder: 1008
cylinders: 310101
total sectors: 312581808
rpm: 7200
interleave: 1
trackskew: 0
cylinderskew: 0
headswitch: 0           # microseconds
track-to-track seek: 0  # microseconds
drivedata: 0 

16 partitions:
#        size    offset     fstype [fsize bsize cpg/sgs]
 a: 312452784    129024       RAID                     # (Cyl.    128 - 310100)
 c:        16         0     unused      0     0        # (Cyl.      0 -      0*)
 d: 312581808         0     unused      0     0        # (Cyl.      0 - 310100)
 e:    129024         0     4.2BSD   1024  8192    90  # (Cyl.      0 -    127)

Partition "e" is the dummy partition which was necessary to make this work
with the NetBSD 1.6.x boot loader. After upgrading to NetBSD 2.0_BETA
I tried to upgrade the bootblocks, too, like this:

mount /dev/wd0e /mnt
cp -p /usr/mdec/boot /mnt
installboot -v /dev/rwd0e /usr/mdec/bootxx_ffsv1
umount /mnt

The BIOS started the new boot loader just fine but the boot loader wants
to load the kernel from partition "e" instead of "a". I've afterwards
remove "boot" from "wd0e" because the manual page claims that the boot
loader will automatically use the partition "a" if "boot" isn't found
on the current partition. But that didn't work, too.

	Kind regards

-- 
Matthias Scheler                                  http://scheler.de/~matthias/