On 7/14/2005 7:57 AM Pertti Kosunen wrote:
Drew Tomlinson wrote:
So where in the boot sequence is GEOM_STRIPE loaded? I'm starting to
suspect it's being loaded twice. I have it in /boot/loader.conf
which is where I thought it should be. Is there anywhere else to check?
If you have GEO
Drew Tomlinson wrote:
So where in the boot sequence is GEOM_STRIPE loaded? I'm starting to
suspect it's being loaded twice. I have it in /boot/loader.conf which
is where I thought it should be. Is there anywhere else to check?
If you have GEOM_STRIPE in kernel do you have to load it from
On 7/14/2005 5:30 AM Giovanni P. Tirloni wrote:
Drew Tomlinson wrote:
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).
G
Drew Tomlinson wrote:
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=1
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 di
