Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 5 May 2009 12:13:01 +0200
From:      Holger Kipp <hk@alogis.com>
To:        Chris H <chris#@1command.com>
Cc:        freebsd-stable@freebsd.org
Subject:   Re: GEOM_STRIPE: Cannot add disk da2c to st0 (error=17).
Message-ID:  <20090505101301.GA31143@intserv.int1.b.intern>
In-Reply-To: <20090505024800.tk0saqntsgk8kk8c@webmail.1command.com>
References:  <20090505024800.tk0saqntsgk8kk8c@webmail.1command.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, May 05, 2009 at 02:48:00AM -0700, Chris H wrote:
> Greetings,
> 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
entry)...

Mind you, this is just a wild guess from my side ;-)

Regards,
Holger



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090505101301.GA31143>