You are not logged in.
I've been trying to create an image of a friends corrupted hd (the drive it self seems fine but the partition table is pretty messed up) using ddrescue with no options set and it's taking forever.
Here's the last output before I stopped it:
rescued: 927535 kB, errsize: 10285 kB, current rate: 16384 B/s
rescued: 927600 kB, errsize: 10285 kB, current rate: 0 B/s
ipos: 937885 kB, errors: 256, average rate: 13076 B/s
opos: 937885 kB, time since last successful read: 1 s
Copying non-tried blocks...
This was running for 20 hours or so. @ this rate it'll take a year or so to finish. A bit long. After searching, it seems it's quite common for ddrescue to take a while (people complaining about only getting 800kb to 6mb/s, which I would kill for) but this is ridiculous.
I'm new to ddrescue and hard drive recovery in general. Can anyone give me some advice? Should I just let it go and hopefully it'll get faster. Are there some arguments I can specify to speed it up? Or is there some other software that may do the job?
Any help would be greatly appreciated,
Ignotus
Last edited by ignotus (2013-01-07 18:00:37)
Offline
maybe "testdisk and photorec"
ezik
Offline
Thanks. I'll give those a go.
Offline
Are you sure that the hard disk didn't simply shut down? One of my old disks parked the heads and turned off if i tried to read a certain damaged sector.
'What can be asserted without evidence can also be dismissed without evidence.' - Christopher Hitchens
'There's no such thing as addiction, there's only things that you enjoy doing more than life.' - Doug Stanhope
GitHub Junkyard
Offline
I've been trying to create an image of a friends corrupted hd (the drive it self seems fine but the partition table is pretty messed up) using ddrescue with no options set and it's taking forever.
The drive seems fine? Your output indicates read errors, suggesting the disk is not fine. Check the disk's SMART status, it probably has run into some bad sectors (feel free to post it)..
How are you running ddrescue? Hopefully you've specified a log file. Also try tips found elsewhere, for example -n to skip splitting bad blocks for your initial run.
Offline
I feel really stupid! It turns out the reason it was going so slowly was because the usb cable busted. I had the chance to swap the cables today and that's definitely what it was.
Thanks for all the help
Offline