I've been trying this (converting a disk clone into a image file) using: ddrescue /dev/sdb imagefile logfile2
(where sdb is the original target of a data recovery of failing disk sdc, but I want to continue the recovery into a image file to free up the disk) However, whilst this started off migrating at about 30MB/S average (up tp 60MB/s peak), when I woke up the next morning it had slowed to about 300KB/s, and I'm not sure why. I'd seen it reach 105GB transferred at 30MB/s without any problems before I went to bed and was on target to finish in about 150mins total. Not sure when it hit slow motion, but was only at 220GB by the morning (hours after it should have finished)! I tried restarting the computer in case this sped it back up. It didn't. Neither did going back to the failing disk for a quick test using: ddrescue /dev/sdc imagefile logfile2 All these tests were also running at 300KB/s. Anyone any ideas why this has happened and what I can do to fix it? In case it makes a difference, the image file is on a NTFS drive with plenty of space. It was running fine certainly until at least 105GB. It has now been running for about 40hours to migrate 320GB, and we are still only up to 260GB.. which means another 55hours! Would it be faster on EXT3 drive? (not that I have one, but could try a free up space and create a EXT3 partition). Any thought or ideas welcome. Mike -- View this message in context: http://old.nabble.com/Change-from-Disk-Cloning-to-File-Image-half-way-through--tp30366546p30366667.html Sent from the Gnu - ddrescue mailing list archive at Nabble.com. _______________________________________________ Bug-ddrescue mailing list Bug-ddrescue@gnu.org http://lists.gnu.org/mailman/listinfo/bug-ddrescue
