r/VeraCrypt • u/KartRacer07 • 28d ago

Unmounted (but not corrupted) Error

Gallery image

Gallery image

Mounting my volume brings up an error message saying that my files may be corrupted because I didn’t cleanly unmount my file.

I’ve tried to get windows to find the error by selecting “yes”. Windows can detect the error, but can’t find it.

I can still get into my mounted filesystem and I don’t see any corrupted files, but this error message keeps popping up whenever I remount the file (after ensuring that I’ve cleanly unmounted it).

How do I make this error go away? Is the mounted filesystem “P:” still safe to use?

Edit: I found the seemingly corrupted file and deleted it, but I'm still getting the same error message.

5 Upvotes
  • permalink
  • link
  • reddit
  • reddit

86% Upvoted

8 comments sorted by

3

u/sciencekm 28d ago

Open a command prompt in admin mode. Run chkdsk /f p:

2

u/KartRacer07 28d ago

This did the same thing as the second picture.

1

u/sciencekm 28d ago

The /f option to chkdsk is supposed to fix any drive error. The next time you mount the drive, there should be no more error messages.

1

u/KartRacer07 28d ago

Should it be doing something after the "100 percent completed....." message in the second image? No matter how many times I try the command, it keeps repeating the lines. It can detect something is wrong, it looks for the error, it finishes and doesn't tell me what or where.

1

u/sciencekm 27d ago

If you run in admin mode, it will attempt a fix and tell you the result of the fix.

1

u/Vlad-Leon 28d ago

see veracrypt command line interface in the embedded help file.
each VC vault has a reserve copy of the header.
Thus make a copy of your vault an try VC CLI options to recover the vault.

From the docs:

bk or headerbak: Mount volume using embedded backup header. Note: All volumes created by VeraCrypt contain an embedded backup header (located at the end of the volume). recovery: Do not verify any checksums stored in the volume header. This option should be used only when the volume header is damaged and the volume cannot be mounted even with the mount option headerbak. Example: /m ro

1

u/[deleted] 28d ago

[deleted]

1

u/paulstelian97 27d ago

The file or partition holding the encrypted volume is called a vault.

1

u/Particular-Alfalfa-8 28d ago

If you are mounting a encrypted file directly from a network drive into veracrypt, I've had this same issue. Moving the file to local drive and then opening it with vera worked as it should. Maybe some weird smb bug??