All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vitaly Fertman <vitaly@namesys.com>
To: Kristian Koehntopp <kris@xn--khntopp-90a.de>, reiserfs-list@namesys.com
Subject: Re: Hard errors, trying to recover
Date: Wed, 30 Jun 2004 18:02:05 +0400	[thread overview]
Message-ID: <200406301802.05840.vitaly@namesys.com> (raw)
In-Reply-To: <20040629193943.GA15481@p15104972.pureserver.info>

Hello,

On Tuesday 29 June 2004 23:39, Kristian Koehntopp wrote:
> I have a 160 GB disk that has at least one hard read-error.
>
> I tried reiserfsck'ing that disk, in order to salvage data on that disk by
> copying it to a safe location one last time. Unfortunately, reiserfsck
> --rebuild-tree runs into that read-error and stops, lecturing me on disk
> quality (I knew that!). Now I cannot even mount that disk, because
> reiserfsck zeroed root block 0 during the rebuild-tree.
>
> I am at the moment dd'ing that disk with conv=noerrors, hoping that I will
> get an image (which will be truncated by 4 GB, because my scratch disk is
> somewhat smaller than the source disk). I tried to reiserfsck
> --rebuild-tree the partial image, but I reiserfsck breaks down, because it
> is unable to read the last block of the images (it is a partial image).
>
> What can I do to salvage the data on my broken disk?

we deal with hardware problems only under www.namesys.com/support.html terms.

-- 
Thanks,
Vitaly Fertman


  reply	other threads:[~2004-06-30 14:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-29 19:39 Hard errors, trying to recover Kristian Koehntopp
2004-06-30 14:02 ` Vitaly Fertman [this message]
2004-06-30 14:45   ` Kristian Köhntopp
2004-06-30 15:16     ` Carl-Daniel Hailfinger
2004-06-30 15:59     ` Vitaly Fertman
2004-06-30 19:42       ` Kristian Köhntopp
2004-07-01  1:04         ` Redeeman
2004-07-01  6:23           ` Raymond A. Meijer
2004-07-01 10:10             ` Dieter Nützel

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=200406301802.05840.vitaly@namesys.com \
    --to=vitaly@namesys.com \
    --cc=kris@xn--khntopp-90a.de \
    --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.