From: PFC <lists@boutiquenumerique.com>
To: David Masover <ninja@slaphack.com>, michael chang <thenewme91@gmail.com>
Cc: reiserfs-list@namesys.com
Subject: Re: recovering from "rm -rf"
Date: Fri, 05 Aug 2005 23:36:29 +0200 [thread overview]
Message-ID: <op.su10y3q7th1vuj@localhost> (raw)
In-Reply-To: <42F3D760.7090008@slaphack.com>
> 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.
You probably fried the electronics... if the heads are still OK, you
could recover your data by exchanging the PCB from a brand new drive, with
the fried PCB of the old drive. You need some electronics skillz, but a
friend of mine did this (it was an adventure, as he had to find the same
drive as he had, from ebay, etc) and it worked for him... if something
that's not on the PCB is dead, well, you need a recovery company.
Or you could give $25 to Hans Reiser via his website for an answer ?
next prev parent reply other threads:[~2005-08-05 21:36 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
2005-08-05 21:39 ` David Masover
2005-08-05 21:36 ` PFC [this message]
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=op.su10y3q7th1vuj@localhost \
--to=lists@boutiquenumerique.com \
--cc=ninja@slaphack.com \
--cc=reiserfs-list@namesys.com \
--cc=thenewme91@gmail.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.