I looked at those log files with a text editor, and can definitely see an issue.nissimezra":6stm6igs said:I uploaded 2 files with error. You can try it in your tool. I have more if you want
http://www.filedropper.com/maxtor
https://ufile.io/fvkw8
All of the log files show zero run time and zero progress, indicating that they are new progress files that have not had any recovery ran with them yet. They also don’t have a progress status line written to them yet, which is causing the error. They have a total LBA, but the source and destination are both blank (null). I don’t even know what conditions could produce logs like that. I can’t reproduce that in any way. It does not make sense.
Now for some other things that don’t make sense to me on how they came to be.
The “maxtor" and “maxtor.bak” files are from different runs that are a few weeks apart. The total LBA is also different between them, so it wasn’t even the same disk.
The “taher” and “taher.bak” are almost 2 minutes apart, but the total LBA is different between the two. That would also indicate two separate attempts with two different drives. But the LBA to read is the same, which leads to even more confusion.
I don’t know what you are doing, but it is very confusing.