[Bug-ddrescue] ddrescue relaunch and reading non-damaged part first

[Matthieu Kretzschmar]

Hello,

I have dropped my macbook (apple laptop) and my 80Gb SATA hard drive  
(with all my research data) does not mount anymore. It is now  
connected though firewire to another computer and I am running  
ddrescue on it. Actually, because I have done things a little bit too  
fast, I am running ddrescue on the primary partition.

ddrescue -v /dev/disk1s2 /home/new.dmg rescue.log

it is running now since 2 days. It has first stopped for some time  
(about one hour) at the very beginning and then read very fast 19 Gb  
(in 2 hours?), but it is now stopped (I mean very slow) since about  
36 hours. As an example, it has read about only 24Mb during the last  
whole night.

I am considering to stop it (btw how do I do that ? control+C ?), and  
relaunch it in a way that it first reads the non-damaged part. This  
way, I hope to know how much is damaged and to have an estimation of  
the needed time to rescue the maximum of my data. Here I am asking  
for help:

- How do I stop it ?

- Which options should I use in order that it restarts at the right  
place (or the existence of the log file is enough?) ?

- Which options should I use in order that it first reads all what  
can be read ?

Many thanks for that program and for help,

Matthieu