From owner-freebsd-current  Wed Aug 26 11:04:51 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id LAA14003
          for freebsd-current-outgoing; Wed, 26 Aug 1998 11:04:51 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from www.video-collage.com (www.video-collage.com [206.15.171.132])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA13980;
          Wed, 26 Aug 1998 11:04:47 -0700 (PDT)
          (envelope-from mi@xxx.video-collage.com)
Received: from xxx.video-collage.com (mi@xxx.video-collage.com [199.232.254.68])
	by www.video-collage.com (8.8.5/8.8.5) with ESMTP id OAA22178;
	Wed, 26 Aug 1998 14:02:35 -0400 (EDT)
Received: (from mi@localhost)
	by xxx.video-collage.com (8.8.8/8.8.7) id OAA08562;
	Wed, 26 Aug 1998 14:03:54 -0400 (EDT)
	(envelope-from mi)
From: Mikhail Teterin <mi@video-collage.com>
Message-Id: <199808261803.OAA08562@xxx.video-collage.com>
Subject: recovering disk
To: questions@FreeBSD.ORG, current@FreeBSD.ORG
Date: Wed, 26 Aug 1998 14:03:54 -0400 (EDT)
X-Face: 
	%UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w<gv/&E-lL7twZCT8B~/PA4|\t$ti+22K">
		 hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli"<kcG^EOVih
		 y+z3/UR{6SCQ
X-Mailer: ELM [version 2.4ME+ PL35 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Ok, so woke up in the morning to find my machine hanging:
	FreeBSD 3.0-CURRENT #0: Wed Aug 19 23:41:32 EDT 1998

Upon cold reset (soft one did not work) one of the disks had an
invalid partition table (No magic). The disk is 2Gb Barracuda and
had one slice in use: sd1s1 with sd1s1b being a 64Mb swap and sd1s1e
being my home directory. I also had "dumpon" set to save crash onto
the sd1s1b and suspect that this is the reason for this disaster...

fdisk let me make the partition table, but I do not think I made it
right because my subsequent attempts to `disklabel' result in the
following being logged:

	sd1s1: type 0xa5, start 0, end = 4194057, size 4194058 
	sd1s1: C/H/S start 0/0/0 (4294967295) != start 0: invalid
	sd1s1: C/H/S end 995/241/44 (10605407) != end 4194057: invalid
	sd1s2: type 0x0, start 3804688384, end = 3314409471, size 3804688384 
	sd1s2: C/H/S start 994/240/21 (10594692) != start 3804688384: invalid
	sd1s2: C/H/S end 994/240/18 (10594689) != end 3314409471: invalid
	sd1s3: type 0x0, start 0, end = 4294967295, size 0 
	sd1s3: C/H/S start 0/240/0 (10559) != start 0: invalid
	sd1s4: type 0xa5, start 1, end = 4193639, size 4193639 
	sd1s4: C/H/S end 457/10/44 (4866619) != end 4193639: invalid
	sd1: cannot find label (no disk label)
	sd1s1: cannot find label (no disk label)
	sd1: ILLEGAL REQUEST asc:21,0 Logical block address out
		of range field replaceable unit: 3 sks:cf,2
	sd1s4: cannot find label (no disk label)

I'm wondering, if I can write a program which will:
	1) read /dev/rsd1 to
	2) find the beginning of the file-system partition and
	3) write it out (all the way to the end) as a separate file, which
	4) vn-mechanism will let me access and get to my files
?

Or may be a program can be written to wonder through the /dev/sd1, find the
correct parameters (with some human assistance/guessing) for fdisk and disklabel?

I'm quite sure my data is intact on the disk and it is only its beginning that's
hosed. Thanks in advance for your ideas and suggestions. Yours,

	-mi

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message