raidframe root issue?

[Jeff Rizzo <riz%tastylime.net@localhost>]

Trying to set up a dom0 under -current as of yesterday (9.99.87) - after 
some scrambling trying to figure out serial console (haven't figured it 
out entirely yet - this is a 10 year old HP DL160 using the IPMI console 
- I can get kernel serial, and dom0 output, but haven't yet figured out 
a working login tty), I discovered the reason I wasn't getting to 
multiuser with a dom0 kernel is that it wasn't finding the root partition:


[  32.1900747] boot device: dk0
[  32.1900747] root device (default dk0):


...once I sorted out serial console enough to be able to type "raid0a", 
things finished booting.  At first, I assumed the relatively new 
"softroot" option was causing the issue, but I see the same behavior 
with "forceroot".  Any suggestions for changes I need to make to get 
this machine to boot unattended?  I'm currently using the stock 
XEN3_DOM0, but am not averse to rebuilding...


Components:
            /dev/dk0: optimal
            /dev/dk3: optimal
No spares.
Component label for /dev/dk0:
   Row: 0, Column: 0, Num Rows: 1, Num Columns: 2
   Version: 2, Serial Number: 2021071902, Mod Counter: 92472626
   Clean: No, Status: 0
   sectPerSU: 128, SUsPerPU: 1, SUsPerRU: 1
   Queue size: 100, blocksize: 512, numBlocks: 230162304
   RAID Level: 1
   Autoconfig: Yes
   Root partition: Force
   Last configured as: raid0
Component label for /dev/dk3:
   Row: 0, Column: 1, Num Rows: 1, Num Columns: 2
   Version: 2, Serial Number: 2021071902, Mod Counter: 92472626
   Clean: No, Status: 0
   sectPerSU: 128, SUsPerPU: 1, SUsPerRU: 1
   Queue size: 100, blocksize: 512, numBlocks: 230162304
   RAID Level: 1
   Autoconfig: Yes
   Root partition: Force
   Last configured as: raid0
Parity status: clean
Reconstruction is 100% complete.
Parity Re-write is 100% complete.
Copyback is 100% complete.