Hello! Thanks for your program! I am still using it to recover data from very slow hitachi 1 terabyte hdd. 213 Gb rescued. I have detected a bug. When using start or end positions that are not rounded to hardbs (512 bytes) - I always receive an error of "bad sector" with sizes varying from 0 to 512 bytes. For example, try ddrescue /dev/sda -i100 -s1s ~/tryoutfile.img ~/logforbugs.log or ddrescue /dev/sda -i100 -s800 ~/tryoutfile.img ~/logforbugs.log Of course, I am not using such stupid values, but something like -i371G -s49k may result in 2 bads for the logfile. Sorry for my English - I am from Russia. Also, my HDD being rescued contains areas with good read rate (about 4Mb/s) sized about 600M, and between them - areas of slow readable sectors (about 4 seconds per sector). I need some options to immediately skip such slow areas to recover as much as possible with minimal time spent. For example, such strategy as to read forwards until slowing to min_read_rate or detecting an error, then read backwards, until slowing or bad, too. Then divide the maximum sized untried block by half and repeat.
Oh! My HDD is such a slow one and contains many actual bads that I use only -d -c1 -n -N. Maybe, I am ignoring trim! Will reread the manual and try options with trimming. _______________________________________________ Bug-ddrescue mailing list Bug-ddrescue@gnu.org https://lists.gnu.org/mailman/listinfo/bug-ddrescue
