Operation Failed error Source: MountVolume:7763
Open source disk encryption with strong security for the Paranoid
Brought to you by:
idrassi
Menu
▾
▴
Hi,
Its with most of these issues - hopping theres a fix rather than my data is lost.
Had a 2nd hdd installed, encrypted it (VC1.19). Passed the tests, ran the process, said was a success, gave the messages to use Auto mount to mount it.
On restart, windows sees it (doesnt recognise the file system, asks to format, no no no)
Try to mount, get the error:
Operation failed due to one or more of the following:
-Incorrect Password
-Incorrect Volume PIM number
-Incorrect PRF (hash)
-Not a valid volume.
Source:MountVolume:7763
Tried lots of options, no joy.
Took out the drive and put into an external caddy to try to mount it and save laptop restarts, get the same error.
VC sees it :
Select Device
Harddisk 1: 1.8TB
\Device\Harddisk 1\Partition1 128MB
\Device\Harddisk 1\Partition2 G: 1.8TB
Can you clarify your account of the initial encryption, please? The drive you encrypted apparently contained partitions; theoretically, Veracrypt will not let you encrypt a non-system drive with partitions, only the individual partitions. Did you encrypt each partition separately?
Last edit: Adrian Kentleton 2017-06-08
Errr is the answer.....
I only ran the process once, to encrypt that "full drive" (not a partition on it or create a partition on it) and followed the instructions to do it with keeping the data that was on it.
I think it was the G partition, as that was showing as the G drive in Windows before it started.
VC seemed comfortable to allow it, all seemed normal.
So full encryption of G, keeping all the data.
(I dont recall choosing the bigger partition, so I don't think it was ever listed as an option)
I'm cloning the drive in question right now, when it's done, I'll remount it internally and try to duplicate the encryption steps again to be able to be more specific to help with what steps were originaly followed, in case whats written here has not been of value. (sorry!)
Thank you for helping.
It looks as though your starting point was a drive which had only one 'real' partition on it, 128 MB smaller than the drive capacity, and you encrypted that - which, as you say, VeraCrypt would be OK with. (The other 128MB 'partition' is probably just unallocated space.)
One issue you have, is that you haven't freed up the initial Windows allocated drive letter G:. That's why you get the offer to format the partition, and it also means it is unavailable to Veracrypt to use as a mount point drive letter. (I should say, I don't think it will solve your main problem, but it's always a good idea to eliminate other obvious issues, just in case.)
Use Windows Disk Management to view the partition structure on the drive, and remove G: from the now-unavailable-to-Windows-directly encrypted partiton. Best way to launch WDM is via the Run box, type
diskmgmt.msc, and click 'Enter'. Right click on your encrypted partition (which will be shown as 'RAW'), left click 'Change Drive Letter and Paths...', left click 'Remove'.Last edit: Adrian Kentleton 2017-06-09
When I plugged the external caddy in with the (3.5") cloned drive, I was able to unassign the letter as you said.
didnt make any difference to the dectryption error.
I put the original drive pack in the laptop, wasn't recognised at all.
Not G, not in disk manager, not in the bios.
Was just invisible.
Checked all the connections, no change.
Plugged it into the caddy, it's seen as a healthy Raw primary partition.
Only 1 partition too, not 2 like before.
It wasn't showing as a G like before.
But, If I select it as a file for VC decryption, VC shows it as the 2 partions like before.
None of the options though change the decryption error.
So, I assigned it a letter to try to retrace the earlier original steps.
Encrypt a non system partition/drive
Standard VC
volume location
Selecting Harddisk 1 brings up the error you posted, it wont allow it.
Selecting Partition 2 (the 1.8Tb partition) is accepted.
Encrypt partition in place
(I now get its not a valid NTFS system, as it isnt, but it was before, so followed all teh steps after that)
I'd need to format it to make ntfs, but then I know the data is gone.
But I'm now pretty sure I did just the 1.8 Tb partion before as an in place encryption, with selcting keeping the data and no wiping.
With the back up, I can play with the original hdd, if there is anything that may help.
What are your thoughts please?
I'm getting the feeling it may be game over?
Thank you
Don't assume it's game over! There's two possibilities: a. where the password is stored on the volume is corrupted , or b. you are entering the wrong password (or PIM, or hash).
I'm not knowledgeable enough to help you with a. Anything I could say would only be secondhand knowledge, gleaned from advice given by more expert folk trying resolve similar issues in other threads on the forum; try searching for such.
But b.? I sometimes repeatedly get the 7763 error, eventually, my password is accepted. It's worth thinking hard about why this might happen.
Did you use a password or passphrase? How did you enter the original password (on volume creation)? Copy and paste it in from a .txt file, or type it in manually twice, blind? It's very easy to typo twice. Try typing your password as a line in a blank .txt file, and copy/paste it into the password box. Do the passwords you use normally follow a certain style/pattern? Does the password you've just typed into the text file look right? Is it possible there's a character you'd normally use upper- or lower-case, used the other way round?
Did the password you used contain characters you don't normally use? In my experience (partly because I use to live in a house with high humidity) little used keys often 'mis-fire' (fail to register), presumably because the switches were minutely corroded (oxidised); the solution was to repeatedly use them, typing the character into a .txt file, until they started working properly again.
You say you have been having this trouble on a laptop, so different keyboards (or keyboard layouts) can't be an issue. But I typo far more on a laptop keyboard than on my desktop one.
Above advice may be redundant; you've probably repeatedly tried all the above. However, I still think it's worth a very deliberate re-look at what you think your password is, and ask yourself how you might have entered something (slightly) different at volume creation stage. I say deliberately, because it's very easy to panic when you get a 'wrong password' message, and keep on repeating the same error.
Hopefiully someone else may come to your assistance if you are utterly sure you are using the right password. Don't be afraid to 'bump' the issue if necessary. Other folk may have hung back from offering help since I had got involved, but may come forward now I have said I can't help further.
Good luck.
Hi Adrian,
Things seem quiet on a) the technical side, but yes, b) - the password - it's worth trying your advice.
I entered it twice, blind thinking "well, XYZ-1 is my main drive password, so shouldn't use the same password for the second drive, so lets use XYZ-2"....
As you say, I lose nothing by taking an hour to very methodically run through a written down list of options and close to that options.
As much as it's a I thought 20 character long password, it only contains 8 or 9 different characters, which could, without out running the numbers to see how practical/timely it would actually be, mean if one could brute force it, just with those, it may be possible to solve.
I did see in here some brute force code, but I couldn't understand how to apply it to make some kind of automated process.
That it seems to take 5-10 seconds to process from password entry to Denied/accepted, I cant see an automated system ploughing through thousands of permutations a second.
I'll try your approach.
Thank you for taking the time to help.