From owner-freebsd-questions@FreeBSD.ORG Thu Feb 14 20:41:10 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 99D9A16A46B for ; Thu, 14 Feb 2008 20:41:10 +0000 (UTC) (envelope-from jd1987@borozo.com) Received: from smtp.3dresearch.com (dorabella.3dresearch.com [66.167.251.2]) by mx1.freebsd.org (Postfix) with ESMTP id 8013313C458 for ; Thu, 14 Feb 2008 20:41:10 +0000 (UTC) (envelope-from jd1987@borozo.com) Received: from fracasso.3dresearch.com (c-71-61-128-39.hsd1.pa.comcast.net [71.61.128.39]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by vmail.3dresearch.com (Postfix) with ESMTP id 3A23752409 for ; Thu, 14 Feb 2008 15:41:09 -0500 (EST) Received: from fracasso.3dresearch.com (fracasso.3dresearch.com [10.61.70.2]) by fracasso.3dresearch.com (Postfix) with ESMTP id 8FBCE17016 for ; Thu, 14 Feb 2008 15:41:08 -0500 (EST) From: Joe Demeny To: freebsd-questions@freebsd.org User-Agent: KMail/1.9.7 References: <200802140108.35844.jd1987@borozo.com> <20080214170411.GC86111@gizmo.acns.msu.edu> In-Reply-To: <20080214170411.GC86111@gizmo.acns.msu.edu> MIME-Version: 1.0 Content-Disposition: inline X-KMail-Filtered: 120313 Date: Thu, 14 Feb 2008 15:41:05 -0500 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200802141541.06233.jd1987@borozo.com> Subject: Re: Trying to recover data from FreeBSD 4.11 system X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Feb 2008 20:41:10 -0000 On Thursday 14 February 2008 12:04:11 pm you wrote: > On Thu, Feb 14, 2008 at 01:08:35AM -0500, Joe Demeny wrote: > [...] > Use fdisk to find out how it sees the drive. Do fdisk ad1 > and check out what it says. Especially look to see what slices > that fdisk thinks it has. Maybe there is only an s1 active > with anything in it. That would be easiest and very common. > > Then use bsdlabel to look at what partitions are defined in any > of the slices. do ad1s1 (for slice 1, ad1d2 as well > if there is a slice 2 being used, etc) > From root, do bsdlabel ad1d1 and see what partitions are defines. > Remember that partition 'c' is not a real partition, but a label to > define the whole slice to the system (it will have a type of 'unused') > and that in most cases partition 'b' is used for swap (and will have > a type of 'swap'), though it does not have to be swap. > The other partitions; a, d, e, f, g, h, could be real partitions with > something on them. Almost certainly the 'a' partition will be root > on a bootable slice. It turns out that I mixed up my drives. I found the boot drive - it could not boot with my old custom kernel (unknown processor class...). I fell back on kernel.GENERIC, which booted - to a point. It seems to bog down when it tries to recognize the keyboard. I guess at this point my choices are: 1) build a new 4.x kernel on the new hardware 2) find a working old computer and try my boot drive. Thank you all for your help... -- Joe Demeny