maximus wrote:nissimezra wrote:@maximus, This seems to work like charm for wd that one of the head isn't reading.
I have a drive that if it connected to windows it mount and disconnect repeatedly.
I cloned the drive, 75% went smooth but 25% aint moving. Now it's scrapping. still only 75%.
This seems to get job like head mapping.
The smooth part would be the head skipping algorithm doing its job in phases 1 and 2. So in this case of a dead head, you basically already had the best recovery at the end of phase 2. The trick is to be able to understand the results. Someone that is technical could use hddscviewer to get a better idea of what the recovery looks like, and even tell if there seems to be any data readable in the bad head. It also helps to be able to understand the log file (by reading the manual), as analyzing it can also give an indication if any data is being read from a bad/weak head. Learn how to understand the results and you could tell at the end of phase 2 what the condition of the drive is.
And you are using the free version. Imagine using the pro version and properly implementing the timeouts for directly connected SATA drives, and making the whole process faster.
maximus wrote:Don't worry too much about the errors you see in the console when starting hddsuperclone. Some of that is from having to run it as root (sudo). You would be surprised how many console errors there can be when starting a program from the terminal in Linux. I have seen many errors from the likes of Firefox and R-Studio, but they work fine. The average user would never see that because they started it from an application shortcut that does not open a terminal.
Users browsing this forum: No registered users and 0 guests