Corrupted VeraCrypt container?

[Fred]

Hello, everyone.

My situation is like this:
Last year, I created a bunch of VeraCrypt containers.
They have been stored on an external hard drive that hasn't been used very much since then (but may have been short on empty disk space for a while).
Yesterday, I could decrypt and open all but one of my containers. (The error message I get is the same as when I enter an incorrect password for a functional container.)

What is your guess. Has the container been corrupted, or have I simply forgotten my password? Could anything be done in the corruption case?

Thanks in advance.

[RealTehreal]

Hey there. You could try to mount the volume using the backup header (it's a mount option). If that won't help, the volume is either utterly damaged (both main and backup header damaged) or you simply forgot the credentials.

In case of damaged headers, the only way to still get access to the volume would be using a header backup. But you would have had created it before the headers got corrupted.

Greets

[Fred]

Thank you for your quick reply.
I did make a few attempts restoring the embedded backup header, to no avail. But just to be clear, such a header would have been automatically created along with the container, right?

[RealTehreal]

Yes, the backup header is automatically created within the volume.

Greets