I recently added some drives to my raid. I used veracrypt expander and it told me everything was fine once it finished. But then when I mount the volume it tells me I have to format before I can use the drive! Anyone know whats causing this, and how to fix it? It was formated with NTFS as it should be (to use the expander tool) and as you can see from ss3, when I do the "check filesystem" in veracrypt, it also says NTFS.
Anyone know why this happened and how to fix it? Any help is much appreciated!
EDIT: I also tried to "Repair file system" in veracrypt, but it didn't find any errors. Said everything was alright.
EDIT2: I'm using Veracrypt 1.24-Hotfix1 on Windows Server 2016, if it matters.
If you have RAM Encryption option enabled then you've fallen prey to a bug in the current versions (just like me) which causes corruption on volume expansion, so far there is no way to recover the contents of the container as it seems to screw something up at the encryption level, so all data read is giberish. :(
I don't have RAM Encryption (I think) and my data isn't corrupted, fortunately. Its just that Windows doesn't seem to recognize the filesystem or something, and tells me to format when I mount the volume.
As you can see from the screenshot I have attached, my recovery program can see folders and also tells me its NTFS. I can recover my data but since I would have to buy some new drives, I would rather fix the problem, if it's possible. Maybe it's not?
I tried to create an encrypted container and expand it the same way I did my raid, and there was no problem mounting and my data was intact. Could it be something when I did wrong when I extended the volume in disk management? I mean, there is not many different ways to do this...
This is the second time it's happened to me with my encrypted raid volume. I have no clue what I'm doing wrong. Maybe I'll just have to stop using encryption if I can't figure out whats causing the problem :\ I don't want this to happen a third time when I'm expanding in the future. Would have been pretty sweet if there could be a guide (preferably with screenshots) in the documentation page for Veracrypt on how to expand raid volume, because I seem to be too much of a newbie to make it work :P
Sorry to bump this, but I'm finally done recovering files from the raid, so now I have to format...
Nobody knows what may have caused this issue? Anything I might have done wrong or doesn't Verecrypt work well when expanding raids? I would really like to continue to use Veracrypt, but this is the second time it has happened to me. I'm not sure what to do... Anyone have any suggestions?
Any help is appreciated!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I recently added some drives to my raid. I used veracrypt expander and it told me everything was fine once it finished. But then when I mount the volume it tells me I have to format before I can use the drive! Anyone know whats causing this, and how to fix it? It was formated with NTFS as it should be (to use the expander tool) and as you can see from ss3, when I do the "check filesystem" in veracrypt, it also says NTFS.
Anyone know why this happened and how to fix it? Any help is much appreciated!
EDIT: I also tried to "Repair file system" in veracrypt, but it didn't find any errors. Said everything was alright.
EDIT2: I'm using Veracrypt 1.24-Hotfix1 on Windows Server 2016, if it matters.
Last edit: Joe Hax 2019-12-30
If you have RAM Encryption option enabled then you've fallen prey to a bug in the current versions (just like me) which causes corruption on volume expansion, so far there is no way to recover the contents of the container as it seems to screw something up at the encryption level, so all data read is giberish. :(
See Ticket : https://sourceforge.net/p/veracrypt/tickets/305/
Forum: https://sourceforge.net/p/veracrypt/discussion/technical/thread/810d99acfc/
Last edit: Enigma 2020-01-06
Hey Enigma! Thanks for the reply!
I don't have RAM Encryption (I think) and my data isn't corrupted, fortunately. Its just that Windows doesn't seem to recognize the filesystem or something, and tells me to format when I mount the volume.
As you can see from the screenshot I have attached, my recovery program can see folders and also tells me its NTFS. I can recover my data but since I would have to buy some new drives, I would rather fix the problem, if it's possible. Maybe it's not?
I tried to create an encrypted container and expand it the same way I did my raid, and there was no problem mounting and my data was intact. Could it be something when I did wrong when I extended the volume in disk management? I mean, there is not many different ways to do this...
This is the second time it's happened to me with my encrypted raid volume. I have no clue what I'm doing wrong. Maybe I'll just have to stop using encryption if I can't figure out whats causing the problem :\ I don't want this to happen a third time when I'm expanding in the future. Would have been pretty sweet if there could be a guide (preferably with screenshots) in the documentation page for Veracrypt on how to expand raid volume, because I seem to be too much of a newbie to make it work :P
Sorry to bump this, but I'm finally done recovering files from the raid, so now I have to format...
Nobody knows what may have caused this issue? Anything I might have done wrong or doesn't Verecrypt work well when expanding raids? I would really like to continue to use Veracrypt, but this is the second time it has happened to me. I'm not sure what to do... Anyone have any suggestions?
Any help is appreciated!