exFAT volume often gets corrupted

Sounds like you didn't type 'sudo' infront of the command. And from the looks of it I didn't write that in the original solution, sorry.

So, with your disk and partition try this:

sudo fsck_exfat -d disk0s4

Not sure why i left sudo out in the original post, apologies.

Neo Amiga, it's official.

you are the best thing that's ever happened to the apple website!!!

YOU SO HAVE MY RESPECT!

T H A N K S

For some reason when I run that in terminal I get:

Eths-MacBook-Pro-2013:~ ethanaylett$ fsck_exfat -d disk0s4

fsck_exfat: Can't open /dev/rdisk0s4: Opening /dev/rdisk0s4

No such file or directory

Am I plugging in the wrong device name?

I may have done it. I now get this:

Eths-MacBook-Pro-2013:~ ethanaylett$ fsck_exfat -d disk2

Opening /dev/rdisk2

fsck_exfat: Can't open /dev/rdisk2: Permission denied

Eths-MacBook-Pro-2013:~ ethanaylett$ sudo fsck_exfat -d disk2

Opening /dev/rdisk2

fsck_exfat: Opened /dev/rdisk2 read-only

** Checking volume.

** Checking main boot region.

fsck_exfat: Invalid jump or signature

Main boot region is invalid. Trying alternate boot region.

** Checking alternate boot region.

fsck_exfat: Invalid jump or signature

Alternate boot region is invalid.

** The volume could not be verified completely.

Yes. disk0s4 was the partition in my case, but there's nothing sayting that it's that in your setup. You could start with running this in the terminal.

diskutil list

In my setup that gives me

So in the output at your place you have to find the 'name' of your partition and look to the right in the 'identifier' column and use that partition identifier in the command. In your last example you just use 'disk2' which isn't a partition identifier but the disk itself.

Hope this helps.

Cheers

NEO_AMiGA, you definitely saved me as well. I thought using a LaCie Rugged external drive would keep corruption from physical damage to a minimum only to be handicapped by exFat and boy did I exhaust all of my expertise (including extensive work on Ubuntu and CentOS). As an additional word, for some reason running 'sudo fsck -d /dev/disk###' did not work. I had to run it as 'sudo fsck -d disk###' Curious syntax... Thanks A Million!!!

Perfect! For a while there I thought I would never be able to joint the NEO_AMiGA praise wagon, but I can now say it with everyone else, "YOU ROCK!"

"diskutil list" got me my partition identifier and I used "sudo fsck_exfat -d disk6s2" and it asked for my password and it was done. It's amazing. Thank you!

What does it mean if the resonse given is:

Can't open /dev/rdisk5s2: Resource busy

Opening /dev/rdisk5s2

Ujayank, can you please be more specific in your query? In what context are you getting the "can't open /dev/rdisk5s2: Resource Busy" prompt? What command are you executing in terminal?

sudo fsck_exfat -d disk5s2

I ended up restarting and the drive mounted. Still don't know what that "...Resource Busy" prompt was, but it may or may not have mattered.

Can you help me with that annoying error?

I don't know what's going on with this HD

Its been a while since anyone checked this thread but I was super excited to see this workaround now that my once every few months boot up in Windows and a Recuva session to copy the files on the exFAT with hierarchy intact won't work because my boot camp partition (which shares space with the exFAT partition) is no longer listed as a start up disk.

When I tried the wonder trick above posted by NEO-AMIGA I get this:

$ fsck_exfat -d disk1s2

Opening /dev/rdisk1s2

fsck_exfat: Can't open /dev/rdisk1s2: Permission denied

Anyone got a way to get around tho new layer of denial? I'm not a seasoned terminal operator so I may be doing something wrong.

I fixed it, just like everyone else...SUDO was needed.

Kudos to Neo_Amiga!!!

I am having the same issue. have you figured out the fix yet?