Re: [Bug-ddrescue] 250gig error... out of nowhere.

[Scott Dwyer]

Niklas,

The first thing you might want to do is run ddrescuelog with the -t (--show-status) option. In your case:
ddrescuelog -t nsclone.log

I see you still have the -n (--no-split) in your command line. Look at the results from ddrescuelog to see if that large 200+gig section is marked as non-split. If it is, removing the -n from your command will allow ddrescue to attempt to break down the error into smaller chunks. However, see what I say about the input position below (as Paul Daniels pointed out in his reply). You are trying to go after the last big chunk yet, and just removing the -n would cause any previous non-split areas (possibly 20,000+ in your case) to be done first unless you tell it where to read.

You should also look at your logfile to try to find the big error (by the sound of it, it might be at the end of the logfile), and get the offset position and size so you can use the -i (--input-position=) option to manually tell it to read the area you wish. If it is recorded as a big error, you would have to use the -r (--retries=) option to get it to try again (otherwise ddrescue will just report finished and exit right away). I would choose a value of 1 for the retry. Also, this is where having the proper input offset really comes in, as if you don't specify it, ddrescue will retry all the errors from the beginning, going through the 20,000+ errors you already encountered before getting to the big area you are still trying to get.

In all of this, also try powering down the computer and removing power from the drive for awhile, maybe more than once. Maybe you could get lucky and it will read again. Or maybe it won't.

Best of luck,

Scott

On 11/4/2013 9:17 PM, Niklas Swan wrote:

Hi Antonio / DDrescue community,

Just wanted to say thanks for helping me out in the early stages of my recovery, now I've reached (hopefully not) the end of it and I have a question or two.

so. after the first 100gig it sped up from 20gig a day to 60gig a day, and ran that way up until 501 gigs. this is where it gets fun.

so, my computer was in the office. someone in my office borrowed my laptop charger when I wasn't there, so when I viewed my computer via VNC I saw it had 20 minutes battery, stopped the recovery and shut down my computer.

so the next day I started it up and it was going about 200kb again, so back to around 20gig a day. I was not happy, but I figured it would pick up.

then BOOM, error size shot up from 10gig to 244gig and was like, "finished!". Fail.

I've tried a bunch of different commands, like attempting to run it backwards, direct mode (doesn't work on mac) but all of them either don't grab any data, or its just like "finished" and I'm like... no your not.

here's some info:

# Rescue Logfile. Created by GNU ddrescue version 1.17

# Command line: ddrescue -f -n -c 1 /dev/rdisk3 /dev/rdisk1 nsclone.log

# current_pos  current_status

0xAEAB74B400     +

GNU ddrescue 1.17

Press Ctrl-C to interrupt

Initial status (read from logfile)

rescued:   506054 MB,  errsize:    244 GB,  errors:   20248

Current status

rescued:   506054 MB,  errsize:    244 GB,  current rate:        0 B/s

   ipos:   750200 MB,   errors:   20248,    average rate:        0 B/s

   opos:   750200 MB,    time since last successful read:       1 s

Finished 

I tried starting it at 550gi, no dice... still finished.

so Questions:

is there any other DDrescue commands I can try to get the rest of the data off? 

(I refuse to believe 233gig was dead like that)

Do you think my coworker just gorked the last 250gigs of my drive?

if so, do you think I should seek some kind of revenge?

And Finally, as my new disk image mounts, do I need to use any further recovery tools to improve the quality of the data?

Thanks yall!

Niklas.

_______________________________________________
Bug-ddrescue mailing list
address@hidden
https://lists.gnu.org/mailman/listinfo/bug-ddrescue