You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It is actually possible to determine what is the current cluster size of a FAT32 partition under Linux, it might be useful to add that information to guide.
The command is:
$ fsck.fat -n -v /dev/<SD card device>
-n here means do a check without changing anything and -v for verbose.
The important part is this section:
Media byte 0xf8 (hard disk)
512 bytes per logical sector
32768 bytes per cluster
64 reserved sectors
So it's possible to see the SD card is formatted with 32 kb cluster size.
The text was updated successfully, but these errors were encountered:
It might not be useful to immediately check the cluster size after formatting.
However it might be useful to check it if you formatted with some other tool or have an old install and you are considering whether you should re-format the SD card or not (moving all files to a PC and back might be very slow, depending on size of card and speed).
In that case you would check.
We don't double-check for Windows either, so if this were to be added, it should be applied to the other operating systems as well.
I'm not very familiar with how to do this on Windows, but I would guess either the properties window or the Disk management tool could easily show this info.
It's a bit unfortunate that GNOME Disks on Linux kinda hides it (although it might be exposed via udisks)
Pages with issue(s)
https://3ds.hacks.guide/formatting-sd-(linux)
Description of the issue(s)
It is actually possible to determine what is the current cluster size of a FAT32 partition under Linux, it might be useful to add that information to guide.
The command is:
$ fsck.fat -n -v /dev/<SD card device>
-n
here means do a check without changing anything and-v
for verbose.The important part is this section:
So it's possible to see the SD card is formatted with 32 kb cluster size.
The text was updated successfully, but these errors were encountered: