Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 26 Aug 1998 12:09:00 -0700 (PDT)
From:      Julian Elischer <julian@whistle.com>
To:        Mikhail Teterin <mi@video-collage.com>
Cc:        questions@FreeBSD.ORG, current@FreeBSD.ORG
Subject:   Re: recovering disk
Message-ID:  <Pine.BSF.3.95.980826115816.2391A-100000@current1.whistle.com>
In-Reply-To: <199808261803.OAA08562@xxx.video-collage.com>

next in thread | previous in thread | raw e-mail | index | archive | help

firstly

fdisk partitions cannot start at 0

usually they start either at 1 or at 64 or at the beginning of the 2nd
cylinder.
how did you make that drive?
different methids will have done differnt things.

the fdisk was possibly still there.. 
if so, it was the disklabel that was gone..

this is likely because it appears to have complained about  abad label
rather than a bad MBR.

julian


On Wed, 26 Aug 1998, Mikhail Teterin wrote:

> 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...

probably not....

> 
> 	sd1s1: type 0xa5, start 0, end = 4194057, size 4194058 
                                ^^^ buzz!

> 	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
> ?

several people have written such programs before.....
I guess we might find
references in the archives..

if a good one exists we probably should check it in..

what order were the
partitions?

would a dump fit in the swap partition?


> 
> 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,

you can just look for the superblock backups
unfortunatly, if the crash wrote a lot of data then it may have written
over the first parts of the filesystem so we don;t know how much you will
be able to recover....




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


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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.95.980826115816.2391A-100000>