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

Đang mở
  • Có gì không ổn?
#1,897 1 bình luận 0 reaction 0 người được giao Xem trên GitHub

Maintainer thường phản hồi trong vòng 1 ngày

Chưa có ai nhận issue này.

Đánh giá

Độ khó
4/5
Thời gian dự kiến
3-5 ngày
Mức phù hợp với người mới
20/100
Loại issue
Lỗi
Độ rõ ràng
Cần làm rõ
Mức độ hoạt động
Sôi nổi
Công nghệ
c
Lĩnh vực
cryptography, security

Hướng nghiên cứu

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.

Do mô hình lập chỉ mục viết ra từ nội dung của issue.

Mô tả

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.

Ngôn ngữ chính
C
Star
11.7k
Fork
1.4k
Merge trung bình
1 ngày 1 giờ
Pull request đã merge (30 ngày)
28

Chuẩn bị môi trường

Dự án này không cung cấp dev container, Dockerfile hay hướng dẫn đóng góp, nên bạn cần tự thiết lập môi trường: hãy bắt đầu từ README và xem hướng dẫn đóng góp lần đầu của chúng tôi để biết các bước chung.

Bắt đầu từ đâu

  1. Đọc hết issue, rồi đọc hướng dẫn đóng góp của dự án.
  2. Bình luận trên issue rằng bạn sẽ nhận — tránh hai người làm cùng một việc.
  3. Fork repository và làm thay đổi trên một nhánh.
  4. Mở pull request có tham chiếu số hiệu của issue.

Issue khác của veracrypt/VeraCrypt

Tất cả issue của veracrypt/VeraCrypt

Issue tương tự

Thêm issue về C

Nhận issue mới trong hộp thư của bạn

Bản tóm tắt ngắn những issue GitHub phù hợp với người mới.