Hi gang,
I'm running a remote 6.2 system which recently got shut down
unexpectedly (tower was physically nudged and apparently lost power).
I am running a 2-disk striped array with the geom_stripe.ko module.
So my fstab line is
/dev/stripe/st0a/data ufs rw,acls 2
2009/3/31 hv :
>
> Am 30.03.2009 um 21:21 schrieb Juan Miscaro:
>
> Hi gang,
>
> I'm running a remote 6.2 system which recently got shut down
> unexpectedly (tower was physically nudged and apparently lost power).
> I am running a 2-disk striped array with the geo
2009/3/31 Ivan Voras :
> Juan Miscaro wrote:
>> Hi gang,
>>
>> I'm running a remote 6.2 system which recently got shut down
>> unexpectedly (tower was physically nudged and apparently lost power).
>> I am running a 2-disk striped array with the geom_strip
2009/3/31 Ivan Voras :
> Ivan Voras wrote:
>
>> If "gstripe list" doesn't mention ad3, you need to establish what
>> happened to metadata on ad3. Try extracting the last sector from ad3 by
>> hand (using dd) into a file and inspect it (send output of "hd filename").
>
> I just noticed there could b
2009/3/31 Ivan Voras :
> Juan Miscaro wrote:
>
>> This is the end of dmesg (the drives in question are ad1 and ad3):
>
>> GEOM_STRIPE: Device st0 created (id=3091204740).
>> GEOM_STRIPE: Disk ad1 attached to st0.
>> GEOM_STRIPE: Disk ad1 removed from st0.
>
2009/3/31 Ivan Voras :
> Juan Miscaro wrote:
>
>>> What does "gstripe list" say? What does "sysctl -b kern.geom.confxml" say?
>>
>> 'gstripe list' does not return any output at all.
>>
>> Output to the sysctl command is attach
2009/3/31 Ivan Voras :
> Juan Miscaro wrote:
>
>>> It looks like you created a both a fdisk partition table and a bsdlabel
>>> partition table on the ad3 drive. If so, your data is probably already
>>> corrupted.
>>
>> What is a generic configuration
