Skip to content

Instantly share code, notes, and snippets.

Embed
What would you like to do?
Fix corrupted exFAT disk macOS/OSX

exFAT support on macOS seems to have some bugs because my external drives with exFAT formatting will randomly get corrupted.

Disk Utility is unable to repair this at first, but the fix is this:

  1. Use diskutil list to find the right drive id.
  2. You want the id under the IDENTIFIER column, it should look like disk1s1
  3. Run sudo fsck_exfat -d <id from above>. eg sudo fsck_exfat -d disk1s3
  4. -d is debug so you'll see all your files output as they're processed.
  5. Answer YES if it gives you the prompt Main boot region needs to be updated. Yes/No?
  6. Open Disk Utility and you should be able to repair here successfully.

See the apple man page below for details on the fsck_exfat utility.

Sources/Extra Reading: https://developer.apple.com/legacy/library/documentation/Darwin/Reference/ManPages/man8/fsck_exfat.8.html https://craigsmith.id.au/2014/07/06/repairing-a-corrupted-mac-osx-exfat-partition/ https://discussions.apple.com/thread/4154638?tstart=0

@Alex-Swann

This comment has been minimized.

Copy link

@Alex-Swann Alex-Swann commented Jun 14, 2018

Thanks man. This saved me being suckered into a $80 disk recovery app.

@ashutoshdesign

This comment has been minimized.

Copy link

@ashutoshdesign ashutoshdesign commented Aug 24, 2018

I'm getting an error saying- "Can't open /dev/rdisk2s2: Resource Busy". What do I do?

@michaelmruta

This comment has been minimized.

Copy link

@michaelmruta michaelmruta commented Sep 2, 2018

@ashutoshdesign you can try doing the command in single-user mode by holding ⌘+S on boot-up just after pressing the power button of your mac.

@sriharshachilakapati

This comment has been minimized.

Copy link

@sriharshachilakapati sriharshachilakapati commented Sep 25, 2018

I'm getting this error:

21 clusters were marked used, but not referenced
0 clusters were marked used and CLUST_BAD
3 clusters were marked free, but referenced
** Rechecking main boot region.
** Rechecking alternate boot region.
Write     offset = 0x000003c00000  length = 0x020000
fsck_exfat: Couldn't write 131072 bytes at offset 62914560: Bad file descriptor

What should I do?

@sriharshachilakapati

This comment has been minimized.

Copy link

@sriharshachilakapati sriharshachilakapati commented Sep 25, 2018

EDIT: If you ever happen to find my error, just ignore that and go to Disk Utility. It should now repair fine.

It appears to be stuck, but actually works. Took 30 minutes to repair my 2TB external HDD from Seagate.

@occupiedUsername

This comment has been minimized.

Copy link

@occupiedUsername occupiedUsername commented Jan 4, 2019

@ashutoshdesign you can try doing the command in single-user mode by holding ⌘+S on boot-up just after pressing the power button of your mac.

This worked for me.

THANK YOU!

@Mathy5

This comment has been minimized.

Copy link

@Mathy5 Mathy5 commented Jan 19, 2019

Hi guys! After had typed “sudo fsck_exfat -d disk1s1” in single-user mode my Mac is working for like 9h till now. Ok the hdd has inside like 1.2T of 2T but, damn...

@simonjpartridge

This comment has been minimized.

Copy link

@simonjpartridge simonjpartridge commented Feb 12, 2019

To fix the error "Can't open /dev/rdisk2s2: Resource Busy". you can download and launch Disk Arbitrator to prevent the disk from being mounted when is is plugged in.

@djruess

This comment has been minimized.

Copy link

@djruess djruess commented Mar 6, 2019

Thank you @scottopell This solved my problem!

@cheTesta

This comment has been minimized.

Copy link

@cheTesta cheTesta commented Mar 19, 2019

Or @djruess eventually, you could run the above mentioned commands in terminal entering in macOS recovery mode, opening terminal from there!

@davur

This comment has been minimized.

Copy link

@davur davur commented Apr 3, 2019

I'm getting an error saying- "Can't open /dev/rdisk2s2: Resource Busy". What do I do?

I was stuck with "Resource Busy" too, but a comment on the Source link (on craigsmith.id.au) describes how to find and kill the process locking the resource which worked for me.

ps -ax | grep disk2 (but your disk)
13699 ?? 11:52.83 /System/Library/Filesystems/hfs.fs/Contents/Resources/./fsck_hfs -y /dev/disk2s2

sudo kill 13699

Once the offending process is killed, I got an OS prompt about an error mounting the drive (something along the lines of it being mounted in read only mode, don't remember the wording). After that the drive mounted in Finder and Disk Utility and I was able to run "First Aid" using "Disk Utility"

@Seluj78

This comment has been minimized.

Copy link

@Seluj78 Seluj78 commented Apr 25, 2019

I am running the sudo fsck_exfat -d on my 4TB drive. Hopefully it won't take too long

@bcomnes

This comment has been minimized.

Copy link

@bcomnes bcomnes commented May 18, 2019

It works, but it takes a long time

@yogesh2jadhav

This comment has been minimized.

Copy link

@yogesh2jadhav yogesh2jadhav commented Jun 3, 2019

Apples-MacBook-Pro:/ Yogesh$ sudo fsck_exfat -d disk3s1
Opening /dev/rdisk3s1
** 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.

What to do in such case...?

@tfkproject

This comment has been minimized.

Copy link

@tfkproject tfkproject commented Jun 5, 2019

Apples-MacBook-Pro:/ Yogesh$ sudo fsck_exfat -d disk3s1
Opening /dev/rdisk3s1
** 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.

What to do in such case...?

I got same problem here. What should I do?

@cowteets

This comment has been minimized.

Copy link

@cowteets cowteets commented Jul 14, 2019

I keep getting stuck at the "** Checking main boot region" portion

after working for a few min i get a "Could Not Read Boot Region" error, every time.
Anyone else? Help?

@ronylucca

This comment has been minimized.

Copy link

@ronylucca ronylucca commented Aug 18, 2019

I've got 'Invalid jump or signature' but when I tried to mount got success. Problem solved. Probably some process was blocking the drive even after reboot.
Thanks man!

@bcbrendan

This comment has been minimized.

Copy link

@bcbrendan bcbrendan commented Sep 5, 2019

I keep getting stuck at the "** Checking main boot region" portion

after working for a few min i get a "Could Not Read Boot Region" error, every time.
Anyone else? Help?

I get this, too. Very frustrating.

Opening /dev/rdisk5s3 ** Checking volume. ** Checking main boot region. fsck_exfat: Could not read boot region ** The volume could not be verified completely.

With that said, my TV is no longer able to access the drive, either—this is a HDD that I use for storing movies, etc.—so I'm equally concerned that the drive could be damaged.

@dghein

This comment has been minimized.

Copy link

@dghein dghein commented Sep 7, 2019

happening on brand new thumb drive for some reason was read only out of the box. same deal with a terabyte hard drive. any format, fat32, exfat, macos journaled, etc. is unwritable. tried creating directories and modifying permissons in /Volumes/ also with no luck. any suggestions would be appreciated!

@windhost

This comment has been minimized.

Copy link

@windhost windhost commented Oct 13, 2019

got it too

** 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.
@WeijieZhu0204

This comment has been minimized.

Copy link

@WeijieZhu0204 WeijieZhu0204 commented Nov 8, 2019

awesome work!

@SikSo1897

This comment has been minimized.

Copy link

@SikSo1897 SikSo1897 commented Nov 19, 2019

thx ☺️ you saved me

@yogesh2jadhav

This comment has been minimized.

Copy link

@yogesh2jadhav yogesh2jadhav commented Nov 19, 2019

Sikso1897 and WeijieZhu0204 which commands helped u?

@pkorson

This comment has been minimized.

Copy link

@pkorson pkorson commented Nov 30, 2019

Just wanted to say thanks. Took less than 10min for me to get my 8tb external back.

@PrasannaBrabourame

This comment has been minimized.

Copy link

@PrasannaBrabourame PrasannaBrabourame commented Dec 3, 2019

When i tried the above command i am getting response as
fsck_exfat: Can't open /dev/rdisk2s2: Resource busy

@maotisimo

This comment has been minimized.

Copy link

@maotisimo maotisimo commented Dec 12, 2019

Thank you very much Scottopell, worked for me and saved a lot of very important things. Thank you for sharing this solution.

@theIYD

This comment has been minimized.

Copy link

@theIYD theIYD commented Jan 4, 2020

I'm getting an error saying- "Can't open /dev/rdisk2s2: Resource Busy". What do I do?

I was stuck with "Resource Busy" too, but a comment on the Source link (on craigsmith.id.au) describes how to find and kill the process locking the resource which worked for me.

ps -ax | grep disk2 (but your disk)
13699 ?? 11:52.83 /System/Library/Filesystems/hfs.fs/Contents/Resources/./fsck_hfs -y /dev/disk2s2

sudo kill 13699

Once the offending process is killed, I got an OS prompt about an error mounting the drive (something along the lines of it being mounted in read only mode, don't remember the wording). After that the drive mounted in Finder and Disk Utility and I was able to run "First Aid" using "Disk Utility"

Worked perfectly fine for me

@mareksimunek

This comment has been minimized.

Copy link

@mareksimunek mareksimunek commented Feb 17, 2020

^yep above also worked for me. Thanks you very much 3TB WD elements, 10.14.6 osx, ext4 filesystem.

@stergios-dot

This comment has been minimized.

Copy link

@stergios-dot stergios-dot commented Feb 28, 2020

supper useful, just saved me from a STROKE
now i'm going to do my back up as usual

@cfc4n

This comment has been minimized.

Copy link

@cfc4n cfc4n commented Mar 13, 2020

I'm getting an error saying- "Can't open /dev/rdisk2s2: Resource Busy". What do I do?

I was stuck with "Resource Busy" too, but a comment on the Source link (on craigsmith.id.au) describes how to find and kill the process locking the resource which worked for me.

ps -ax | grep disk2 (but your disk)
13699 ?? 11:52.83 /System/Library/Filesystems/hfs.fs/Contents/Resources/./fsck_hfs -y /dev/disk2s2

sudo kill 13699

Once the offending process is killed, I got an OS prompt about an error mounting the drive (something along the lines of it being mounted in read only mode, don't remember the wording). After that the drive mounted in Finder and Disk Utility and I was able to run "First Aid" using "Disk Utility"

Worked perfectly fine for me

me too,thanks you very much...

@Krellan

This comment has been minimized.

Copy link

@Krellan Krellan commented Apr 25, 2020

Thanks! This is what i needed.

I made the mistake of formatting a large external hard drive ExFAT.

Should have done it MacOS Extended (Journaled).

Although I unmounted it cleanly, it still came back dirty. Although the drive was fine, it wouldn't mount. Nothing showed up in Finder. No obvious error messages. It was clearly visible in diskutil list. The drive was perfectly visible, but nothing would mount it. Using fsck_exfat from the command line resulted in the error message Resource busy.

The good news was that, somehow, the system was already running the fsck_exfat program behind the scenes! Using ps revealed it. It was being ran by diskarbitrationd. It also appeared in Activity Monitor.

It's kind of weird that Apple wouldn't put up a progress bar or anything friendly like that. It took over 1 full hour to run. Simply waiting it out did the trick. My external hard drive mounted normally, without incident, after over an hour of waiting.

Now, I'm using rsync to copy all files to a second hard drive. Then, going to erase and reformat this ExFAT drive as MacOS Extended (Journaled) then copy everything back! Wish me luck....

@201411108

This comment has been minimized.

Copy link

@201411108 201411108 commented Apr 28, 2020

You save my life. Thanks for your tips

@flip112

This comment has been minimized.

Copy link

@flip112 flip112 commented May 9, 2020

Thanks a lot, this worked for me pretty fine, just like a charm got my exFAT 5TB writable again.

Owe you a drink!

Environment: OS Catalina with Seagate 5TB external disk drive,
First, plug usb, device doesn't mount by itself, then I opened console and executed sudo fcsk_exfat -d disk3s2
Console starts listing and checking all files inside partition, hold on until finishing, in my case didn't need to finish it. It was fixed at beginning.

@lilrkt

This comment has been minimized.

Copy link

@lilrkt lilrkt commented Jun 6, 2020

I'm getting an error saying- "Can't open /dev/rdisk2s2: Resource Busy". What do I do?

I was stuck with "Resource Busy" too, but a comment on the Source link (on craigsmith.id.au) describes how to find and kill the process locking the resource which worked for me.

ps -ax | grep disk2 (but your disk)
13699 ?? 11:52.83 /System/Library/Filesystems/hfs.fs/Contents/Resources/./fsck_hfs -y /dev/disk2s2

sudo kill 13699

Once the offending process is killed, I got an OS prompt about an error mounting the drive (something along the lines of it being mounted in read only mode, don't remember the wording). After that the drive mounted in Finder and Disk Utility and I was able to run "First Aid" using "Disk Utility"

Thank you so much for posting this.
ExFAT... never again.

@ethanyanjiali

This comment has been minimized.

Copy link

@ethanyanjiali ethanyanjiali commented Jul 4, 2020

I'm getting an error saying- "Can't open /dev/rdisk2s2: Resource Busy". What do I do?

I was stuck with "Resource Busy" too, but a comment on the Source link (on craigsmith.id.au) describes how to find and kill the process locking the resource which worked for me.

ps -ax | grep disk2 (but your disk)
13699 ?? 11:52.83 /System/Library/Filesystems/hfs.fs/Contents/Resources/./fsck_hfs -y /dev/disk2s2

sudo kill 13699

Once the offending process is killed, I got an OS prompt about an error mounting the drive (something along the lines of it being mounted in read only mode, don't remember the wording). After that the drive mounted in Finder and Disk Utility and I was able to run "First Aid" using "Disk Utility"

Thank you! This is exactly what happened in my case. The system kept trying to mount the disk and made it busy, but the disk has to be fixed before mounting, which forms a deadlock and my Macbook was just running hot as hell.

@tomasproano

This comment has been minimized.

Copy link

@tomasproano tomasproano commented Jul 7, 2020

I'm getting an error saying- "Can't open /dev/rdisk2s2: Resource Busy". What do I do?

I was stuck with "Resource Busy" too, but a comment on the Source link (on craigsmith.id.au) describes how to find and kill the process locking the resource which worked for me.

ps -ax | grep disk2 (but your disk)
13699 ?? 11:52.83 /System/Library/Filesystems/hfs.fs/Contents/Resources/./fsck_hfs -y /dev/disk2s2

sudo kill 13699

Once the offending process is killed, I got an OS prompt about an error mounting the drive (something along the lines of it being mounted in read only mode, don't remember the wording). After that the drive mounted in Finder and Disk Utility and I was able to run "First Aid" using "Disk Utility"

Worked perfectly fine for me

Thank you, this also worked for me!

@shashikantkulkarni

This comment has been minimized.

Copy link

@shashikantkulkarni shashikantkulkarni commented Jul 18, 2020

ps -ax | grep disk

and then sudo kill <process_id>

This fixed my problem. This is much easier and quick solution.

@george-roussos

This comment has been minimized.

Copy link

@george-roussos george-roussos commented Sep 5, 2020

Hi, once again github and a kind man saves the day. No words to express my gratitude. Thank you.

@ProjectileObjects

This comment has been minimized.

Copy link

@ProjectileObjects ProjectileObjects commented Sep 14, 2020

Lifesaver!

@harolsblog

This comment has been minimized.

Copy link

@harolsblog harolsblog commented Oct 10, 2020

Hello guys. Nothing worked for me. Tried, disk utility, terminal, single user mode, recovery mode. Nothing worked. Ended up pluging the drive into a windows 10 machine. And it recognized it inmediately. All my files there. So I’m copying them from that windows machine and then plan on reformatting the drive as APFS - GUID Scheme.

@giomurru

This comment has been minimized.

Copy link

@giomurru giomurru commented Oct 27, 2020

I'm getting an error saying- "Can't open /dev/rdisk2s2: Resource Busy". What do I do?

I was stuck with "Resource Busy" too, but a comment on the Source link (on craigsmith.id.au) describes how to find and kill the process locking the resource which worked for me.

ps -ax | grep disk2 (but your disk)
13699 ?? 11:52.83 /System/Library/Filesystems/hfs.fs/Contents/Resources/./fsck_hfs -y /dev/disk2s2

sudo kill 13699

Once the offending process is killed, I got an OS prompt about an error mounting the drive (something along the lines of it being mounted in read only mode, don't remember the wording). After that the drive mounted in Finder and Disk Utility and I was able to run "First Aid" using "Disk Utility"

Wait, this means that macOS was already taking care about the problem, automatically running filesystem check on the partition. If you notice, the process that is using the disk is fsck_hfs. I had the same problem but I didn't kill it, I just waited 10 minutes that the process finished doing its thing and it solved the problem. After a while the partition was mounted again automatically. My suggestion to all of you, when something like this happens be patient and just wait a little more to let macOS do its things.

@lilloraffa

This comment has been minimized.

Copy link

@lilloraffa lilloraffa commented Oct 31, 2020

Hi all, I’m getting the following error when I launch /sbin/fsck_exfat -d disk2s2:

fsck_exfat: Can’t open /dev/rdisk2s2: Operation not permitted

Can anybody help me? Thanks!

@lilloraffa

This comment has been minimized.

Copy link

@lilloraffa lilloraffa commented Oct 31, 2020

Hi all, I’m getting the following error when I launch /sbin/fsck_exfat -d disk2s2:

fsck_exfat: Can’t open /dev/rdisk2s2: Operation not permitted

Can anybody help me? Thanks!

I was in single user mode... I tried normally following below instruction, and just by killing the pending process solved my issue. Thanks a lot for the thread!

@jahbungle

This comment has been minimized.

Copy link

@jahbungle jahbungle commented Nov 2, 2020

HI, I have a 4TB seagate external drive formatted ExFat and I use MacOs Yosemtie. I also use a laptop MACOS Mojave. I have the same problem on both macs.

My drive just died today. I have followed lots of tutorials on how to fix the drive using Disk Utility (drive doesnt show up) , I have used terminal and i get the message :
fsck_exfat: Can't open /dev/rdisk1s4: No such file or directory

I have used single user mode fsck and got the same message.

is there any way that I can fix my drive and recover my data stored on there.
Pulling my hair out, thanks in advance. C

@lasithasenadheera

This comment has been minimized.

Copy link

@lasithasenadheera lasithasenadheera commented Nov 6, 2020

I accidentally hit the power pack of WD 6TB hard drive that used be attached to my Mac mini. Mac did not read the drive after reconnecting but Windows 10 did.
This fixed the issue. Now it's working....!!! Thanks you.

@yoni-g

This comment has been minimized.

Copy link

@yoni-g yoni-g commented Dec 13, 2020

Thanks @davur

@DKayB68

This comment has been minimized.

Copy link

@DKayB68 DKayB68 commented Dec 18, 2020

Thanks so much!!

@nullfy

This comment has been minimized.

Copy link

@nullfy nullfy commented Jan 4, 2021

I'm getting an error saying- "Can't open /dev/rdisk2s2: Resource Busy". What do I do?

I was stuck with "Resource Busy" too, but a comment on the Source link (on craigsmith.id.au) describes how to find and kill the process locking the resource which worked for me.

ps -ax | grep disk2 (but your disk)
13699 ?? 11:52.83 /System/Library/Filesystems/hfs.fs/Contents/Resources/./fsck_hfs -y /dev/disk2s2

sudo kill 13699

Once the offending process is killed, I got an OS prompt about an error mounting the drive (something along the lines of it being mounted in read only mode, don't remember the wording). After that the drive mounted in Finder and Disk Utility and I was able to run "First Aid" using "Disk Utility"

thx, it's working for me
Can't open (Resource busy)

@nc-aura

This comment has been minimized.

Copy link

@nc-aura nc-aura commented Jan 18, 2021

To fix the error "Can't open /dev/rdisk2s2: Resource Busy". you can download and launch Disk Arbitrator to prevent the disk from being mounted when is is plugged in.

thanks, this definitely helps to prevent resource busy

@almarcano

This comment has been minimized.

Copy link

@almarcano almarcano commented Jan 20, 2021

I'm getting an error saying- "Can't open /dev/rdisk2s2: Resource Busy". What do I do?

I was stuck with "Resource Busy" too, but a comment on the Source link (on craigsmith.id.au) describes how to find and kill the process locking the resource which worked for me.

ps -ax | grep disk2 (but your disk)
13699 ?? 11:52.83 /System/Library/Filesystems/hfs.fs/Contents/Resources/./fsck_hfs -y /dev/disk2s2

sudo kill 13699

Once the offending process is killed, I got an OS prompt about an error mounting the drive (something along the lines of it being mounted in read only mode, don't remember the wording). After that the drive mounted in Finder and Disk Utility and I was able to run "First Aid" using "Disk Utility"

Thank you so much @davur you save my disk!!!

@tomfu

This comment has been minimized.

Copy link

@tomfu tomfu commented Jan 24, 2021

This worked! Thank you!!!

@FalconBFR

This comment has been minimized.

Copy link

@FalconBFR FalconBFR commented Feb 5, 2021

This worked! :)

This is a life safer! Thanks so much! A Million Thanks won't be enough to express my gratitude! Thanks!!!!!!!!!

@akashrajpal

This comment has been minimized.

Copy link

@akashrajpal akashrajpal commented Feb 7, 2021

@ashutoshdesign you can try doing the command in single-user mode by holding ⌘+S on boot-up just after pressing the power button of your mac.

Thanks. This helped. I have had lot of disk failures. I try to be careful but it seems I'm not. Is there a file format which is safest for accidental usb disk removal without proper eject. Which fileformat fat/exfat/HFS/NTFS is most safe for mac usb use

@Emanuele-Spatola

This comment has been minimized.

Copy link

@Emanuele-Spatola Emanuele-Spatola commented Feb 22, 2021

thanks a lot! that worked!

@steviegayet

This comment has been minimized.

Copy link

@steviegayet steviegayet commented Mar 4, 2021

It worked, I think I owe you a drink !! :)

@pravin772

This comment has been minimized.

Copy link

@pravin772 pravin772 commented Mar 20, 2021

I'm getting an error saying- "Can't open /dev/rdisk2s2: Resource Busy". What do I do?

I was stuck with "Resource Busy" too, but a comment on the Source link (on craigsmith.id.au) describes how to find and kill the process locking the resource which worked for me.

ps -ax | grep disk2 (but your disk)
13699 ?? 11:52.83 /System/Library/Filesystems/hfs.fs/Contents/Resources/./fsck_hfs -y /dev/disk2s2

sudo kill 13699

Once the offending process is killed, I got an OS prompt about an error mounting the drive (something along the lines of it being mounted in read only mode, don't remember the wording). After that the drive mounted in Finder and Disk Utility and I was able to run "First Aid" using "Disk Utility"

Thanks mate!! finally got to use hard disk.

@mohamednidsaid

This comment has been minimized.

Copy link

@mohamednidsaid mohamednidsaid commented Apr 6, 2021

I'm getting an error saying- "Can't open /dev/rdisk2s2: Resource Busy". What do I do?

I was stuck with "Resource Busy" too, but a comment on the Source link (on craigsmith.id.au) describes how to find and kill the process locking the resource which worked for me.

ps -ax | grep disk2 (but your disk)
13699 ?? 11:52.83 /System/Library/Filesystems/hfs.fs/Contents/Resources/./fsck_hfs -y /dev/disk2s2

sudo kill 13699

Once the offending process is killed, I got an OS prompt about an error mounting the drive (something along the lines of it being mounted in read only mode, don't remember the wording). After that the drive mounted in Finder and Disk Utility and I was able to run "First Aid" using "Disk Utility"

thx, it's working for me
Can't open (Resource busy)

this is the one that helped me I'm grateful

@DenaFrancis

This comment has been minimized.

Copy link

@DenaFrancis DenaFrancis commented Apr 9, 2021

I have tried your suggestions @scottopell but it has not worked for me. What should I do next?

$ sudo fsck_exfat /dev/disk2s2
Password:
** Checking volume.
** Checking main boot region.
fsck_exfat: Could not read boot region
** The volume  could not be verified completely.
$ sudo fsck_exfat -d disk2s2
Password:
Opening /dev/rdisk2s2
** Checking volume.
** Checking main boot region.
fsck_exfat: Could not read boot region
** The volume  could not be verified completely.
@kakty3

This comment has been minimized.

Copy link

@kakty3 kakty3 commented Apr 23, 2021

Dude, thank you so much!

@cannyboy

This comment has been minimized.

Copy link

@cannyboy cannyboy commented May 2, 2021

@ashutoshdesign you can try doing the command in single-user mode by holding ⌘+S on boot-up just after pressing the power button of your mac.

Any tips for getting single-user mode to work? I get the wall-of-command-line-text but then it just kicks into the usual 'select user' GUI login screen. I've also turned off Firmware password. One suggestion I haven't tried is turning off Filevault, which some sources say take up to a week (!) to decrypt the start-up drive.. MacBook Air Intel 2018 with macOS 11.3 here.

@AravindaSetty

This comment has been minimized.

Copy link

@AravindaSetty AravindaSetty commented May 6, 2021

Thank you this was very useful, I had an 8TB drive crashed got all the data recovered....

@xiaodiwong

This comment has been minimized.

Copy link

@xiaodiwong xiaodiwong commented May 21, 2021

I'm getting an error saying- "Can't open /dev/rdisk2s2: Resource Busy". What do I do?

I was stuck with "Resource Busy" too, but a comment on the Source link (on craigsmith.id.au) describes how to find and kill the process locking the resource which worked for me.

ps -ax | grep disk2 (but your disk)
13699 ?? 11:52.83 /System/Library/Filesystems/hfs.fs/Contents/Resources/./fsck_hfs -y /dev/disk2s2

sudo kill 13699

Once the offending process is killed, I got an OS prompt about an error mounting the drive (something along the lines of it being mounted in read only mode, don't remember the wording). After that the drive mounted in Finder and Disk Utility and I was able to run "First Aid" using "Disk Utility"

i did exactly the same and i manage to reach to the step whereby i am able to run "First Aid" using "Disk Utility", however, i get stuck at first aid for very very long time and it doesn't move on from there, anybody can help me?

@T3kbug58

This comment has been minimized.

Copy link

@T3kbug58 T3kbug58 commented Jun 1, 2021

Hi I tried the above. After the drive debug on a 6TB WD Elements usb hard drive Took more than 12/hrs whew...the message said "everything seems to be ok" received No errors. Back to square one the drive shows but still won't repair in disk utility tried almost everything since mid March of this year. One thing I did notice maybe that's the problem I go to the drive icon right click go to "Get info" my Storage Info is wrong it says Modified:Monday, December 31,1969 at 11:00PM and under General: Created: Wednesday,December 31,1969 at 7:00PM Modified: Monday, December 31,1979 at 11:00PM. The format, capacity, available space left on partion info are correct. The drive content did show on windows but Not in Mac the format is Exfat there is a 'Back Up" partion also.When I run Diskutil: I get this message "Updating boot support partitions for the volume as required.Unable to unmount volume for repair.Operation failed..." The drive did open once the files were accessible. When I reboot my Mac I'm back to square one. Any ideas on how to fix this problem. I ran fsck in single mode diskutil in terminal all that.At least I got some good Mac lessons. Please Help Thanx

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment