Package: gddrescue Version: 1.21-1 Severity: important File: /usr/bin/ddrescue
Dear Maintainer, This is important. My disk had crashed and about 132KB of sectors were damaged: http://pix.toile-libre.org/upload/original/1513821694.png I decided to recover my data, partition by partition sdc4, sdc3, sdc2, etc I passed the ddrescue_log file as an option, every time I ran the command. Then I decided to RMA the disk and ran this command ddrescue --fill-mode=+ --force /dev/zero /dev/sdc ddrescue_GNU.log It finished almost immediately - it did not register in my head at that moment, that the disk was substantially NOT ERASED. If you look at the log file IMAGE you see why. While recovering my data - at some point, probably for sdc1, I must have interrupter the program. Then when I tried to zero the entire disk it just used the 'faulty' log and blanked out a portion assuming that's what I wanted. The log appears to be not cummulative across runs - ddrescue needs some mechanism for either informing the user when it fails to blank the entire disk. -- System Information: Debian Release: 9.3 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8), LANGUAGE=en_IN:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gddrescue depends on: ii libc6 2.24-11+deb9u1 ii libgcc1 1:6.3.0-18 ii libstdc++6 6.3.0-18 gddrescue recommends no packages. gddrescue suggests no packages. -- no debconf information
