I kicked off a BitLocker encryption process on one of my organizations new production servers's drives ("D:") yesterday evening at 7:00PM and left for the day. For reasons known only to God, my partner hard-killed that server at 10:00PM.
When I arrived at the office this morning I saw the machine was off, powered it up and gave it a once-over...and saw that it's "D:" drive showed as BitLocker "Locked". I right-clicked, selected "Unlock" and was prompted for the key, which I provided. It rejected the key as not being the correct key for that drive. I double checked the key's GUID, and tried again, and it failed with the same error message. I rebooted and repeated the procedure twice more and got the same result the first time, but the second returned an error code of 0X8007007a.
Accepting that the volume was likely corrupt, I attempted to run repair-bde, and while it accepted the key and evaluated the volume's metadata, it returned the message below:
C:\Windows\system32>repair-bde D: Z: -rp 000000-000000-000000-000000-000000-000000-000000-000000 -F
BitLocker Drive Encryption: Repair Tool version 6.3.9600
Copyright (C) 2013 Microsoft Corporation. All rights reserved.
Beginning scan for BitLocker metadata.
Scanning boot sectors for pointer to metadata: 100%
Finished scanning for BitLocker metadata.
LOG INFO: 0x0000002a
Valid metadata at offset 39647494144 found at scan level 1.
LOG INFO: 0x0000002b
Successfully created repair context.
ACTION REQUIRED: Run 'chkdsk Z: /f' before viewing decrypted data.
The parameter is incorrect.
My questions are these:
1. Which parameter is the utility reporting incorrect? Assuming the key....is this correct?
2. Given that the volume had only been partially encrypted, is there any hope that there might be clean files on that volume that a recovery utility might be able to save?
3. What other options might you know of, if any, aside from nuking and paving that drive?
Thanks for the assist in advance!