If you rely on plausible deniability, you should recreate the affected outer file container and its hidden volume using VeraCrypt 1.26.29 or later, then securely erase the old container.
(1) copy the entire contents of the hidden volume to a separate SSD (let's call it SSD #2).
(2) securely erase the entire SSD (let's call it SSD #1) which holds the outer file container and its hidden volume using the SECURE ERASE tool such as is found in Parted Magic.
(3) use Veracrypt v1.26.29 to re-create the outer file container and its hidden volume on SSD #1.
(4) copy the contents of SSD #2 back to the hidden volume of SSD #1.
Am I correct?
Vencent
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
If I understand the above advice given by @enigma2illusion correctly, I must do the following steps:
(1) copy the entire contents of the hidden volume to a separate SSD (let's call it SSD #2).
(2) securely erase the entire SSD (let's call it SSD #1) which holds the outer file container and its hidden volume using the SECURE ERASE tool such as is found in Parted Magic.
(3) use Veracrypt v1.26.29 to re-create the outer file container and its hidden volume on SSD #1.
(4) copy the contents of SSD #2 back to the hidden volume of SSD #1.
Am I correct?
Vencent
Hi Vencent,
In step 1, create new file container on SSD #2 with 1.26.29 version.
Mount old and new outer volumes and copy outer data from old to new.
Then unmount outer volumes.
Mount old and new inner (hidden) volumes and copy inner data from old to new.
Be aware of the following:
https://veracrypt.jp/en/Wear-Leveling.html
https://veracrypt.jp/en/Reallocated%20Sectors.html