GEOM_STRIPE Problems on Reboot
drew at mykitchentable.net
Wed Jul 13 17:01:07 GMT 2005
I apologize if anyone sent replies and they were rejected. It appears I
had a hostname problem on my box and thus, postfix was rejecting all
mail to me. All is working again. Please resend any reply you may have
made. I'd *REALLY* like to get this resolved before I go on vacation
next week. :)
On 7/12/2005 9:35 AM Drew Tomlinson wrote:
> On 7/11/2005 11:00 AM Drew Tomlinson wrote:
>> 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:
>> 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?
> I also tried compiling the kernel with geom_stripe as an option. I
> get the same error except that now I can't unload/reload the kernel
> module to get my system running.
> So now I'm really stuck. Any help is appreciated.
Visit The Alchemist's Warehouse
Magic Tricks, DVDs, Videos, Books, & More!
More information about the freebsd-questions