public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Iain Buchanan <iaindb@netspace.net.au>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] {OT} Recovering data from a formatted hard disk
Date: Wed, 01 Feb 2006 11:47:51 +0930	[thread overview]
Message-ID: <1138760271.9601.17.camel@orpheus> (raw)
In-Reply-To: <49bf44f10601311739l28ec25d0g87d0d73db0b82afa@mail.gmail.com>

On Tue, 2006-01-31 at 17:39 -0800, Grant wrote:
> 
> Almost everyone seems to agree that recovering data from a formatted
> drive is possible.  What is the process by which this is done?  I've
> read here that:
> 
> 1. The space between tracks contains historical data information.
> 
> and:
> 
> 2. There is a difference between a track written with a 0 and then
> overwritten with a 0 and a track written with a 1 and then overwritten
> with a 0.
> 
> Are these the two processes by which this data recovery is made possible?

They both rely on the fact that you can read what _was_ once written to
the hard drive by examining the spaces.  So that's one method.

The other method of recovering data is just to cat /dev/hda, but that
relies on the hd not being "wiped" (overwritten with 0's and 1's many
times in a semi-random fashion!).
-- 
Iain Buchanan <iain at netspace dot net dot au>

Never make anything simple and efficient when a way can be found to
make it complex and wonderful.

-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2006-02-01  2:23 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-31  1:03 [gentoo-user] {OT} Recovering data from a formatted hard disk Grant
2006-01-31  1:21 ` Mike Williams
2006-01-31  7:27 ` Stroller
2006-01-31  8:11   ` Iain Buchanan
2006-01-31 12:20     ` Michael Kintzios
2006-01-31 12:56     ` Dale
2006-01-31 13:13       ` Iain Buchanan
2006-01-31 13:22         ` Dale
2006-01-31 14:27         ` Richard Fish
2006-01-31 13:19       ` Schleimer, Ben
2006-01-31 13:31         ` Schleimer, Ben
2006-01-31 16:36         ` Alexander Skwar
2006-01-31 17:03         ` Uwe Thiem
2006-02-01  1:39           ` Grant
2006-02-01  2:17             ` Iain Buchanan [this message]
2006-02-01  8:11               ` Alexander Skwar
2006-02-01 16:42                 ` Richard Fish
2006-02-01 16:47               ` Grant
2006-02-01  6:22           ` Alexander Skwar
2006-02-02  0:56         ` Stroller
2006-01-31 15:32       ` Ted Ozolins
2006-01-31 14:05     ` Richard Fish
2006-01-31 16:32   ` Alexander Skwar
2006-02-02  0:59     ` Stroller
2006-02-02 11:26       ` Alexander Skwar
2006-01-31 16:31 ` Alexander Skwar
2006-02-01 18:27 ` Peter Volkov (pva)
2006-02-01 19:26   ` Alexander Skwar
2006-02-02  0:54   ` Stroller
2006-02-02 11:28     ` Alexander Skwar
2006-02-02 17:48       ` Stroller
2006-02-02 18:13         ` Alexander Skwar
2006-02-02 18:41         ` Chris Woods
2006-02-02  4:16   ` Grant
2006-02-02  4:41     ` Dale
2006-02-02 11:32       ` Alexander Skwar
2006-02-02 11:53         ` Dale
2006-02-02 17:59           ` Alexander Skwar
2006-02-02 18:20             ` Ian Kester-Haney
2006-02-02 12:06         ` Neil Bothwick
2006-02-02  4:56     ` Richard Fish
2006-02-02  9:58       ` Neil Bothwick
2006-02-02 11:29     ` Alexander Skwar

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=1138760271.9601.17.camel@orpheus \
    --to=iaindb@netspace.net.au \
    --cc=gentoo-user@lists.gentoo.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