External HDD Won't Mount Despite Correct Password – Possible Interrupted Finalization (MountVolume:9553)

未关闭
  • 哪里不对？
#1,897 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
20/100
Issue 类型
缺陷
描述清晰度
需要澄清
活跃度
活跃
技术栈
c
领域
cryptography, security

调研方向

The issue provides no source files, tests, or code entry points to investigate. First establish whether this is a reproducible VeraCrypt defect or a user-support question; the report asks for diagnostic guidance and does not identify a code change or a testable expected result.

由索引模型根据 Issue 内容生成。

描述

External HDD – Correct password but volume won't mount (MountVolume:9553 / 4549)

Hello,

I need some help recovering access to a VeraCrypt-encrypted external HDD.

The HDD was encrypted with VeraCrypt on another Windows computer some time ago. I am now connecting the same physical HDD to a different Windows PC using a USB HDD enclosure.

VeraCrypt detects the disk/partition normally, but I cannot mount the volume.

I am confident that I know the correct password and, as far as I remember, the password has never been changed.

When I try to mount the volume, VeraCrypt reports:

Operation failed due to one or more of the following:

Incorrect password

Incorrect Volume PIM

Incorrect PRF (hash)

Not a valid volume

Source: MountVolume:9553

On another attempt, I also received:

Source: MountVolume:4549

There is one detail from the original encryption process that may be important.

As far as we remember, the actual encryption process reached the end. However, VeraCrypt was performing some kind of finalization/closing operation at the very end of the process, and it is possible that the program or computer was closed during that final stage.

I am not saying that encryption was interrupted halfway through while the disk was still being encrypted. My concern is specifically that the encryption itself may have completed, but the finalization/closing stage immediately afterward may have been interrupted.

Unfortunately, I cannot remember exactly what VeraCrypt was doing at that final point.

Could interruption at this stage cause the volume header or other VeraCrypt metadata to remain in an incomplete/inconsistent state and later result in the password/PIM/PRF/not-valid-volume error?

I would also like to rule out other possibilities, such as:

Volume header corruption

Different PIM or PRF/hash settings

Selecting the partition vs. the entire physical device incorrectly

VeraCrypt version compatibility

An older VeraCrypt/TrueCrypt format or algorithm

The USB HDD enclosure presenting the drive differently from the original SATA connection

Another mount option that may have been used when the volume was created

The data on this HDD is important, so I do not want to perform any operation that writes to or modifies the encrypted disk until I understand the problem.

What would be the safest diagnostic procedure in this situation?

In particular, is there a safe way to determine whether the primary/backup volume headers are valid, or whether the finalization stage of the original encryption was not completed, without modifying the disk?

If necessary, I can provide the VeraCrypt version I am currently using, Windows version, HDD/partition layout, and any other technical information needed.

Thank you for your help.

主要语言
C
星标
11.7k
派生
1.4k
平均合并
1 天 1 小时
30 天内合并 PR
28

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

veracrypt/VeraCrypt 的其他 Issue

查看 veracrypt/VeraCrypt 的全部 Issue

相似的 Issue

更多 C Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。