January 23rd, 2021, 3:47
I imagine using the virtual driver could assist greatly retrying the recovery of missing sectors using DMDE or rstudio set against the clone and drive, little point in thrashing about with empty sectors.maximus wrote:I am not sure if the OP would benefit much from the pro version, without any experience.
January 23rd, 2021, 10:13
Agree, the OP did say somewhere in this thread they wanted to learn. Right now I think they may learn the hard way that it is important to target needed data during cloning because the drive will only get worse and possibly die.I imagine using the virtual driver could assist greatly retrying the recovery of missing sectors using DMDE or rstudio set against the clone and drive, little point in thrashing about with empty sectors.
Yes, that is very interesting.Speaking of which, slightly OT but have you seen Sin's thread in R&D on reading .map files from DE and parsing into DDI ?
January 23rd, 2021, 10:56
maximus wrote:Agree, the OP did say somewhere in this thread they wanted to learn. Right now I think they may learn the hard way that it is important to target needed data during cloning because the drive will only get worse and possibly die.I imagine using the virtual driver could assist greatly retrying the recovery of missing sectors using DMDE or rstudio set against the clone and drive, little point in thrashing about with empty sectors.Yes, that is very interesting.Speaking of which, slightly OT but have you seen Sin's thread in R&D on reading .map files from DE and parsing into DDI ?
Lardman wrote:I'm curious too as to how it will turn out - last time I looked in the drive wasn't being recognised in the bios.
I imagine using the virtual driver could assist greatly retrying the recovery of missing sectors using DMDE or rstudio set against the clone and drive, little point in thrashing about with empty sectors.maximus wrote:I am not sure if the OP would benefit much from the pro version, without any experience.
Speaking of which, slightly OT but have you seen Sin's thread in R&D on reading .map files from DE and parsing into DDI ?
January 23rd, 2021, 11:27
January 23rd, 2021, 11:38
maximus wrote:I see that it shows as a 100% recovery, which I did not expect. Also, since you say there are damaged files, obviously it is not 100%. Were you using a USB adapter to clone the drive? If so, I think that it did not properly identify the errors. I suspect this because the log showed it was in SCSI passthrough mode, and I don't see the model and serial number in any screenshot. You may have got a false recovery if you did not have the drive directly connected to the computer. THAT would be learning the hard way.
January 23rd, 2021, 13:28
January 23rd, 2021, 15:18
January 23rd, 2021, 17:47
January 27th, 2021, 18:07
maximus wrote:Yes, another option is to start over with a new progress log file, and the source directly connected to the computer (but keep using the same destination), and target the second partition with the input offset and size. Actually since it is the last partition, only the input offset should need to be changed, the size will adjust to the end of the drive.
I was only trying to minimize read attempts of already read data with my suggestion, since we don't know how long the drive will last, or how much data is melting off the surface with every pass. This whole recovery attempt has been kind of a mess from the start. And I was assuming it was directly connected from previous posts about getting it to show up in the bios, so I missed noticing it was probably connected via USB, which really messed things up, and also messed up my assessment of the condition.
January 27th, 2021, 19:09
Watch the video farther, it shows how to hide the drive using the live CD.
January 27th, 2021, 20:17
Powered by phpBB © phpBB Group.