This automated behavior can be very bad in cases which is needed to have more precise control over clone process (such as the clone direction), when handling scratched disks, per example. In such cases, it's quite important to keep the heads away from scratched areas to prevent permanent damages.
Just setting the copy direction does not prevent the heads from eventually reaching the scratched area. You also need to limit the rescue domain as explained above.
The possibility of controling pass direction can helps to avoid some problems and prevent ddrescue to go over an unwanted area for twice (when it turns from forwards to backwards, per example), and other stuff. Even setting domain size, DDrescue automatically alternates its direction, which can be a bad ideia in some cases. This is based on my data recovery routines with Data Extractor (from PC-3k) and some older DDrescue versions.
Is there a way to force Ddrescue to run in only one especific direction (at least in --no-retry mode)? Per example, "ddrescue --forward --force /dev/sda /dev/sdb" to run only in forward direction.
Currently not, but it can be added if needed.
Listen, as a data recovery professional, I just want to help improve this tool which I really appreciate. The possibility of controlled clone can avoid some damages and makes DDrescue even more useful for professional (data recovery and forensics) routines.
Please, think about it. Thank you. William. _______________________________________________ Bug-ddrescue mailing list [email protected] https://lists.gnu.org/mailman/listinfo/bug-ddrescue
