#521 Error: Found a atari partition table in /dev/mapper/veracrypt1

[Francewhoa]

Summary:

On Linux, when creating a new VeraCrypt Volume Container between 3.5 and 7.0 TB. After the Container is created. VeraCrypt displays this error message below. Then VeraCrypt automatically permanently deletes this newly created Container.

Steps to reproduce:

1. Using VeraCrypt 1.25.9, create a new Volume Container.

   • VeraCrypt Container configuration:
     • 7 TB
     • Linux Ext 4 (Ext4)
     • Allowed files larger than 4 GB
     • I will mount the volume only on Linux
     • Add Keyfile
   • Operating system:
     • Debian 10 Buster
   • Physical disk:
     • 8 TB capacity
     • Brand new Western Digital. Bought 2022.
     • Empty disk
     • Sata6 connection
   • Disk formatted using gnome-disk-utility 3.30.2. With this configuration:
     • Linux Ext 4 (Ext4)
     • Protected with LUKS. The disk is both mounted and the LUKS password is entered before creating the new VeraCrypt container.
     • With password
     • Fast formatted. Without the "Erase" option.

2. After VeraCrypt is done creating this new VeraCrypt Volume Container, a new window open. With this error message:
   

3. Using any file manager to your liking, such as Double Commander or Nautilus, navigate to the newly created Container Volume file. You can see it. In this example, it is 7 TB in size.
4. Click on OK / Validater button
5. Somehow, VeraCrypt automatically permanently delete the full 7 TB container

---

Note:

• This challenge was confirmed by multiple users:
  * https://sourceforge.net/p/veracrypt/discussion/general/thread/7a3f38a3a2/
  * https://askubuntu.com/questions/1268631/cant-create-a-large-veracrypt-partition-in-hard-drive-found-a-atari-partition
  * https://www.reddit.com/r/VeraCrypt/comments/jprhsi/atari_partition_table_error_when_creating/

• We created 3 Container Volumes. Each are around 7 TB. The first two were successful and did not display this error message. The third one displayed this atari error message.

---

What we tried that did not work:

• Create a first smaller VeraCrypt Volume Container. Minimum 5 GB. This is a success. Delete this first Container. Create a larger Container of 7 TB. This fails. With the same atari error message as above. In other words, creating a 5 GB Container is a success. But creating a Container of 7 TB fails. Both Containers use the exacts same configuration. Same disk. Same device. Same everything else. Only a different size. So this challenge seems to somehow be related to the Container size.

---

Contribution:

Any volunteer for a patch? Both me and the Ubertus.org team would be happy, as volunteer, to contribute testing and documentation, if needed.

[Francewhoa]

Error message

English

mke2fs 1.44.5 (15-Dec-2018)
Found a atari partition table in /dev/mapper/veracrypt1

French

mke2fs 1.44.5 (15-Dec-2018)
Trouvé une table de partitions atari dans devmapper/veracrypt1

[Francewhoa]

We double-checked. Before, during, and after the creation of this new VeraCrypt Volume Container, the partition table format is ext4. Not atari.

[Francewhoa]

I created a ticket on github at https://github.com/veracrypt/VeraCrypt/issues/1038

Same steps to reproduce

[Francewhoa]

Temporary workaround

---

Summary

Using VeraCrypt, create a new Container Volume, using Filesystem field set to None. Mount the Container with Do not mount filesystem option. Using Terminal, execute the appropriate mkfs command to manually and very carefully add the missing partition. Using VeraCrypt, unmount the Container, then mount it. The Container will open without error message :)

---

Detailed Steps

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

1. Using VeraCrypt, create a new Container Volume, using Filesystem / Système field set to None / Aucun.

   

2. Using VeraCrypt, when you mount the Container you created above, click on this Option > button. Check this Do not mount option.

   

   Note: For those not familiar with this super-duper-secret-hidden Do not mount option, it means, that VeraCrypt will try to mount the Volume within VeraCrypt only. But will not yet try to mount this Volume filesystem.

3. Using VeraCrypt main window, right-click on the Container you mounted above. Select the option Properties. Find the Virtual Device / Périphérique Virtuel line. Write down this path. We will use it in the command below.

4. Before running this command below, now would be a good time to backup your valuable data. Because mkfs command, if not configured appropriately, may result in permanent data lost.

5. Using Terminal/Console, execute the appropriate mkfs command to manually add the missing partition to the Volume Container. In the future, you do not need to manually re-add the partition. This is a one time command per Container.

   • Format:
     sudo mkfs.<TYPE OF FILESYSTEM> <PATH TO VIRTUAL DEVICE>

   • Example:
     sudo mkfs.ext4 /dev/mapper/veracrypt1

6. Wait. In average, themkfs command needs up to 60 seconds to add the partition tables. This duration varies depending on your Container size and its present content.

7. Using VeraCrypt, unmount the Container. Then mount it.

8. The Container will open without error message. Joy :) You have successfully temporary resolved this challenge.

Attribution and thanks to "R" for this temporary workaround

[Francewhoa]

Attaching screenshot for my comment above