SOLVED: How to format 4 TB drive for the A329?

[blinkenjim]

Background: I'm primarily a Linux/Mac user, and I know very little about Windows. However, I am and engineer and software developer so I'm familiar with file systems and external drives, etc.

I have a new A329 and a 4 TB SSD in an external enclosure that I'd like to use with it. I'm confused by the apparent contradiction: (a) Viofo says the A329 supports external SSDs up to 4 TB, but (b) the A329 will only support MBR formatted drives. The contradiction is that MBR only supports partitions of up to 2 TB (correct me if I'm wrong, please); GPT is required for larger partitions.

On the other hand, I've read that the limitation is not inherent in the on-disk data structures, but in the software often used to format them. However, every Linux (I'm on Ubuntu 24) app I've tried enforces the 2 TB limit.

I have tried using a program called GUIformat, running in CrossOver/wine, but it doesn't see the drives -- I get an empty list (yes, I've configured drive mappings in the wine settings).

So here's the big question: is it even possible to format an MBR drive with 4 TB partitions? If so, how?

Or is there a workaround -- can the A329 use two 2T partitions if I format the disk that way?

Would appreciate some help.

 

[lufa6977]

I am Debian Bookworm user, I get your point on this.

The manual states to format the SSD in ExFat either with the computer or the camera. My experience has been that 'things' seem to function better when formatted by the dash cam.

The VIOFO OS appears to have a Linux kernel, one would think GPT is/could be used, however there is a lack of transparency about the matter. VIOFO will also tell people to use a 32GB Microsdxc card, formatted to FAT32 to upgrade firmware. I use a 256 or 512 microsdxc, formatted to ExFAT to do upgrades with, and never an issue.

As far as partitions, as far as I know, you can only have one partition on the SSD or the MicroSDXC.

 

[blinkenjim]

Sudden thought: if I connect an SSD with no filesystems at all -- if I delete all the partitions from the SSD -- is the A329 smart enough to handle that situation and format the drive?

I am Debian Bookworm user, I get your point on this.

The manual states to format the SSD in ExFat either with the computer or the camera. My experience has been that 'things' seem to function better when formatted by the dash cam.

The VIOFO OS appears to have a Linux kernel, one would think GPT is/could be used, however there is a lack of transparency about the matter. VIOFO will also tell people to use a 32GB Microsdxc card, formatted to FAT32 to upgrade firmware. I use a 256 or 512 microsdxc, formatted to ExFAT to do upgrades with, and never an issue.

As far as partitions, as far as I know, you can only have one partition on the SSD or the MicroSDXC.

Thanks for the help. I finally figured it out. See other comment.

 

[blinkenjim]

UPDATE: Problem solved.

I had previously attempted connecting the SSD after deleting all its partitions -- that did not work, in either MBR or GPT. I had also tried formatting a single partition with mkfs.vfat, which the camera did not like.

Here's what did work: I created a single, large, 4 TB GPT partition, but did not format it using mkfs.vfat or anything else. Just a single, raw partition. Upon inserting this SSD, the A329 asked if I wanted to format the SSD, I replied Yes, and it then worked.

So the A329 *can* handle GPT SSDs.

 

[Nigel]

The VIOFO OS appears to have a Linux kernel, one would think GPT is/could be used,

We have heard of problems with Apple formatted disks, but I'm wondering if the problem with these is the format rather than MBR/GPT?

The manual states to format the SSD in ExFat

FAT32 with a small sector size can not manage 4TB, but can with larger sector sizes and should work. However the number of files stored is likely to lead to very slow performance, so ExFAT is definitely recommended for any disk/card over 512GB, and probably for 512GB as well.

 

[Nigel]

UPDATE: Problem solved.

I had previously attempted connecting the SSD after deleting all its partitions -- that did not work, in either MBR or GPT. I had also tried formatting a single partition with mkfs.vfat, which the camera did not like.

Here's what did work: I created a single, large, 4 TB GPT partition, but did not format it using mkfs.vfat or anything else. Just a single, raw partition. Upon inserting this SSD, the A329 asked if I wanted to format the SSD, I replied Yes, and it then worked.

So the A329 *can* handle GPT SSDs.

Is it formatted exFAT?

 

[blinkenjim]

Is it formatted exFAT?

Not formatted at all. I am using Ubuntu 24, so the partition was marked as a Linux filesystem, but the camera just ignored that. I did zero out the first portion of the drive:

dd if=/dev/zero of=/dev/sda bs=1M

 

[blinkenjim]

I am Debian Bookworm user, I get your point on this.

The manual states to format the SSD in ExFat either with the computer or the camera. My experience has been that 'things' seem to function better when formatted by the dash cam.

The VIOFO OS appears to have a Linux kernel, one would think GPT is/could be used, however there is a lack of transparency about the matter. VIOFO will also tell people to use a 32GB Microsdxc card, formatted to FAT32 to upgrade firmware. I use a 256 or 512 microsdxc, formatted to ExFAT to do upgrades with, and never an issue.

As far as partitions, as far as I know, you can only have one partition on the SSD or the MicroSDXC.

Ubuntu appears to refer to "ExFat" as "Vfat". If I format a disk with mkfs.vfat, I can then use that disk anywhere an "ExFat" disk is required.

You're right about the one partition and about letting the camera format the partition. See my UPDATE post.

 

[Nigel]

Not formatted at all.

You formatted it in the camera, I was wondering if it had formatted it using FAT32, or exFAT, and what sector size did it use ?

 

[blinkenjim]

We have heard of problems with Apple formatted disks, but I'm wondering if the problem with these is the format rather than MBR/GPT?

I think that may be the issue.

FAT32 with a small sector size can not manage 4TB, but can with larger sector sizes and should work. However the number of files stored is likely to lead to very slow performance, so ExFAT is definitely recommended for any disk/card over 512GB, and probably for 512GB as well.

The key seems to be to let the camera format the partition.

 

[blinkenjim]

You formatted it in the camera, I was wondering if it had formatted it using FAT32, or exFAT, and what sector size did it use ?

Gotcha. I will have to check and get back to you.

 

[lufa6977]

Ubuntu appears to refer to "ExFat" as "Vfat". If I format a disk with mkfs.vfat, I can then use that disk anywhere an "ExFat" disk is required.

You're right about the one partition and about letting the camera format the partition. See my UPDATE post.

As far as I know, Vfat (is a driver) has a 4TB limit and is a FAT compliant system for Linux and MS and whomever decides to use it. Did you specify a FAT-SIZE in the option string?

man mkfs.vfat

You can use Gpart or Disk to check what the actual file system is. Problem with Gpart is it take ownership of the device and that may be problematic with the dash cam. The Disks tool will more easily enable you to mount/de-mount the device and look at, or change the file system. Terminal is always our friend but sometimes, a GUI tool is much simpler.

If you want to play with it a bit, I think this command will work in Ununtu to format exfat:

sudo mkfs.exfat -n LABEL /dev/sda

Of course, you would use what dev name is appropriate.

 

[lufa6977]

Killing that first meg of space was an interesting move and likely blocked out any Sandisk specific area, which is probably good. If you enable Thunar/Nemo to view hidden files, you will probable see a hidden .db file that is created by VIOFO. Best I can see, this database is used for housekeeping and is best left unmolested.

 

[Karagandinez]

I use a 256 or 512 microsdxc, formatted to ExFAT to do upgrades with, and never an issue.

Have you updated all Viofo models they have released this way?

 

[lufa6977]

Have you updated all Viofo models they have released this way?

I have on my A229 Pro dash cams, and as I recall, I have also done so on my A129 Pro. A few days ago, I pulled the San Disk Max Endurance 256 from my A229 Pro, put the new FW in the root directory and flashed the A229 Pro without incident. I did not even format or erase the existing video files on the card. Maybe I am just lucky, or it may be that I use Linux Debian and do the FW download from VIOFO and the copy to the San Disk using Linux. However, I would agree that it is likely better to at least format the microSDXC prior to the FW file copy. I cannot fathom why VIOFO tell people to use a 32GB card formatted to FAT16.

 

[blinkenjim]

As far as I know, Vfat (is a driver) has a 4TB limit and is a FAT compliant system for Linux and MS and whomever decides to use it. Did you specify a FAT-SIZE in the option string?

man mkfs.vfat

You can use Gpart or Disk to check what the actual file system is. Problem with Gpart is it take ownership of the device and that may be problematic with the dash cam. The Disks tool will more easily enable you to mount/de-mount the device and look at, or change the file system. Terminal is always our friend but sometimes, a GUI tool is much simpler.

If you want to play with it a bit, I think this command will work in Ununtu to format exfat:

sudo mkfs.exfat -n LABEL /dev/sda

Of course, you would use what dev name is appropriate.

Yeah, I had forgotten to install the exfat packages. D’oh!

 

[Karagandinez]

I have on my A229 Pro dash cams, and as I recall, I have also done so on my A129 Pro. A few days ago, I pulled the San Disk Max Endurance 256 from my A229 Pro, put the new FW in the root directory and flashed the A229 Pro without incident. I did not even format or erase the existing video files on the card. Maybe I am just lucky, or it may be that I use Linux Debian and do the FW download from VIOFO and the copy to the San Disk using Linux. However, I would agree that it is likely better to at least format the microSDXC prior to the FW file copy. I cannot fathom why VIOFO tell people to use a 32GB card formatted to FAT16.

Not all models can be flashed with a memory card formatted in ExFAT.
I also flash my models by throwing the firmware file into the root of the memory card without deleting the other files.

 

[blinkenjim]

Killing that first meg of space was an interesting move and likely blocked out any Sandisk specific area, which is probably good. If you enable Thunar/Nemo to view hidden files, you will probable see a hidden .db file that is created by VIOFO. Best I can see, this database is used for housekeeping and is best left unmolested.

Once I format the drive, I don’t touch it. I’ve seen the .diskdb file, but its contents were fairly uninteresting and indecipherable so I’ve been ignoring it.

 

[blinkenjim]

As far as I know, Vfat (is a driver) has a 4TB limit and is a FAT compliant system for Linux and MS and whomever decides to use it. Did you specify a FAT-SIZE in the option string?

man mkfs.vfat

You can use Gpart or Disk to check what the actual file system is. Problem with Gpart is it take ownership of the device and that may be problematic with the dash cam. The Disks tool will more easily enable you to mount/de-mount the device and look at, or change the file system. Terminal is always our friend but sometimes, a GUI tool is much simpler.

If you want to play with it a bit, I think this command will work in Ununtu to format exfat:

sudo mkfs.exfat -n LABEL /dev/sda

Of course, you would use what dev name is appropriate.

After formatting in the camera, I can tell you it’s an ExFat partition with a 512 byte sector size. Still trying to determine the cluster size.

 

[blinkenjim]

You formatted it in the camera, I was wondering if it had formatted it using FAT32, or exFAT, and what sector size did it use ?

Here are the details:

# dump.exfat /dev/sda1
exfatprogs version : 1.2.2
-------------- Dump Boot sector region --------------
Volume Length(sectors): 7814033408
FAT Offset(sector offset): 128
FAT Length(sectors): 477056
Cluster Heap Offset (sector offset): 477184
Cluster Count: 61043408
Root Cluster (cluster offset): 120
Volume Serial: 0x5dbe54cf
Sector Size Bits: 9
Sector per Cluster bits: 7

----------------- Dump Root entries -----------------
Volume entry type: 0x3
Volume label:
Volume label character count: 0
Bitmap entry type: 0x81
Bitmap start cluster: 2
Bitmap size: 7630426
Upcase table entry type: 0x82
Upcase table start cluster: 77
Upcase table size: 5836

---------------- Show the statistics ----------------
Cluster size: 65536
Total Clusters: 61043408
Free Clusters: 61030966