Please note that the above advice is for a veracrypt file container not an encrypted partition. I broke a veracrypt partition trying to cat bytes on to the end of the mapper virtual device and just decided to wipe the veracrypt partition and create a new one that fits the size of the device.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Last edit: simgojohn 2018-02-23
Last edit: simgojohn 2018-02-23
Regarding Linux: There was a suggestion for this on superuser. Short summary:
dd if=/dev/urandom bs=1G count=4 >> CONTAINER.vc[1].resize2fson veracrypt entry in/dev/mapperto resize the filesystem inside the resized container.Beware: As far as I can tell this method will make Veracrypt unable to find the backup header, and I don't know if Veracrypt supports recreating it.
[1] On superuser, using
/dev/zerowas suggested, which should mostly be fine; Using random data should be safer however.Please note that the above advice is for a veracrypt file container not an encrypted partition. I broke a veracrypt partition trying to cat bytes on to the end of the mapper virtual device and just decided to wipe the veracrypt partition and create a new one that fits the size of the device.
What is the current state of this dicsussion or any solution?
I could not find this topic in the FAQ.
Can I use the current stable release for resizing?
What is about the Expander-Tool? Could not find an official release on the VeraCrypt website.