GEOM_STRIPE: Cannot add disk da2c to st0 (error=17).
chris# at 1command.com
Tue May 5 12:08:13 UTC 2009
Hello, and thank you for your reply...
Quoting Holger Kipp <hk at alogis.com>:
> On Tue, May 05, 2009 at 02:48:00AM -0700, Chris H wrote:
>> I'm attempting to upgrade one of our servers to 6.4 (from 6.2)
>> Before doing so I need to stripe 3 identical drives on the
>> same SCSI port into one drive, the drives are on an LSI controller
>> with 2 ports:
>> However, when I attempt to stripe the 3 unused drives, I recieve an
>> error regarding da2:
>> gstripe label -v st0 /dev/da0 /dev/da1 /dev/da2
>> GEOM_STRIPE: Device st0 created (id=2607126992).
>> GEOM_STRIPE: Disk da0 attached to st0.
>> Metadata value stored on /dev/da0.
>> GEOM_STRIPE: Disk da1 attached to st0.
>> Metadata value stored on /dev/da1.
>> GEOM_STRIPE: Disk da2 attached to st0.
>> GEOM_STRIPE: Device st0 activated.
>> GEOM_STRIPE: Cannot add disk da2c to st0 (error=17).
>> Metadata value stored on /dev/da2.
>> I blanked the 3 drives prior to attempting any of this, and it's
>> on a fresh reboot. I'm afraid I don't know how to proceed. Is it
>> a problem with gstripe(8)? I /really/ need to stripe these drives
>> so as to upgrade the system.
> Can you check if you have any fdisk metadata on either of your disks?
> Especially as da0, da1, da2 are attached to st0 without problems,
> but then GEOM_STRIPE complains about da2c (which looks like a partition
I cheated, and went into sysinstall > custom > partition
chose each of da0, da1, and da2
pressed "f" then "no" then "yes". Which forced a "dangerously" dedicated
disk. I also chose "w" on all occasions, and each time the response indicated
Successfully written to disk. I then bailed out of sysinstall, then went
back, and deleted the partitions, and again, chose "w". Which also indicated
"Successfully written to disk". I then bailed out of sysinstall.
Having felt the disks were all now clean, I proceeded with the command:
gstripe label -v st0 /dev/da0 /dev/da1 /dev/da2
...well, you know the rest of the story. :)
Is this not a good (the best) direction to take?
Thank you again for your reply.
> Mind you, this is just a wild guess from my side ;-)
More information about the freebsd-stable