Hello! I've been using Veracrypt since it was first released, and Truecrypt for ages before that. Maybe 20 years all together? And for the first time I've found myself with a problem I'm not sure how to fix, I hope someone has some advice.
What happened is I was getting ready to backup my VC disk, and needed to set up some partitions on the new backup drive. Instead of using the windows disk management like I normally would, I tried the EaseUs disk management software, and that's where I think the trouble started.
I am 100% sure I didn't do anything that should have affected the source drive, I was only working on the new disk I wanted to backup to. But it looks like Easeus decided to initialize my Veracrypt drive for me anyway, without being told to. I'm sure this is ultimately my own fault because I went against recommendations and did not have any partitions on the disk, I encrypted the entire drive. I do this so it doesn't show up in windows with a drive letter, it makes the whole thing totally invisible unless you are using something like a disk manager, or the VC drive selection. I've never had a problem with it before, when something asks me to initialize it I just say no. But this program seems to have gone ahead and done it without asking. Originally it was a basic GPT drive, now it is being seen as a dynamic MBR.
Naturally the first thing I did was try to restore the embedded header info, on the few occasions when I've had an issue in the past that has worked perfectly. But this time I got an error message. It is possible I might have an external backup of it somewhere and I'm sure that would make this easier, but so far I haven't been able to find it.
Right now I am in the process of cloning the drive to try some recovery options on the copy, is there a chance that all I need to do is convert it back to a basic GPT drive to be able to access the embedded header info? It would be nice if it was that simple. But if not, what would be the best thing to try?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello! I've been using Veracrypt since it was first released, and Truecrypt for ages before that. Maybe 20 years all together? And for the first time I've found myself with a problem I'm not sure how to fix, I hope someone has some advice.
What happened is I was getting ready to backup my VC disk, and needed to set up some partitions on the new backup drive. Instead of using the windows disk management like I normally would, I tried the EaseUs disk management software, and that's where I think the trouble started.
I am 100% sure I didn't do anything that should have affected the source drive, I was only working on the new disk I wanted to backup to. But it looks like Easeus decided to initialize my Veracrypt drive for me anyway, without being told to. I'm sure this is ultimately my own fault because I went against recommendations and did not have any partitions on the disk, I encrypted the entire drive. I do this so it doesn't show up in windows with a drive letter, it makes the whole thing totally invisible unless you are using something like a disk manager, or the VC drive selection. I've never had a problem with it before, when something asks me to initialize it I just say no. But this program seems to have gone ahead and done it without asking. Originally it was a basic GPT drive, now it is being seen as a dynamic MBR.
Naturally the first thing I did was try to restore the embedded header info, on the few occasions when I've had an issue in the past that has worked perfectly. But this time I got an error message. It is possible I might have an external backup of it somewhere and I'm sure that would make this easier, but so far I haven't been able to find it.
Right now I am in the process of cloning the drive to try some recovery options on the copy, is there a chance that all I need to do is convert it back to a basic GPT drive to be able to access the embedded header info? It would be nice if it was that simple. But if not, what would be the best thing to try?