Etcher: It always flash fat-16 format to my SD card

Created on 26 Mar 2019  路  7Comments  路  Source: balena-io/etcher

This week I have flashed 3 SD card with different os. But etcher always format the SD card with FAT-16 format which result in I cannot read it in MACOS.

If I can select which format to the SD card system in the future version?

Most helpful comment

I have the same issue! With Mojave! After flashing the card with the latest stretch image, it cannot be opened, no boot. Never had that issue before!
The result looks like that:

/dev/disk3 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: Apple_partition_scheme *15.9 GB disk3
1: Apple_partition_map 4.1 KB disk3s1
2: Apple_HFS 704.5 KB disk3s2

I found the issue! I'm just stupid! The image was to run Raspbian on Mac or PC and not the RaspberryPi Image, that has the "boot" partition where you can edit files...
Maybe this helps someone :)

All 7 comments

Etcher doesn't "format the card" it just copies whatever is in your image file byte-for-byte onto your SD card. So if your SD card is coming out FAT-16 formatted, then the partition in your image file must have been FAT-16 formatted.

I'm surprised to hear that MACOS can't read FAT-16 though :man_shrugging: Have you read https://github.com/balena-io/etcher/blob/master/docs/USER-DOCUMENTATION.md ?

First I init the SD card in MACOS with diskutil partitionDisk /dev/disk2 MBR FAT32 UNTITLED 0b , after that the SD card is FAT32 format , then use etcher to flash the img to SD card. If it works with FAT32, then I can at least read the /boot partition but I cannot. It shows FAT16 format after flash.

I'm actually having the same issue. On that latest version of macOS Mojave using the latest version of Etcher. I used macOS Disk Utility to format the SD Card to FAT32, flashed the image, and then macOS says that it cannot read the SD Card because of the format. If I plug the SD Card into a Windows computer, the format is showing as FAT. The SD Card is also bootable from a Raspberry Pi. This leads me to believe that the SD Card is still a version of FAT but must not be FAT32 which is readable by macOS.

Actually, it seems that it may have something to do with the particular image that I am flashing. I used Disk Utility to format as FAT32 again (SD still readable by macOS) and then used dd to flash the SD card. After dd finished, macOS is reporting that the SD Card is not readable. For future reference, the image is 64bit Hass.io for rPi3B+.

As this evidently has nothing to do with Etcher, my comments can be safely ignored by the maintainers.

Hi, man. Such things I met 2 years ago with it in my last pc with Linux.

From my experience it's actually the Etcher 's problem that it can only used to format the images for Raspberry Pi with certain images.

I have also tried other images for the real pc or just called the AMD64 CPU based computer. As an result, it can even not boot after flash the usb stick using this tool.

What makes me report it not just because it, but this time I cannot even reach the boot folder to create the ssh file on it to enable the sshd service on MacOS system.

But before I tried it on MACOS, the SD card which is flashed from my last PC 'Linux' could be identified in my MACOS. Hope you can understand what I said.

In conclusion, there are now two bugs in this software.

  • It cannot flash the normal images on usb stick for the pc with other platform like X86_64.
  • It cannot flash the FAT32 format space in MACOS.

What I suggest is adding extra options to fit it.

If you are only plan for burn the images for raspberry pi, plz just ignore it!

Etcher does not create partition tables or partitions, it just copies the raw content of your disk image to your disk.

I have the same issue! With Mojave! After flashing the card with the latest stretch image, it cannot be opened, no boot. Never had that issue before!
The result looks like that:

/dev/disk3 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: Apple_partition_scheme *15.9 GB disk3
1: Apple_partition_map 4.1 KB disk3s1
2: Apple_HFS 704.5 KB disk3s2

I found the issue! I'm just stupid! The image was to run Raspbian on Mac or PC and not the RaspberryPi Image, that has the "boot" partition where you can edit files...
Maybe this helps someone :)

Was this page helpful?
0 / 5 - 0 ratings