BUG: Volume Expansion corrupts NTFS containers in 1.24Update 2

Open source disk encryption with strong security for the Paranoid

Brought to you by: idrassi

BUG: Volume Expansion corrupts NTFS containers in 1.24Update 2

Forum: Technical Topics

Creator: Enigma

Created: 2019-12-18

Updated: 2019-12-18

Enigma - 2019-12-18

Attempting to expand any NTFS volume in a file container results in complete corruption of the said container.
The expanded container will mount, but windows sees it as a RAW disk and data seems to be irrecuverable (ie data is gibbirish and data recovery tools can't even find file structures that should be left behind).

I have already lost 900GB to this bug, and have verified it occurs also on a number of test containers I have tried.

Previous versions had no such problem (I dont know about Hotfix 1 as I never expanded a container using that version so dont know if that is affected too).

p.s. I have only tried NTFS containers I can't say if other FS are affected.

Last edit: Enigma 2019-12-18

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Enigma - 2019-12-18

Further investigation looks like it only corrupts the container when "Activate encryption of key and passwords stored in RAM"is enabled. Disable this and the container isnt corrupted.

Still a nasty bug that need squashing.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Log in to post a comment.