I know I've read something about this on this forum but I can't find the topic - sorry for the dupe!
I'm imaging an old 4gig disk using FTK Imager through a Tableau IDE bridge via USB 2 connection. Target drive is a 200gig external also on USB. FTK Imager reports a throughput of only 0.008 mb/s and a whopping 180 hours to image the drive.
The suspect drive sounds like an F16 taking off and is obviously on it's last legs…
Is the problem my configuration or the suspect drive?
The drive is probably full of errors and that's causing the issues. Having it chugging away so long wont help. I typically revert to DOS acquisistions on drives like that and usually have much better results.
That's what I suspected. I'll try another tool. Thanks!
Try ddrescue under Linux
I use dd religiously. Using a blocksize of 4k, I can image a 164GB drive in under two hours.
A
I use dd religiously. Using a blocksize of 4k, I can image a 164GB drive in under two hours.
A
Can you do it that fast when the drive is full of bad clusters, 8 years of dust, dirt and hair accumulation and has crotchety heads? 8)
Last week i imaged an old 8.4 gig harddrive using ddrescue. Alltough it contains quite a lot bad sectors, it took me just under an hour to image it.
I don't have FTK or EnCase handy to try to see the difference in imaging time between these products, but it would be nice to know if there is a real difference between these products, regarding imaging disks with bad sectors.
Does anybody have some information on this?