From owner-freebsd-current@FreeBSD.ORG  Wed Nov  3 06:26:59 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id C251E16A4CE
	for <freebsd-current@freebsd.org>;
	Wed,  3 Nov 2004 06:26:59 +0000 (GMT)
Received: from ox.eicat.ca (ox.eicat.ca [66.96.30.35])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 8398243D5D
	for <freebsd-current@freebsd.org>;
	Wed,  3 Nov 2004 06:26:59 +0000 (GMT)
	(envelope-from dgilbert@dclg.ca)
Received: from [66.96.20.59] (H59.C20.B96.tor.eicat.ca [66.96.20.59])
	by ox.eicat.ca (Postfix) with ESMTP id 96896C746
	for <freebsd-current@freebsd.org>;
	Wed,  3 Nov 2004 01:26:58 -0500 (EST)
Message-ID: <41887A33.2060608@dclg.ca>
Date: Wed, 03 Nov 2004 01:26:59 -0500
From: David Gilbert <dgilbert@dclg.ca>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.1) Gecko/20040707
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: freebsd-current@freebsd.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: More running-with-scissors and fsck.
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Nov 2004 06:26:59 -0000

Well... the recoverdisk is a cool tool.  I can see it coming in handy 
many times.  While there isn't much documentation, I've tended to use it 
by creating a vnode md disk of exactly the right size to recover the 
partition in question.

And I have a problem now.  recover disk finishes fine.  In fact, of the 
40G disk, it only can't recover about 210K.  That's a tiny fraction of 
1% unrecoverd.

However, it's all right around something key.  When I run fsck on the 
recovered image, fsck continuously complains that it can't create 
lost+found.

On the origional disk, of the 210K that's bad, most of it is near the 
start of the partition.  I suspect inode 1 and friends are not recovered 
... and thus all zeroed in the new md partition.

So... 99.99% of the data is there in good form.  How do I recover this 
... force a root to exist?

create an identical partion, newfs it and blindly copy the first 200 or 
so K?

Need someone who knows something about the structure I'm stomping on.

Dave.