Date: Tue, 31 Mar 2009 09:12:40 -0400 From: Juan Miscaro <jmiscaro@gmail.com> To: Ivan Voras <ivoras@freebsd.org> Cc: freebsd-questions@freebsd.org Subject: Re: Recovering a GEOM RAID0 array Message-ID: <d0626390903310612n5eb0ac98vc14b7ab3e5eef1f9@mail.gmail.com> In-Reply-To: <gqt48t$f77$4@ger.gmane.org> References: <d0626390903301221o701f762ao18269ae6e212affa@mail.gmail.com> <gqt0rm$64m$1@ger.gmane.org> <d0626390903310522w67f09292t5148334ee3cd2a2d@mail.gmail.com> <gqt3ei$f77$1@ger.gmane.org> <gqt48t$f77$4@ger.gmane.org>
next in thread | previous in thread | raw e-mail | index | archive | help
2009/3/31 Ivan Voras <ivoras@freebsd.org>:
> 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 be an easier way to do it: use "gstripe dump
> ad3" - it will write out its metadata. Use the manual (dd) approach if
> this doesn't work.
>
>
# gstripe dump ad3
Can't read metadata from ad3: Invalid argument.
Not fully done.
# gstripe dump ad1
Metadata on ad1:
Magic string: GEOM::STRIPE
Metadata version: 3
Device name: st0
Device ID: 3091204740
Disk number: 0
Total number of disks: 2
Stripe size: 4096
Hardcoded provider:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?d0626390903310612n5eb0ac98vc14b7ab3e5eef1f9>