I’ve been using VeraCrypt to encrypt a 16Gb USB drive, and the last time I decrypted the drive I got a message saying that the volume header was corrupt, and needed to be restored. The drive seemed to decrypt, but Windows 7 did not recognize it as NTFS or assign a drive letter, so I did a Restore volume header from the backup embedded in the volume. It still did not recognize the filesystem, so I haven’t been able to recover any data from the drive. I’ve tried several undelete/recovery tools, most of which report the correct drive size but cannot recover the partition, so I assume that there are some bad sectors in the filesystem header area. I also was not diligent recently about defragging the data, so that could be an issue.
Restoring the volume header was the only write operation on the drive since the failure; is it possible to try repairing the filesystem headers? Or a better way to attempt to recover the data, since my last backup is fairly old?
Thanks,
K Walker
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Unfortunately, no. Thanks for the pointer to the update though. The behaviour is the same, and I don't think VeraCrypt recognizes the same partition that it used to. It seems to decrypt the device, but it doesn't display the partition on the device that it used to.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I’ve been using VeraCrypt to encrypt a 16Gb USB drive, and the last time I decrypted the drive I got a message saying that the volume header was corrupt, and needed to be restored. The drive seemed to decrypt, but Windows 7 did not recognize it as NTFS or assign a drive letter, so I did a Restore volume header from the backup embedded in the volume. It still did not recognize the filesystem, so I haven’t been able to recover any data from the drive. I’ve tried several undelete/recovery tools, most of which report the correct drive size but cannot recover the partition, so I assume that there are some bad sectors in the filesystem header area. I also was not diligent recently about defragging the data, so that could be an issue.
Restoring the volume header was the only write operation on the drive since the failure; is it possible to try repairing the filesystem headers? Or a better way to attempt to recover the data, since my last backup is fairly old?
Thanks,
K Walker
does using 1.24-update4 fix the problem?
Unfortunately, no. Thanks for the pointer to the update though. The behaviour is the same, and I don't think VeraCrypt recognizes the same partition that it used to. It seems to decrypt the device, but it doesn't display the partition on the device that it used to.