dignified
asked on
Scanning for FileSystem Errors on FAT32 External Drive
I'm trying to scan for file system errors on my FAT32 USB drive in OS X.
So far I have just tried:
wasabi:~ me$ fsck_msdos /Volumes/MYDRIVE/
** /Volumes/MYDRIVE/ (NO WRITE)
Invalid BS_jmpBoot in boot block: 47494e
wasabi:~ me$
So far I have just tried:
wasabi:~ me$ fsck_msdos /Volumes/MYDRIVE/
** /Volumes/MYDRIVE/ (NO WRITE)
Invalid BS_jmpBoot in boot block: 47494e
wasabi:~ me$
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
dignified
The problem you had with the 5Gb file ... is to be expected.
FAT32 has an individual file limit of 4Gb .. I suggest you split the 5Gb file into a few smaller pieces to avoid problems.
See this wikipedia article .. http://en.wikipedia.org/wiki/File_Allocation_Table
in particular this paragraph
"The maximum possible size for a file on a FAT32 volume is 4 GiB minus 1 Byte (2321 bytes). For most users, this has become the most nagging limit of FAT32 as of 2007, since video capture and editing applications and some other software can easily exceed this limit."
The problem you had with the 5Gb file ... is to be expected.
FAT32 has an individual file limit of 4Gb .. I suggest you split the 5Gb file into a few smaller pieces to avoid problems.
See this wikipedia article .. http://en.wikipedia.org/wiki/File_Allocation_Table
in particular this paragraph
"The maximum possible size for a file on a FAT32 volume is 4 GiB minus 1 Byte (2321 bytes). For most users, this has become the most nagging limit of FAT32 as of 2007, since video capture and editing applications and some other software can easily exceed this limit."
ASKER