All of lore.kernel.org
 help / color / mirror / Atom feed
From: michael chang <thenewme91@gmail.com>
To: David Masover <ninja@slaphack.com>
Cc: reiserfs-list@namesys.com
Subject: Re: recovering from "rm -rf"
Date: Fri, 5 Aug 2005 17:27:35 -0400	[thread overview]
Message-ID: <b14e81f00508051427254bb32@mail.gmail.com> (raw)
In-Reply-To: <42F3D760.7090008@slaphack.com>

On 8/5/05, David Masover <ninja@slaphack.com> wrote:
> michael chang wrote:
> > On 8/5/05, David Masover <ninja@slaphack.com> wrote:
> >
> >>I've got a Reiser4 partition which I just moved (mv) a bunch of stuff
> >>off of, onto another drive.  The other drive died immediately after.
> >>
> >>I'm trying to repair the other drive, and to find any backups, but is
> >>there a reasonable chance to recover from the good drive?  Maybe force
> >>fsck.reiser4 to rebuild stuff... somehow?  It's sort of the equivalent
> >>of an "rm -rf".
> >
> >
> > I have no idea what you're trying to say; can you identify your drives
> > by e.g. Drive A and Drive B?  However, I've heard that Spinrite
> > (grc.com) is known to be pretty good at drive recovery, and supposedly
> > compatable with Linux partitions.  Requires an i386 compatable
> > machine, and I believe you need Windows to write the diskette/iso
> > which you can boot the recovery system from.  Haven't tried it though.
> 
> I could do that, but this is Reiser4.  Does anyone but Namesys support
> recovery from Reiser4 yet?

No clue.  They'll be able to tell you, for $25, from what I've heard.

> > What are you trying to do?  Format a broken hard drive so you can
> > write to it again, or recover data you deleted unintentionally?  A
> 
> Sort of both.
> 
> Drive A is a 500 gig striped RAID.  Drive B is a 200 gig IDE drive.  I
> mv'ed all my data (about 100 gigs) from drive A to drive B.  Drive B
> then had its power plug fall out (don't ask me how I managed that), I
> plugged it back in (stupid!) -- there was a spark -- drive B now won't
> spin up, and drive A is essentially "rm -rf"ed.

Well, most filesystems [I don't know for sure about Reiser4] will not
immediately clear out unused data.  However, if Drive A has been
running for a while post "rm -rf" and has some sort of repacker
enabled (I think they haven't implemented it yet or it was removed in
recent versionf of Reiser4) then the data could be all gone. 
Otherwise, I suppose if you had a backup of the metadata [which you
probably don't], you could try recovering from that...

As a note for the Power Plug + Sparks -- in the future, if it falls
out, unplug BOTH ends of the cord, then plug in the end that is
connected to the device FIRST, then the power socket/source SECOND. 
This goes for _ALL_ electronic devices, and will save you a lot of
hassle.  Paranoid people will also unplug electronics during a
thunderstorm/rolling blackouts/brownouts, and get a UPS system.

> > anyways, so you shouldn't use it).  For all you know, the drive could
> > have died because the internals wore out/broke, or because your cable
> > died/broke/etc.
> 
> I'm guessing that the internals did break, so I think that a recovery
> service would probably be able to recover 100% of my data (as an image),
> but only after replacing some parts, or even pulling the whole thing
> apart in a cleanroom.  This would cost at least $300-500, and if it goes
> to the cleanroom, probably $700 and up.

Considering the situation, most likely you shocked (e.g. with static
electricity or from that AC)  the motor and head and whatnot, although
if you're lucky, the spindle containing your data will be untouched.
In that case, a data recovery center only has to take it apart, move
the spindle to an identical drive, and put it back in the machine
(hopefully, without shocking it a second time).  As for drive A, you
can ask if there is some hack to get an older version of the metadata.
 *shrugs*

> By the way, do you know any good data recovery services?

Not that I've used.  What area [e.g. country, metro area, etc.]

-- 
~Mike
 - Just my two cents
 - No man is an island, and no man is unable.

  reply	other threads:[~2005-08-05 21:27 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-05 17:23 Reiser4progs-1.0.4-1 issues with gcc-4.0.1 Stef van der Made
2005-08-05 17:27 ` Vladimir V. Saveliev
2005-08-05 20:08   ` recovering from "rm -rf" David Masover
2005-08-05 20:57     ` michael chang
2005-08-05 21:17       ` David Masover
2005-08-05 21:27         ` michael chang [this message]
2005-08-05 21:39           ` David Masover
2005-08-05 21:36         ` PFC
2005-08-05 21:44           ` Aaron D. Ball
2005-08-05 21:52             ` PFC
2005-08-05 23:03             ` David Masover
2005-08-07  0:01               ` Aaron D. Ball
2005-08-07  7:16                 ` Rudy Zijlstra
2005-08-05 22:28           ` David Masover
2005-08-05 22:59             ` Rudy Zijlstra
2005-08-05 23:22               ` David Masover
2005-08-06  0:22                 ` michael chang
2005-08-06  1:06                   ` David Masover
2005-08-06  1:22                     ` michael chang
2005-08-06  7:37                 ` Hans Reiser
2005-08-07  0:06                   ` David Masover
2005-08-07 21:33                     ` michael chang
2005-08-08  6:05                     ` Hans Reiser

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=b14e81f00508051427254bb32@mail.gmail.com \
    --to=thenewme91@gmail.com \
    --cc=ninja@slaphack.com \
    --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.