The following recovery is being (has been) performed on an external enclosure running JBOD. I recently "recovered" a bitlocker drive using the following command in cmd prompt on windows 7:
repair-bde C: Z: -rp 062612-026103-175593-225830-027357-086526-362263-513414
Once the recovery process reached 50% cmd prompt gave me the following error (see attached screenshot). During this screenshot, Cmd prompt did not stop outputting out log errors, but error code was ALWAYS "log error 0xc0000035" and was continuously being output for different offset points.
I was able to restore the content, however, I do have an issues reading the files. 95% of the files (except for the most recently written data), have a read error. The file sizes seem to be fine, but the data is unreadable. I am wondering if you have any suggestions beyond running chk disk?
Please let me know if you have any advice as to where i might turn next folks. This recovery effort has been an ongoing project since 2012. Thanks in advance for your time, and support.
Regards
Don't know if it will work with Bitlocker but when I have problem HDDs to deal with I will boot to a Linux LiveDVD such as Linux Mint to check the contents of a drive. Linux supports NTFS and other drive formats. The main thing is that encryption keys may be stored in Windows and booting to Linux bypasses that, sometimes accessing files works. Just an idea.This recovery effort has been an ongoing project since 2012.
have you ever tried to unlock a bitlocker drive encrypted in windows from Linux LiveDVD? I have a suspicion this would work. perhaps i am not understanding? Thanks for the reply
