From: Willy Tarreau <w@1wt.eu>
To: Al Boldi <a1426z@gawab.com>
Cc: linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFH] Partion table recovery
Date: Fri, 20 Jul 2007 07:35:27 +0200 [thread overview]
Message-ID: <20070720053526.GG943@1wt.eu> (raw)
In-Reply-To: <200707200813.03553.a1426z@gawab.com>
On Fri, Jul 20, 2007 at 08:13:03AM +0300, Al Boldi wrote:
> As always, a good friend of mine managed to scratch my partion table by
> cat'ing /dev/full into /dev/sda. I was able to push him out of the way, but
> at least the first 100MB are gone. I can probably live without the first
> partion, but there are many partitions after that, which I hope should
> easily be recoverable.
>
> I tried parted, but it's not working out for me. Does anybody know of a
> simple partition recovery tool, that would just scan the disk for lost
> partions?
The best one is simply "fdisk", because you can manually enter your
cylinders numbers. You have to find by hand the beginning of each partition,
and for this, you have to remember what filesystems you used and see how to
identify them (using a magic). Then with an hex editor, you scan the disk to
find such entries and note the possible sectors on a paper. Then comes fdisk.
You create the part, exit and try to mount it. If it fails, fdisk again and
try other values.
I've saved many disks that way, it may sound harder than it really is. It
should not take you more than half an hour to get the first part. Knowing
your approximate partitions size will help too.
Good luck!
Willy
next prev parent reply other threads:[~2007-07-20 5:35 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-20 5:13 [RFH] Partion table recovery Al Boldi
2007-07-20 5:20 ` Dave Young
2007-07-20 5:57 ` Dave Young
2007-07-20 11:29 ` [RFH] Partition " Al Boldi
2007-07-20 5:25 ` [RFH] Partion " James Lamanna
2007-07-20 7:00 ` Jan-Benedict Glaw
2007-07-20 11:29 ` [RFH] Partition " Al Boldi
2007-07-20 11:53 ` Anton Altaparmakov
2007-07-20 5:35 ` Willy Tarreau [this message]
2007-07-20 5:44 ` [RFH] Partion " Dave Young
2007-07-20 7:03 ` Jan Engelhardt
2007-07-20 11:29 ` [RFH] Partition " Al Boldi
2007-07-20 11:39 ` Jan-Benedict Glaw
2007-07-20 12:22 ` Al Boldi
2007-07-20 12:29 ` Rene Herman
2007-07-20 16:06 ` Theodore Tso
2007-07-21 17:54 ` Rene Herman
[not found] ` <20070722011141.GJ26752@thunk.org>
2007-07-22 4:10 ` Al Boldi
2007-07-22 16:28 ` Theodore Tso
2007-07-22 19:05 ` Al Boldi
2007-07-22 21:23 ` Indan Zupancic
2007-07-23 8:15 ` Rene Herman
2007-07-23 8:41 ` Jan-Benedict Glaw
2007-07-23 10:54 ` Rene Herman
2007-07-23 12:39 ` Rene Herman
2007-07-23 13:15 ` Jan-Benedict Glaw
2007-07-23 13:32 ` Rene Herman
2007-07-23 20:22 ` Bill Davidsen
2007-07-23 13:58 ` Theodore Tso
2007-07-24 4:08 ` Rene Herman
2007-07-22 9:11 ` Rene Herman
[not found] ` <20070722163934.GB20174@thunk.org>
[not found] ` <46A45A01.5050709@gmail.com>
2007-07-23 13:48 ` Theodore Tso
2007-07-24 3:41 ` Rene Herman
2007-07-20 6:47 ` [RFH] Partion " Jeffrey V. Merkey
2007-07-20 11:29 ` [RFH] Partition " Al Boldi
2007-07-20 7:35 ` [RFH] Partion " Anton Altaparmakov
2007-07-21 19:40 ` Willy Tarreau
2007-07-23 20:08 ` Bill Davidsen
2007-07-24 3:45 ` Rene Herman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070720053526.GG943@1wt.eu \
--to=w@1wt.eu \
--cc=a1426z@gawab.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).