All of lore.kernel.org
 help / color / mirror / Atom feed
From: Carl-Daniel Hailfinger <c-d.hailfinger.kernel.2004@gmx.net>
To: dan@ngenllc.com
Cc: matts@ksu.edu, reiserfs-list@namesys.com
Subject: Re: Need help recovering lost partitions
Date: Thu, 29 Jan 2004 00:35:32 +0100	[thread overview]
Message-ID: <40184744.1020301@gmx.net> (raw)
In-Reply-To: <20040128143848.27765.h003.c001.wm@mail.ngenllc.com.criticalpath.net>

dan@ngenllc.com wrote:

> So how can I scan the partition for the old
> superblocks?  gpart and parted weren't picking them up,
> but I know they were there.  And the 6GB of data it
> found is much less then the size of the partition
> (50GB), which makes me think that some data might still
> be there (i.e. only 100 * (6/50) % of the data could
> have been overwritten).

If you did reiserfsck --rebuild-tree --scan-whole-partition on the
unpartitioned hard drive, it is very likely that this reduced your chance
of rescueing some data to zero.

It all depends on how much money you're willing to spend. For starters, I
would recommend you to try the support offered by Namesys. Since they
wrote reiserfs they should have the best chance rescuing you data if it is
still on disk. If the data has already been overwritten by your actions,
you could try some data rescure company who claim to restore overwritten
data with a scanning tunneling microscope or somesuch.

The namesys support has helped a colleague of mine to restore all of his
data albeit some filenames were lost. The files themselves were
uncorrupted. And another big advantage of namesys is that they charge only
about 1/10th of the amount a commercial data rescue company would bill
you. (based on quotes from the web sites of the respective companies)


HTH,
Carl-Daniel


  parent reply	other threads:[~2004-01-28 23:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-28 22:38 Need help recovering lost partitions dan
2004-01-28 23:22 ` Matt Stegman
2004-01-28 23:35 ` Carl-Daniel Hailfinger [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-01-28 20:35 dan
2004-01-28 22:10 ` Matt Stegman
2004-01-28 22:36 ` Phil Frost

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=40184744.1020301@gmx.net \
    --to=c-d.hailfinger.kernel.2004@gmx.net \
    --cc=dan@ngenllc.com \
    --cc=matts@ksu.edu \
    --cc=reiserfs-list@namesys.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.