All of lore.kernel.org
 help / color / mirror / Atom feed
From: michael chang <thenewme91@gmail.com>
To: David Masover <ninja@slaphack.com>
Cc: PFC <lists@boutiquenumerique.com>,
	reiserfs-list@namesys.com, rudy@edsons.demon.nl
Subject: Re: recovering from "rm -rf"
Date: Fri, 5 Aug 2005 20:22:54 -0400	[thread overview]
Message-ID: <b14e81f0050805172275d01c26@mail.gmail.com> (raw)
In-Reply-To: <42F3F4A4.2050505@slaphack.com>

On 8/5/05, David Masover <ninja@slaphack.com> wrote:
> Rudy Zijlstra wrote:
> > David Masover wrote:
> >
> >> PFC wrote:
> >>
> >>
> >>>> 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.
> >>>
> >>
> >>
> >> Seems kind of a waste to buy a whole new drive, if it does end up being
> >> that simple.  I wonder if I couldn't ship this back to the manufacturer
> >> and have them do it?  I'm sure they have extras...
> >>
> >>
> >>
> > forget that idea, the extra's are bough by the recovery companies...
> >
> > In other words, its not cost effective for the manufacturers to keep
> > spare parts around.
> >
> > /Kick in open door
> > The thing you *should* have done is keep good backups, especially
> > considering the amount you are willing to pay to recover...
> 
> I'm not sure yet how much I'm willing to pay.  If the Namesys people can
> help me out, there will certainly be a donation headed their way, but
> I'm not sure yet if I want to spend $500 to $5000 on a recovery.  It's
> an academic question, anyway -- if it costs too much, I'll have to wait.

Most people I've seen, when the drive dies, they just buy a new one,
and forget about their old data.

> > No matter how you do it, no matter what type of RAID level you run,
> 
> Striping is fast, but not really RAID.

So this was a performance raid, not a backup raid?  Did you RAID on
the same drive?  o_O  [If memory serves me right, RAID/Striping only
gives better performance on multiple drives.]

> > nothing beats a backup on a separate medium, with an automated script to
> > make it every night (or more often if needed).
> > Kick in open door/
> 
> Indeed, a lesson learned.  I've got some sort of backup script
> somewhere, but I'm not sure exactly what it's backing up, or to where.
> It may have the really important stuff, but almost certainly won't have
> all the music and anime, so I'm still trying to recover Drive A.

Music and Anime?  Lol.  No wonder you're trying to recover it all. 
I'd suggest a data recovery company, all the same, before you damage
your computer completely.  And maybe consider using e.g. a backup -
two drives; while you have to store data twice, at least if one fails,
you'll have a backup [how in the world did you end up with two drives
dead anyways?!?].

> Similar drive, if it'd work.  But my manufacturer warns me that even
> identical-looking drives sometimes have different firmware.

In the manual, or over the phone?

> > What you can do is ask the manufacturer which drives are using the same
> > PCBs. You might get lucky.
> 
> (same PCBs and firmware.)  Thanks, I'll do that.

You'll be hard pressed to find a e-bay listing that lists the PCBs and
Firmware, per the components, though?  *shrugs*

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

  reply	other threads:[~2005-08-06  0:22 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
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 [this message]
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=b14e81f0050805172275d01c26@mail.gmail.com \
    --to=thenewme91@gmail.com \
    --cc=lists@boutiquenumerique.com \
    --cc=ninja@slaphack.com \
    --cc=reiserfs-list@namesys.com \
    --cc=rudy@edsons.demon.nl \
    /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.