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 16:57:32 -0400	[thread overview]
Message-ID: <b14e81f0050805135739c94933@mail.gmail.com> (raw)
In-Reply-To: <42F3C73B.9040808@slaphack.com>

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.

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
"dead" hard drive usually may be usable, but using one is extremely
dangerous (read: you're best off throwing it away, because any data
stored on it would have to have a backup on another e.g. hard drive
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.

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

  reply	other threads:[~2005-08-05 20:57 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 [this message]
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
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=b14e81f0050805135739c94933@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.