From owner-freebsd-fs@FreeBSD.ORG Fri Jul 26 10:11:06 2013 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 09E8C1C4 for ; Fri, 26 Jul 2013 10:11:06 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 53A792015 for ; Fri, 26 Jul 2013 10:11:04 +0000 (UTC) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id NAA23771; Fri, 26 Jul 2013 13:10:56 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1V2ezA-000Hmv-GQ; Fri, 26 Jul 2013 13:10:56 +0300 Message-ID: <51F24AF8.5070106@FreeBSD.org> Date: Fri, 26 Jul 2013 13:10:00 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130708 Thunderbird/17.0.7 MIME-Version: 1.0 To: Kirk Richard Holz Subject: Re: Trying to recover 2-element zfs striped (raid0) filesystem References: <1b756c89576eb509d1197c4d9ab66fea@kirkholz.com> In-Reply-To: <1b756c89576eb509d1197c4d9ab66fea@kirkholz.com> X-Enigmail-Version: 1.5.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-fs@FreeBSD.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Jul 2013 10:11:06 -0000 on 26/07/2013 11:33 Kirk Richard Holz said the following: > When the drive's GPT partition table was corrupted it apparently picked up the > backup partition table, which wasn't current. I'm not sure how that happened. I'd recommend that you do not do any destructive actions. Then try to recall how the disk was partitioned. Then carefully re-create its partitioning setup. If you do everything right your data should be intact and accessible. It would be wise to make a full disk copy of the disk before doing anything with it. -- Andriy Gapon