Re: [Bug-ddrescue] Slowness during recovery

[colo]

Ouch. I feel really bad for your experience of it. But it's good to know what did happen.

As I have been trying to run Diskwarrior on it for almost two days before I started ddrescue 

I fear that running it this long will do the same thing soon. 

So I turned it off for now to let it cool a bit. 

My ears are open as well right now. 

On Mon, Dec 22, 2008 at 4:53 PM, James W. Watts <address@hidden> wrote:

Here's your answer...

It never got any faster. Unfortunately, after getting back only 7GB of the 500GB, the drive ultimately experienced internal, mechanical failure (i.e. very loud clicking). Repeated attempts to resume were futile because the system would not recognize the drive drive following the internal failure. And now the next stop is a pro data recovery service which will charge hundreds/thousands to get the data back.

I can't help but feel that this could have been prevented if there were some way to make ddrescue jump past large chunks of bad spots. I thought that was how ddrescue was supposed to work. Instead, I just experienced ddrescue bogging down at the first bad sector(s) it encountered. And there it remained until the drive gave up and died completely.

Really, what could I have done differently? Please educate me.

James

---

From: colo <address@hidden>
To: address@hidden
Sent: Monday, December 22, 2008 2:50:26 PM
Subject: Re: [Bug-ddrescue] Slowness during recovery

Regarding the post from James W. Watts

I am curious to hear if it ever went any faster. 

I started today around 11:00 and at 2:00 I have a measly 32megs from a 500 gig 260 used Western Digital piece o crap. 

I swapped it into a new shell and sit here on a macbook pro running ddrescue 1.9 using this as my command

sudo ./ddrescue -B -n -v -r1 /dev/disk1 /Volumes/LaCie/testtwo/savepleasetwo.dmg savepleasetwo.log

Log file

Initial status (read from logfile)

rescued:   25857 KiB,  errsize:       0 B,  errors:       0

Current status

rescued:   31170 KiB,  errsize:       0 B,  current rate:     2148 B/s

   ipos:   31170 KiB,   errors:       0,    average rate:     2607 B/s

   opos:   31170 KiB

Copying data...

With 0 errors what is up with it's current speed? Did I do something wrong? 

It's transferring the data to a Lacie Raid 1 terabyte drive as firewire from the WD hd via usb 2.0

Either way I am ultra happy to find a tool that seems to work compared to diskwarrior and the like

Hello all,

I kicked off a recovery this morning of a 200GB IDE hard drive. I issued the 

following command:

sudo ddrescue -v -n /dev/sdb /media/wd500gb/blc.img /media/wd500gb/blc.log

As you can see below, it is going very slowly. After running all day, it has 

recovered less than 2GB from the drive. Please tell me what I am doing wrong. I 

have started and stopped ddrescue several times and rebooted, unplugged/plugged 

the drives several times, too. But it continues to be slow.

I keep waiting for ddrescue to just leapfrog past the bad area(s) it is 

obviously stuck in, but it just keeps slogging away. How can I make it go 

faster?

At this rate it would take months for the drive to finish recovery.

Thank you,

James