[Bug-ddrescue] fill-mode vs luks encryption

[Atom Smasher]

i've been using ddrescue for a while, usually with great success. thanks!

right now i've got a 1.5TB WD drive (1.4TB, actually) with a luks 
(encrypted) partition.

 * Raw_Read_Error_Rate - FAILING_NOW - 66055
 * Current_Pending_Sector - 1450

the drive is screwed. i got most of the data (>99%) recovered from the 
drive on the first pass, and over the last month i've been picking tiny 
bits and pieces off the drive. currently it's at:
        percent recovered = 99.95278650616919872200
        percent missing = .04721349383080127700

the data on it is nothing critical, but i'd like to recover it... if 
nothing else, as an exercise in data recovery from a failing drive.

so far, so good. here's the tricky part...

on other failing drives i've used the "fill mode" to identify files that 
haven't been completely recovered, but this disk is encrypted (with luks). 
because the drive is encrypted, filling the un-recovered parts of the 
image with a string will NOT put that string in the files, after the image 
is decrypted.

before i spend too much time on it, does anyone have any tips or ideas for 
identifying which files are missing some of their bits?

thanks...


--
        ...atom

 ________________________
 http://atom.smasher.org/
 762A 3B98 A3C3 96C9 C6B7 582A B88D 52E4 D9F5 7808
 -------------------------------------------------

        "The only defense against evil, violent people
         is good people who are more skilled at violence."
             -- Rory Miller's Hard Truth #1