From owner-freebsd-questions@FreeBSD.ORG Thu Feb 14 20:46:26 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 0ACBD16A420 for ; Thu, 14 Feb 2008 20:46:26 +0000 (UTC) (envelope-from tundra@tundraware.com) Received: from ozzie.tundraware.com (ozzie.tundraware.com [75.145.138.73]) by mx1.freebsd.org (Postfix) with ESMTP id AFD7B13C45B for ; Thu, 14 Feb 2008 20:46:25 +0000 (UTC) (envelope-from tundra@tundraware.com) Received: from [192.168.0.2] (viper.tundraware.com [192.168.0.2]) (authenticated bits=0) by ozzie.tundraware.com (8.14.2/8.14.2) with ESMTP id m1EKkJ0M001971 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES256-SHA bits=256 verify=NO) for ; Thu, 14 Feb 2008 14:46:19 -0600 (CST) (envelope-from tundra@tundraware.com) Message-ID: <47B4A896.4060603@tundraware.com> Date: Thu, 14 Feb 2008 14:46:14 -0600 From: Tim Daneliuk Organization: TundraWare Inc. User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) MIME-Version: 1.0 To: FreeBSD Mailing List References: <200802140108.35844.jd1987@borozo.com> <20080214170411.GC86111@gizmo.acns.msu.edu> <200802141541.06233.jd1987@borozo.com> In-Reply-To: <200802141541.06233.jd1987@borozo.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-tundraware.com-MailScanner-Information: Please contact the ISP for more information X-tundraware.com-MailScanner: Found to be clean X-tundraware.com-MailScanner-From: tundra@tundraware.com X-Spam-Status: No 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 Reply-To: tundra@tundraware.com List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Feb 2008 20:46:26 -0000 Joe Demeny wrote: > 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... > Another possible path: Boot Freesbie or PC-BSD from CD-ROM and mount your old drives from there. It might take running an fsck to clean up the old filesystems (depending on whether or not you clobbered them while trying to get this all to work). 'Just a thought - I take no responsibility if you hose your data though :) -- ---------------------------------------------------------------------------- Tim Daneliuk tundra@tundraware.com PGP Key: http://www.tundraware.com/PGP/