All of lore.kernel.org
 help / color / mirror / Atom feed
From: Billy Transue <bill@black9.net>
To: reiserfs-list@namesys.com
Subject: Re: Problem with my HDD
Date: 31 May 2002 00:15:48 -0500	[thread overview]
Message-ID: <1022822148.334.18.camel@threshold> (raw)
In-Reply-To: <20020530091729.C3922@namesys.com>

On Thu, 2002-05-30 at 00:17, Oleg Drokin wrote:
> Hello!
> 
> On Thu, May 30, 2002 at 02:09:09AM +0200, Anders Widman wrote:
> 
> > > If you can I'd consider getting an image of the drive.  It may help with 
> > > data recovery later.  something like:
> > > dd if=/dev/sda1 of=/bigfilesystem/diskimage
> > I've  heard  of  something  called  dd_rescue,  but  "dd  if=/dev/sda1
> > of=/path/image  conv=sync,noerror"  should  do the trick. The sync and
> 
> Our attempts show that dd (even with conv=sync,noerror,notrunc) does not
> help and produces broken images, where no data inserted in image for sectors
> that cannot be read.
> 
> dd_rescue is shipped with SuSE.
> Also it can be obtained from here:
> http://www.garloff.de/kurt/linux/ddrescue/
> 
> > noerror   causes  the disk-copy to continue when there are read errors
> > and  fill in with blanks instead. If you don't do this you will end up
> 
> No, for some reason it does not fills the blanks.
> At least for us.
> 
> > with  offset  errors  -  the  image  will be shorter than the original
> > drive, and it would be impossible to fix.
> 
> This is also not true, it will be possible to fix, but that would be
> more expensive ;)
> 
> Bye,
>     Oleg

I've suffered a very similar problem and posted to the list earlier, I
did, dd_resuce -l dd.log /dev/hdd5 ./hdd5 and winded up w/ this:
dd_rescue: (info): ipos:         0.0k, opos:         0.0k,
xferd:         0.0k
                   errs:      0, errxfer:         0.0k,
succxfer:         0.0k
             +curr.rate:        0kB/s, avg.rate:        0kB/s,
avg.load:  0.0%

it never changed, the file created hdd5 was 65536 bytes large.  The log
file was empty.  Am I doing something wrong?  Any info would be
appreciated.  Thanks in advance.





  reply	other threads:[~2002-05-31  5:15 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-29 17:49 Problem with my HDD Cookie-Monster
2002-05-29 17:53 ` Anders Widman
2002-05-29 21:19 ` Kuba Ober
2002-05-29 23:45 ` Robert Brockway
2002-05-30  0:09   ` Re[2]: " Anders Widman
2002-05-30  5:17     ` Oleg Drokin
2002-05-31  5:15       ` Billy Transue [this message]
2002-05-31  8:29         ` Oleg Drokin
2002-05-30  5:14   ` Oleg Drokin
2002-05-30  5:49     ` Robert Brockway
2002-05-30 11:35     ` Re[2]: " Cookie-Monster
2002-05-30 11:58     ` Cookie-Monster
2002-05-30 13:35       ` Re[3]: " Anders Widman
2002-05-30 13:39       ` Re[2]: " Chris Mason
2002-05-30 13:59         ` Robert Brockway
2002-05-30  5:21 ` Oleg Drokin
     [not found]   ` <781752530.20020530134323@starfall.de>
     [not found]     ` <20020530155353.B1060@namesys.com>
2002-06-02 18:02       ` Re[2]: " Cookie-Monster
  -- strict thread matches above, loose matches on Subject: below --
2002-05-31 16:28 Dieter Nützel
2002-05-31 18:49 ` Billy Transue

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=1022822148.334.18.camel@threshold \
    --to=bill@black9.net \
    --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.