Menu

Is this VeraCrypt or Is this Hard Drive Failure?

WRVC2016
2022-12-29
2022-12-29
  • WRVC2016

    WRVC2016 - 2022-12-29

    I am able to mount the drive (with password, keyfiles, PIM, etc...). Once mounted and clicking on the mounted drive letter, I hear the hard drive clicking. The clicking only happens when I am trying to get to the mount letter.

    After a two minutes wait, I get a message of: The volume does not contain a recognized file system. Please make sure that all required file system drivers are loaded and that the volume is not corrupted.

    I am able to restore the backup header but still same issue.

    Have been using VeraCrypt and TrueCrypt from the inception and this is the first time I have seen this.

    When I run this: chkdsk w: /x /r

    It does say that the: The type of the file system is NTFS.

     

    Last edit: WRVC2016 2022-12-29
  • WRVC2016

    WRVC2016 - 2022-12-29

    I was able to get to the file structure using Recuva after 3 hours of scanning. Still clicking and not able to recover the files yet, except for one file (jpg).

     
  • WRVC2016

    WRVC2016 - 2022-12-29

    So here is an update in case someone else runs into this situation. Luckily, I do have a backup of this drive but there is 10% of it that has not been backed up. Good practice for me is that I always do a comparison and take a screen print of the differences that are not backed up between the two drives. In this case, I knew exactly what I needed to recover.

    Fortunately, Recuva has been able to recovered 85% of the 10% (not backed up) which is about 200 GB. Mostly are old games. During those files that are recoverable, there are no clicking sounds, only the ones that cannot be recovered is when I hear the clicking.

    Anyway, I think this maybe a corrupted VeraCrypt Volume or system table thing. Although it is clicking, I don't think it is a hardware issue.

    After I recover most of my files from that 10%, I do plan to redo this VeraCrypt drive and see if this has been a hardware issue or a VeraCrypt Volume corruption issue. This drive was encrypted about 7 years ago.

     

Log in to post a comment.