From owner-freebsd-fs@FreeBSD.ORG  Fri May 25 22:37:01 2012
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Delivered-To: freebsd-fs@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 1DC24106564A;
	Fri, 25 May 2012 22:37:01 +0000 (UTC) (envelope-from mahan@mahan.org)
Received: from ns.mahan.org (ns.mahan.org [67.116.10.138])
	by mx1.freebsd.org (Postfix) with ESMTP id EA2AB8FC15;
	Fri, 25 May 2012 22:37:00 +0000 (UTC)
Received: from gypsy.mahan.org (localhost [127.0.0.1])
	by ns.mahan.org (8.14.4/8.14.4) with ESMTP id q4PMaxnI053777;
	Fri, 25 May 2012 15:36:59 -0700 (PDT) (envelope-from mahan@mahan.org)
Message-ID: <4FC0098C.9060107@mahan.org>
Date: Fri, 25 May 2012 15:37:00 -0700
From: Patrick Mahan <mahan@mahan.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6;
	rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: Matthew Seaman <matthew@FreeBSD.org>
References: <4FBFEF94.4020407@mahan.org> <4FC002CF.2080702@FreeBSD.org>
In-Reply-To: <4FC002CF.2080702@FreeBSD.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: freebsd-fs@FreeBSD.org
Subject: Re: GEOM: ada0: corrupt or invalid
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
	<mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
	<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 25 May 2012 22:37:01 -0000

On 5/25/12 3:08 PM, Matthew Seaman wrote:
> On 25/05/2012 22:46, Patrick Mahan wrote:
>> But the question is -  "Is this recoverable?  Or should we just
>> re-install everything from scratch?"
> 
> Re-install.  You can't use dd(1) to copy a disk image to a smaller
> physical drive: the disk size is encoded in various structures on disk
> and used at boot time; copying a filesystem with dd(8) and  truncating
> it (even if the used space is less than the target partition size) just
> doesn't work.
> 
> If you have work you've done on the original disk images that you'ld
> like to copy to the new ones, then use a file-system level copy program.
> There are any number of suitable candidates, most of which have the
> ability to write across a network link if needed:
> 
>    * dump(8) and restore(8)
> 
>    * rsync(1)
> 
>    * tar(1)
> 
>    * find(1) and cpio(1)
> 
> Even cp(1).
> 
> 	Cheers,
> 
> 	Matthew
> 

Thanks,

As I expected, it was chock gun, aim at foot, pulled the trigger....

Re-installing now.

Patrick