Flashed a 64GB micro SD, and while it works fine, the effective size has been reduced to 45MB. I need to put some video files in there too so I need to use the rest of that space.
It’s FAT32, macOS 10.13.6.
I suspect I may have done something wrong when formatting the card, or possibly need to change some options when flashing. Anyoe have any ideas? Experienced the same problem?
Yup @tacLog is correct here! By default macOS does not support the other filesystems used on the card so you can’t see them unless you take a look at some of the methods in the link shared.
Hi, what image are you flashing onto the SD card? Etcher flashes that image exactly, and doesn’t affect your card’s size.
What likely happens, is that the image has partitions that are formatted with a file system which macOS cannot read natively. For example if you are flashing a balenaOS image, there the first partition is a FAT32 partition with about that much size, while, the rest are ext4 partitions, and I think you would see behaviour similar to this, if your system cannot read ext4 file system. You can try to plug the SD card into a Linux machine, or try to erase the partitions on the card currently to check (and then reflash later on), for example following these hints https://github.com/balena-io/etcher/blob/master/docs/USER-DOCUMENTATION.md#recovering-broken-drives
Let us know how it goes, and rest assured, your SD card capacity does not change by flashing it with Etcher.
Correct, macOS doesn’t support extfs. I’d add one thing - there’re free ways how to mount extfs (2, 3, 4) on the macOS, but they’re not reliable. I mean, read only is mostly fine, but read & write has some issues.
If you’re willing to pay, there’re commercial alternatives, like this one.
macOS only supports FAT and it’s this small blue portion. Rest is unsupported. But when you install the commercial SW I linked in the previous post, you can access everything …
Great responses, thank you everyone. I suspected it may have been a mac thing, I usually do this kind of stuff from home on my windows PC and never had a problem like this. I’ll give it a quick go on that before I really get stuck in to mac based fixes.