#491 Error "VeraCrypt::File::Write:384" When Creating New Volume Container

[Francewhoa]

When creating a new Volume Container, after it is created, VeraCrypt display this message: VeraCrypt::File::Write:384 This is the 1st challenge. This screenshot shows this.

Then, VeraCrypt automatically deletes this newly created Volume Container. This is the second challenge.

The needed end results are that no error message is display and VeraCrypt does not delete the Volume Container

---

Below is the same message as above. But with details if you're interested in those.

Steps to reproduce error

1. Using Debian Buster 10. Using VeraCrypt 1.25.9, create a new Volume Container. Choose the option to use the full available space of the disk.

2. VeraCrypt creates the Volume Container

3. A popup is display. With this error message VeraCrypt::File::Write:384
   The attached screenshot shows this error. This is the second challenge.

4. Usign the popup above, click on the "Validate/Validater" button

5. Without asking, VeraCrypt automatically deletes this newly created Volume Container. This is the second challenge.

6. The needed end results are that no error message is display and VeraCrypt does not delete the Volume Container

What I tried that did not work

• Searched this forum for similar error message

• Searched the website and documentation at https://veracrypt.fr

[Francewhoa]

I was able to reproduce this challenge multiple times. Using various peripherals ranging from 1MB to 20TB.

To be able to reproduce this error, before starting the formatting of the Volume Container, I need to choose the option to use the full available space of the disk. The number 1 in the attached screenshot shows this option and its checkbox.

If this option above is unchecked, I am not able to reproduce this challenge. So this challenge is somehow related to this checkbox.

In the steps to reproduce above, I used this test:

• Peripheral
  • 8TB brand new hard drive
  • Partitioned with LUKS
• VeraCrypt configuration
  • AES(Twofish(Serpent))
  • Whirlpool
  • Ext4
  • Mount on Linux only
  • With keyfile

I tried to edit my ticket to add this new information. But somehow I can't edit my ticket. How do we edit our ticket? I searched both the forum and the documentation of sourceforge. But found no answer.

[Francewhoa]

Something else unusual is that after VeraCrypt is done formatting the Volume Container, I am not prompt to enter my Linux user password. Usually, VeraCrypt always ask for this password.

In comparison, if I do not check the option to use the full available space of the disk, after VeraCrypt is done formatting the Volume Container, I am prompt to enter my password. And the creation of the Volume Container is both a success and not automatically deleted. So this challenge is maybe related to VeraCrypt is missing permission to "write" and finalize this new Volume Container. But somehow, the user is never prompted to allow this permission.

[RealTehreal]

Have you tried to run VeraCrypt from CLI with administrative privileges? Maybe this helps.

[Daw]

So, I had the same problem and tried to look it up for a long long time but couldn't find anything. But eventually I realised that I was trying to create a container that was larger than 4 GB inside a drive that had FAT file system which isn't possible. Reformatted the drive to exFAT and worked like a charm.

[dnoergaard]

I've also encountered this recurring issue while attempting to create a Volume Container on a new 22TB disk. The problem persisted across three attempts, each resulting in the same error, VeraCrypt::File::Write:384.

First Attempt: Initially, I opted for the "use the full available space of the disk" option. However, this led to the aforementioned error.

Second Attempt: In the second attempt, I manually entered the size, noting that the maximum allowable size was 19382GB. To err on the side of caution, I selected a slightly smaller size of 19380GB. Despite this adjustment, the error recurred after approximately 26 hours of VeraCrypt writing the volume.

Third Attempt: For the third attempt, I again chose manual input, this time specifying an even smaller size of 19370GB. Nevertheless, the error persisted after another 26 hours of writing, despite ample remaining disk space (3.2GB - see attached screen shot).

A few details:
Peripheral

• 22TB brand new hard drive containing 1 (20TB) Ext4 formatted partition
  VeraCrypt configuration
• Version: 1.25.9-1
• AES
• SHA-512
• Ext4
• Mount on other OS