Mounted container while Veracrypt was expanding it and now it doesn't show...
Open source disk encryption with strong security for the Paranoid
Brought to you by:
idrassi
Menu
▾
▴
So, basically that's what happened. I mounted the container in the exact moment VC was trying to update the header and was trying to mount the container so it throwed an error message stating that the container was already mounted. Now the container doesn't show the new space but the space is already taken by the container because its size has increased and the available space on the hard drive has decreased. Fill empty space was ticked.
Is there a way to make VC resume the expanding process or to expand the partition? Or my only option is create a new container, move all the files to the new one and delete the old?
My container is aprox 1Tb so I'm trying to avoid re-creating the container and move all the files, also I don't currently have enough available space and I can't get out of my house without counting the fact that there is no tech store open in my country until the end of march. I didn't mounted the container manually, I executed a batch script and forgot that it was suppose to mount the container I was expanding along other stuff.
VC reports that the container is 965 GB big but the mounted partition is still 955 GB.
Thanks.
Till this day I haven't touched the container so I haven't "fixed" this but do you think that if I expand the container again, it will now show the 10 GB missing plus whatever amount I'm expanding this time?
I'm kinda worried that I may lost this container in doing such thing so I'm probably first going to back up the container the moment I get another HDD before doing anything.
Assuming this is a container internally formatted as NTFS (which is the only filesystem that can successfully be expanded), I would start with a simple report by running the Windows command "chkdsk." You don't have to run this from the command line, though, as VeraCrypt can run the command for you. From the main VeraCrypt window where you see the mounted drive, right-click on the correct drive and choose "Check Filesystem." Depending on what the report says, you may then want to choose "Repair Filesystem" from that same context menu, which would run the underlying Windows command "chkdsk /f" on the drive. I don't know if the specific problem you have will be fixed, but it's very unlikely to cause any damage to your container.
If that doesn't work, I also like your idea of trying another minimal expansion in the hopes that VeraCrypt can correct the filesystem to show the sum of the two expansions. That seems plausible.
So good luck! I haven't forgotten what it's like to be short on disk space for fixing various problems.
Thanks for your input!
After searching through all my drives (because I was eager to see the results of this) I found one with enough free space, so I made the backup and also a backup of the header, just in case, and proceeded to expand the drive because I didn't check the topic for replies and didn't read your advice (didn't had much hopes on getting any reply in so little time, so thanks for that again) so I didn't check the filesystem before doing this but luckily VC managed to expand the drive and corrected the available space. I'm checking random files to see if anything is corrupted first but so far so good. Apparently our hunch was right.
You're very generous. I'm glad YOUR hunch was right :)