Date: Tue, 31 Mar 2009 14:48:17 +0200 From: Ivan Voras <ivoras@freebsd.org> To: freebsd-questions@freebsd.org Subject: Re: Recovering a GEOM RAID0 array Message-ID: <gqt3ei$f77$1@ger.gmane.org> In-Reply-To: <d0626390903310522w67f09292t5148334ee3cd2a2d@mail.gmail.com> References: <d0626390903301221o701f762ao18269ae6e212affa@mail.gmail.com> <gqt0rm$64m$1@ger.gmane.org> <d0626390903310522w67f09292t5148334ee3cd2a2d@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig91971D4CFBCAE637053D10DF Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Juan Miscaro wrote: > This is the end of dmesg (the drives in question are ad1 and ad3): > GEOM_STRIPE: Device st0 created (id=3D3091204740). > GEOM_STRIPE: Disk ad1 attached to st0. > GEOM_STRIPE: Disk ad1 removed from st0. > GEOM_STRIPE: Device st0 destroyed. > GEOM_STRIPE: Device st0 created (id=3D3091204740). > GEOM_STRIPE: Disk ad1 attached to st0. Firstly, as you can see ad3 is never added. This can mean several things, of which the most probable is that its metadata has been destroyed. The messages after the second message is probably due to you opening the drives manually, bypassing gstripe, probably with the following commands. > # bsdlabel ad1 >=20 > # /dev/ad1: > 8 partitions: > # size offset fstype [fsize bsize bps/cpg] > a: 1250280640 16 4.2BSD 2048 16384 28552 > c: 1250280656 0 unused 0 0 # "raw" > part, don't edit > partition a: partition extends past end of unit > partition c: partition extends past end of unit > bsdlabel: partition c doesn't cover the whole unit! > bsdlabel: An incorrect partition c may cause problems for standard > system utilities >=20 > # bsdlabel ad3 >=20 > # /dev/ad3: > 8 partitions: > # size offset fstype [fsize bsize bps/cpg] > a: 625142432 16 4.2BSD 2048 16384 28552 > c: 625142448 0 unused 0 0 # "raw" part, > don't edit >=20 > These drives should appear to be identical. This is the wrong way to inspect your drives. If you did anything to the drives individually (i.e. bypassing gstripe) it's very likely you corrupted some data. I don't know if this is obvious to you so I'm saying it just in case. Inspect your drives with "diskinfo -v" to get information such as its size. What does "gstripe list" say? What does "sysctl -b kern.geom.confxml" say= ? 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")= =2E --------------enig91971D4CFBCAE637053D10DF Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFJ0hERldnAQVacBcgRAi8RAKCxCW7HJshNkduWDaAZb1abBtOeoACeL/Zk dp7VQji8WDtgwQpIp9sxPrs= =l/V2 -----END PGP SIGNATURE----- --------------enig91971D4CFBCAE637053D10DF--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?gqt3ei$f77$1>