Checking that the drive is being actually cloned in the middle of the process

[mabuimo]

Hi, I am cloning a WD external USB 3.0 5TB HDD to another identical drive. The process has already taken three days and probably a similar amount is left (process is at 88%, phase 3). I have the following questions:

• How can I be sure that the 88% rescued data has been actually copied to the new HDD?
• Is it safe to stop the process and mount that second target drive to check if the files and folder are showing? Can the process be resumed later without unmounting the target drive?
  Thank you.

[SomeCrazyGuy]

The process is saved to the logfile and can be resumed later. Please do not use github issues for help with cloning, instead use https://www.data-medics.com/forum/ or https://hddoracle.com/ or https://forum.hddguru.com/ or https://www.reddit.com/r/datarecovery/

[mabuimo]

Hi, thanks for the links. I am not sure if I've hit a potential bug. Currently the process shows as "finished" in the GUI, but there is still 12% of data which was "not-tried".

[thesourcerer8]

Please provide screenshots and the logfile.
One theory I have: If there are bad sectors, I think hddsuperclone skips larger areas during the first try to not waste too much time, and on the second/further tries it then digs deeper into those initially skipped areas. I guess that if those areas still behave badly, then it could be that it still skips most of them, which could then result in perhaps 12% of not-tried, since it would take too much time to try them. Perhaps it helps to re-run hddsuperclone with the original logfile, perhaps it then dives even deeper into the not-tried areas?

[mabuimo]

Hi, this is the log file from Wednesday, phase 3
data1.log
I'm afraid I've lost the last (and complete) log file. I will try to re-run hddsuperclone.

[mabuimo]

Hi, I've recovered the final finished log and another intermediate one.
data1_finished.log
data2.log
Please let me know your thoughts. Is this a bug? I assumed that in the divide and scrapping phases, all areas would be tried. Thank you.

[SomeCrazyGuy]

there appear to be many large skips but no bad sectors, assuming this is a drive with the WD slow response bug, try resetting the log in the tools menu (this will not clear any successfully read blocks) to clear all saved skip data and non-tried information. make sure you are using the options to handle the slow response drives and try starting again (it will only try to clone the untried blocks)