by rolin » Mon Oct 21, 2019 2:53 pm
You didn't answer my question...
I've used several data recovery tools/software in the past, and RSudio is good at getting data from drives that have corrupted partitions, some damaged sectors, reformatting, etc. But this is the first time I've tried to use RStudio to recover a drive that loses ready often with several large damaged areas - and making an image of this drive before recovery is important to not damage the drive further. I can't restart at the point the drive locked up - always starts at the beginning with the log file or not! It appears the log file only helps to not rescan damaged and marked areas on the drive (from the log file), but it doesn't help from starting at the beginning of the entire drive again. Unless I'm missing something (which is why I posted my question), this is a major oversight on this program.
I waited 2 days after I posted this question and finally decided to use DDRescue instead - a program I've used often in the past and I can restart at the point I left off after the drive locks up. That way I don't have to start over and lose several days of work each time it locks up!
Again, if I'm missing something please let me know. Otherwise I can't use this program to image failing hard drives - it's just not practical.
You didn't answer my question...
I've used several data recovery tools/software in the past, and RSudio is good at getting data from drives that have corrupted partitions, some damaged sectors, reformatting, etc. But this is the first time I've tried to use RStudio to recover a drive that loses ready often with several large damaged areas - and making an image of this drive before recovery is important to not damage the drive further. I can't restart at the point the drive locked up - always starts at the beginning with the log file or not! It appears the log file only helps to not rescan damaged and marked areas on the drive (from the log file), but it doesn't help from starting at the beginning of the entire drive again. Unless I'm missing something (which is why I posted my question), this is a major oversight on this program.
I waited 2 days after I posted this question and finally decided to use DDRescue instead - a program I've used often in the past and I can restart at the point I left off after the drive locks up. That way I don't have to start over and lose several days of work each time it locks up!
Again, if I'm missing something please let me know. Otherwise I can't use this program to image failing hard drives - it's just not practical.