GEOM_STRIPE Problems on Reboot

[Drew Tomlinson]

I posted the following on -questions but have not received any 
assistance.  I also have since tried compiling GEOM_STRIPE support in 
the kernel but get the same behavior (except that I can't perform the 
kldunload/load workaround).  I'm hoping someone here may be able to 
point me in the right direction

Thanks,

Drew

-------- Original Message --------

I just installed 5.4-RELEASE. I created a gstripe volume per the

example in the man page.  Googling revealed that I needed to load the 
geom_stripe module upon reboot so the volume can be created.  I added 
the following line to /boot/loader.conf:

geom_stripe_load="yes"

Now upon reboot, I get this output:

da0 at ahc0 bus 0 target 0 lun 0
da0: <SEAGATE SX19171W 9D32> Fixed Direct Access SCSI-2 device
da0: 11.626MB/s transfers (5.813MHz, offset 8, 16bit), Tagged Queueing 
Enabled
da0: 8683MB (17783112 512 byte sectors: 64H 32S/T 8683C)
da1 at ahc0 bus 0 target 2 lun 0
da1: <SEAGATE SX19171W 9D32> Fixed Direct Access SCSI-2 device
da1: 11.626MB/s transfers (5.813MHz, offset 8, 16bit), Tagged Queueing 
Enabled
da1: 8683MB (17783112 512 byte sectors: 64H 32S/T 8683C)
da2 at sbp0 bus 0 target 0 lun 0
da2: <Oxford 911G 0135> Fixed Simplified Direct Access SCSI-4 device
da2: 50.000MB/s transfers
da2: 76351MB (156368016 512 byte sectors: 255H 63S/T 9733C)
da3 at sbp0 bus 0 target 0 lun 1
da3: <Oxford 911G 0135> Fixed Simplified Direct Access SCSI-4 device
da3: 50.000MB/s transfers
da3: 114473MB (234441648 512 byte sectors: 255H 63S/T 14593C)
SMP: AP CPU #1 Launched!
GEOM_STRIPE: Device data created (id=896603271).
GEOM_STRIPE: Disk da0d attached to data.
GEOM_STRIPE: Disk da1d attached to data.
GEOM_STRIPE: Device data activated.
GEOM_STRIPE: Cannot add disk da0s1d to data (error=17).
GEOM_STRIPE: Cannot add disk da1s1d to data (error=17).
Mounting root from ufs:/dev/da0s1a

Then the machine comes up in single user mode.  At this point if I 
unload and reload geom_stripe, then the volume is created just fine and 
I can boot the system in full production mode.  Any ideas on why I'm 
seeing this behavior?  How can I fix it so that my machine reboots 
without incident?

Thanks,

Drew