I would like to check a file system on an SD card for corruption. It's formatted as ext4 and I would like to run basically fsck.ext4 like on Linux. It seems that only the modules for exfat, msdos, hfs and cs are installed. How can I run it on an ext4 partition? MacOS Sonoma, Intel

I have 2 identical external 2T disks, mirrored using diskutility. Yesterday I realised that this volume was not mounted. I started diskutility to see what was going on and it came up as a blank screen. Tried multiple times until it eventually showed a disk info loading spinner. Eventually it showed my disks, and the raid volume, but no other useful info. Verify threw an error that I can't remember. I then started using the terminal. diskutil appleRaid list showed that one of the disks was rebuilding.... 20 hours later it is rebuilt but still won't mount. diskutil list gives the following (*trimmed to show just the disks with the issue*) /dev/disk3 (external, physical): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *2.0 TB disk3 1: EFI ⁨EFI⁩ 209.7 MB disk3s1 2: Apple_RAID ⁨⁩ 2.0 TB disk3s2 3: Apple_Boot ⁨Boot OS X⁩ 134.2 MB disk3s3 /dev/disk4 (external, physical): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *2.0 TB disk4 1: EFI ⁨EFI⁩ 209.7 MB disk4s1 2: Apple_RAID ⁨⁩ 2.0 TB disk4s2 3: Apple_Boot ⁨Boot OS X⁩ 134.2 MB disk4s3 /dev/disk6 (external, virtual): #: TYPE NAME SIZE IDENTIFIER 0: Apple_APFS +2.0 TB disk6 /dev/disk7 (synthesized): #: TYPE NAME SIZE IDENTIFIER 0: APFS Container Scheme - +ERROR disk7 Physical Store disk6 1: APFS Volume ⁨MediaTwo⁩ ERROR disk7s1 diskutil volumeVerify disk6 shows errors as follows: Started file system verification on disk6 Verifying storage system Performing fsck_apfs -n -x /dev/disk4 Checking the container superblock Checking the space manager Checking the space manager free queue trees Checking the object map Checking volume /dev/rdisk6s1 Checking the APFS volume superblock Checking the object map Checking the snapshot metadata tree Checking the snapshot metadata Checking the fsroot tree error: directory record (id 19): invalid hash (0x0, expected 0x14489a) of name (shutdown_time) error: directory record (id 22922): invalid hash (0x0, expected 0x3c39c7) of name (NSIRD_mediaanalysisd_3J7qIv) ... Similar lines removed error: directory record (id 31262): invalid hash (0x0, expected 0x2ae08b) of name (DB84492D-45C4-421C-8ADE-87682424AB46) error: directory record (id 31262): invalid hash (0x0, expected 0x243010) of name (E637CFBE-FE99-4CEF-B8FF-5B122D5CCA8C) error: directory record (id 378685): invalid hash (0x0, expected 0xfa1fa) of name (426AF3BB-CA79-4E4D-B3D3-59B09DCD5AD2_1_102_o.jpeg) error: directory valence check: directory (oid 0x60492): nchildren (9321) does not match drec count (9320) error: directory record (id 592626): invalid hash (0x0, expected 0x238bff) of name (Asset-tmp.plist) error: directory record (id 592626): invalid hash (0x0, expected 0x253850) of name (HistoryToken-tmp.plist) error: directory valence check: directory (oid 0x90af2): nchildren (47) does not match drec count (45) error: dstream (id 1229027) does not have an associated dstream id object Checking the extent ref tree error: (oid 0x233709) apfs_extentref: btn: invalid o_oid (0x23371f) error: (oid 0x233709) apfs_extentref: btn: invalid o_type (0x40000002, expected 0x40000003) error: (oid 0x233709) apfs_extentref: btn: invalid o_subtype (0xb, expected 0xf) Extent ref tree is invalid The volume /dev/rdisk6s1 was found to be corrupt and needs to be repaired Verifying allocated space Performing deferred repairs error: Unable to perform deferred repairs without full space verification The container /dev/disk4 could not be verified completely I've run `fsck_apfs` on the volume (disk7) and container (disk6) to no avail. How can I recover this? In theory I have 2 disks with a copy of my data, but the RAID array seems to be corrupt in some way. If I unplug one of the disks then I get exactly the same error when running diskutil `verifyVolume or fsck_apfs`

I'm trying to install Windows along side my Mac OS (Catalina 10.15.15). I'm using bootcamp, but it always get stuck at partitioning, telling me it can't partition the disk and check it and fix it with First Aid. Running First Aid it was giving me some orphaned files in the dstream. I fixed it by running network recovery, unmounting the disk and analyzing them with fsck. However, now I still have errors. If I run first aid that's the output I get: https://pastebin.com/iz5nCXPN I know this question may look like a duplicate, but I tried everything I can find online: - First Aid in Recovery and Single User modes - Network Recovery, unmount volumes and use fsck_apfs -y - Partition the disk manually (Disk Utility) doesn't work either - Recovery mode and "Reinstall MacOS" didn't fix it either - Running Disk Utility multiple times, as you can see from the past points, it's an entire week I'm continuosly running Disk Utility in normal and recovery mode. - Running

listlocalsnapshots /

returns nothing as I don't have local snapshots. Time Machine is disabled since 4 days and every external drive is unplugged. I'm out of options, and I can't either find what these errors means, nor how to fix them. So maybe asking again in 2020 could help.

Running diskutil on my intel mac I am getting: Running First Aid on “Macintosh HD - Data” (disk1s1) Verifying the startup volume will cause this computer to stop responding. Verifying file system. Volume could not be unmounted. Using live mode. Performing fsck_apfs -n -l -x /dev/rdisk1s1 Checking the container superblock. Checking the checkpoint with transaction ID 20088642. Checking the EFI jumpstart record. Checking the space manager. Checking the space manager free queue trees. Checking the object map. Checking the encryption key structures. Checking volume /dev/rdisk1s1. Checking the APFS volume superblock. The volume Macintosh HD - Data was formatted by diskmanagementd (945.230.6) and last modified by apfs_kext (2142.40.3.0.5). Checking the object map. Checking the snapshot metadata tree. Checking the snapshot metadata. Checking the document ID tree. Checking the fsroot tree. warning: inode (id 161782158): has the compression bsdflag, but doesn't have the compression xattr warning: inode (id 161782158): dataless bsd_flag is set, but the compression xattr is missing warning: inode (id 172634449): has the compression bsdflag, but doesn't have the compression xattr warning: inode (id 172634449): dataless bsd_flag is set, but the compression xattr is missing warning: inode (id 172652700): has the compression bsdflag, but doesn't have the compression xattr warning: inode (id 172652700): dataless bsd_flag is set, but the compression xattr is missing Checking the extent ref tree. Verifying volume object map space. Verifying allocated space. The volume /dev/rdisk1s1 appears to be OK. File system check exit code is 0. Restoring the original state found as mounted. Operation successful. /dev/disk1s1 is my DATA volume mounted on /Volumes/Macintosh - HD I performed a stat on /Volumes/Macintosh - HD to get the volume id as such: stat /Volumes/Macintosh\ HD 16777220 210857069 lrwxr-xr-x 1 root wheel 0 1 "Aug 28 12:59:24 2022" "Aug 28 12:59:24 2022" "Aug 28 12:59:24 2022" "Aug 28 12:59:24 2022" 4096 0 0 /Volumes/Macintosh HD Then tried to use GetFileInfo to see the files generating the above errors: GetFileInfo /.vol/16777220/161782158 GetFileInfo: could not refer to file (-43) I also tried the find / -inum 161782158 But again nothing. Anyone got ideas on how I can locate the files reported by fsck_apfs above? Thanks

I have an external disk with apfs filesystem that contains my encrypted time machine backups. The filesystem get corrupted and I'm not able to mount it any more. Disk Doctor is not able to fix the issue. I also tried to run fsck_apfs in terminal, but I guess this is the same. I always get an error: The volume /dev/disk3s2 could not be verified completely. I suspect that this is not a hardware failure as I checked with WD Drive Utilities. Is there any other tool that can fix the filesystem?

As the title says, I cannot boot my iMac (late 2012) into anything. I’ve tried everything from booting into Safe Mode, Recovery Mode (and Internet Recovery Mode), doing a diagnostics test (which didn’t work), and resetting NVRAM and SMC; nothing is working. I’m just stuck in a boot loop, the progress bar gets to around 60% and it turns off and reboots. I also have an external hard drive which I boot into to play games but when I try to boot in using the Option key, I get back to the boot loop. I’ve tried booting into Single User Mode and trying to run fsck but I can't do it because I can't disable SIP. I’m really stuck on what do to. Is there any fix to this, or do I have to take a trip to the Apple Store?

Got a bit of vocabulary confusion. I want to re-format an external hard drive. But I'm not sure what the difference is between restore or erase. Does erase, removes all files. or not. I don't want to lose the files. But I'm in a position that can't allow me to back up the entire Volume, for lack of storage. SSDs are on the way, ETA 1 week. I found this answer online but can't be sure of its correctness. https://discussions.apple.com/thread/3111247?answerId=32268374022#32268374022 What I generally do to re-activate a hard drive that could be stuck on a task. Is the following on terminal:

aux | grep fsck

kill -9 [task number]

but this solution does not format. or enable journaling. And, it limits the result by removing the drive's capability to re-write. Forcing me to apply: **Disk Utility>First Aid** (so far, sometimes it takes long, others *very long*). I feel like I'm asking many questions here. **But I simply wish to know if erase or restore will enable journaling without losing all your data** (if **Disk Utility** can do this from their GUI would be a lifesaver). But I'm willing to learn other solutions in the terminal as to how I found out:

aux | grep fsck

Thanks in advance

External disk (2 TB Seagate) is captured by fsck when plugged into a USB 3.0 port on my Macbook Pro (macOS Mojave 10.14.5). This has been discussed by @ArielAllon, and indeed, when I kill the fsck process, the disk is immediately mounted and I can see and read it. When I eject the disk and plug it in again, I always have to kill fsck. I have left fsck running for 12 hours and it never completes. When I kill it, a pop-up warns that the disk could not be repaired. My problem now, as Ariel mentioned, is that the disk is read-only, owned by root (or wheel?). I would like to use the remaining 150 GB on the disk, (remove old backups, etc) and prevent fsck from capturing it when attached. Thanks for any help...

I'm using a Mac Book Pro mid 2012 running 10.15.7on Samsung EVO 1TB internally. It was not possible to boot the computer last Friday. I tried to boot in recovery mode, the SSD was not identified as a bootable device. I removed the SSD and tried to boot it using a UGreen IDE Docking Station without sucess. Now I have connected the UGreen Docking Station to another Mac computer, fsck_apfs -fy gives the result that there are many invalid checksums, therefore the space manager is invalid, the whole issue is here: fsck_apfs Disk utility gives the same output. I run others tools like Drat/APFS Inspect, the output is the following: Drat - APFS Inspect As you can see there are a lot of checksum validation errors. APFS Inspect says an Ephemeral object is malformed. Is there any way to fix this checksum error and get the SSD bootable again? Or is the only possible solution to format the entire SSD and reinstall the operating system? I don't have any idea about the origin of this error and I couldn't find any information about it. It would be nice to receive some help.

Why would I get the same FSCK error on 2 different external drives? About a year ago I archived some important data (photos, etc) onto a 3TB external drive and then copied it (terminal copy command, not an image) onto a 2nd drive. The 2nd drive was stored in a different location to the first. Both drives are formatted HFS+ I recently plugged in the drive to retrieve some files and whilst the drive appears to work fine (photos all load, videos load), OSX says the drive is dirty and I get the below error when running FSCK. The drive definetely was fine last time I used it, as I ran FSCK on it before storing it. ** Checking catalog file. ** Rebuilding catalog B-tree. hfs_UNswap_BTNode: invalid node height (1) hfs_swap_BTNode: offset #0 invalid (0xFC11) (blockSize 0x2000 numRecords 24) Invalid node structure (4, 12830) ** The volume 3TB could not be repaired. Now it gets weird as I just checked the 2nd drive and it has exactly the same error in FSCK despite being a different model (seagate vs WD) and it wasn't created by image, it was populated by an OS level file copy. I don't need help getting the data off it, but I love to know **why** or **what** is going on here? My extensive google search turns up either "physical issue", or "just run disk warrior". Whilst possible, I doubt its a drive hardware issue. Could it just be a bad file on the disk? Or a hardware issue with the USB interface (yes I have tried different cables)? Thanks

I have an OsX installation that doesn't get past the apple logo. The progress bar loads and then shuts down midway. I have rebooted as single user mode and noticed that /sbin/fsck -fy complained that the disk was full. So I deleted some fairly large files and reclaimed > 15% of disk space and ran: fsck_hfs -rft /dev/rdisk0s2 Now, I get the following error messages:

Executing fsck_hfs (version 305.10.1). 
Checking Journaled HFS Plus volume. 
The volume name is Macintosh
Checking extents overflow file. 
Checking catalog file 
Rebuilding catalog B-tree
Rechecking volume
Checking extents overflow file
Checking catalog file
Checking multi-linked files. 
Checking catalog hierarchy 
Invalid volume directory count (It should be 136231 instead of 136234) Checking extended attributes file. 
Checking volume bitmap. 
Checking volume information. 
Repairing volume
Rechecking volume
....
....
The volume Macintosh could not be repaired after 3 attempts.

I have tried rerunning fsck_hfs several times, but it does not change the message. The invalid directory count remains. I've tried booting the repair disk to run DiskUtility, but not surprisingly, this has the same error information as well, with the additional error message:

File system check exit code is 8
Updating boot support partitions for the volume as File system verify or repair failed.

How can I fix this? How do I get fsck to rebuild/reset the directory count? I cannot believe that the installation is toast simply due to an invalid directory count?

Earlier today my 2009 iMac emitted I/O errors trying to copy files. So I ran disk utility, verify disk to see if anything was amiss. It was. But as it's my startup disk I couldn't repair it, so I tried safe mode. Safe mode worked the very first time, but when I rebooted it shows the progress bar filling up, before halting. Every time I turn it on now, the same progress bar then crash happens. Booting in verbose mode reveals fsck is failing with signal 8. Using single-user mode, as that's as far as I'm aware the only way I can get any access to the system, I've been running fsck_hfs. However, it always fails. Below is the output from fsck_hfs -d /dev/disk0s2. ** /dev/rdisk0s2 Using cacheBlockSize=32K cacheTotalBlock=65536 cacheSize=2097152K. ** Root file system Executing fsck_hfs (version diskdev_cmds-491.6~3). ** Verifying volume when it is mounted with write access. ** Checking Journaled HFT Plus volume. ** Checking extents overflow file. ** Checking catalog file. Missing thread record (id = 9931104) Missing thread record (id = 16434146) Missing thread record (id = 19370458) disk0s2: I/O error hfs_swap_BTNode: offsets 10 and 11 out of order (0x0000, 0x0000) Invalid node structure (4, 115897) ** The volume Macintosh HD could not be verified completely. volume check failed with error 7 volume type is pure HFS+ primary MDB is at block 0 0x00 alternate MDB is at block 0 0x00 primary VHB is at block 2 0x02 alternate VHB is at block 1952491198 0x74622d5e sector size = 512 0x200 VolumeObject flags = 0x07 total sectors for volume = 1952591200 0x74622d60 total sectors for embedded volume = 0 0x00 I absolutely need to be able to boot to use it as an external monitor.

I am trying to fix errors on my MacIntosh HD Data volume. I have tried to fix using Disk Utility from normal mode and from recovery mode. Same problem. DI hangs at a certain point and that's it. I boot into single user mode. Using df -h I see that the MacIntosh HD Data volume is /dev/disk2s1. I try to type: fsck_apfs -y /dev/disk2s1 and I get this: > error: device is unreadable because you are in single user mode. I try the same command from normal boot and I get > error: container /dev/rdisk1 is mounted with write access. I have done this thousands of times before, from single user mode. This is some Catalina crap. How do I do that now on Catalina?

My computer was stuck in a boot loop so I connected the drive to another computer and ran fsck. i get the error "failed to read spaceman cib 0xfcfe" "Space manager is invalid" "The volume /dev/disk3s1 could not be verified completely". Is there any way to get the data off this drive? (APFS)

I ran Disk Utility’s First Aid on a portable hard disk I use for Time Machine, which took around 13 hours (with no repairs being needed). I was wondering whether there’s a way to speed that up. Disk Utility’s output shows that it ran fsck_hfs -fy -x /dev/rdisk3, and so it doesn’t use the -c option, which according to the command’s man page “can result in better performance”:

-c size Specify the size of the cache used by fsck_hfs internally.
	   Bigger size can result in better performance but can result
	   in deadlock when used with -l option.  Size can be speci-
	   fied as a decimal, octal, or hexadecimal number.  If the
	   number ends with a `k'', m'', or `g'', the number is
	   multiplied by 1024 (1K), 1048576 (1M), or 1073741824 (1G),
	   respectively.

I was wondering whether anyone has experience using the -c option. Does fsck_hfs not use a cache at all when the option is not used, or does it use a default size? How large would I need to set the cache size to see significant, or even just any, performance improvement? I assume this depends on the size of the disk; mine is 1TB with Disk Utility showing it contains around 15.500.000 files.

Upon running Disk Utility against `Macintosh HD - Data", I get the following towards the end of the check:

error: dstream (id 8753874978) does not have an associated dstream id object
Verifying allocated space.
Performing deferred repairs.
error: Unable to perform deferred repairs without full space verification
error: Try running fsck against the entire APFS container instead of a volume
The volume /dev/rdisk1s1 could not be verified completely.
File system check exit code is 0.
Restoring the original state found as mounted.

I've booted into Single User mode, but running fsck -fy tells me that it cannot be run because the /dev/rdisk1s1 drive is mounted in write mode. I've also tried Googling the term "error: Unable to perform deferred repairs without full space verification" and found 1 thread on Apple's forums, with 67 likes and 0 answers. So, how can I repair my HD? rMBP late 2013 model.

My Time machine backup drive has started giving me these errors on doing a fsck. How can I rebuild the indexes on this drive? I just upgraded to Mac OS Mojave 10.14.6. The drive has 2 partitioned as: 1.9TB for time machine (HFS+) 100GB for other files (HFS+) Logs: /dev/rdisk2s2: fsck_hfs started at Sat Feb 15 08:37:39 2020 /dev/rdisk2s2: /dev/rdisk2s2: ** /dev/rdisk2s2 /dev/rdisk2s2: Executing fsck_hfs (version hfs-407.200.4). /dev/rdisk2s2: ** Checking Journaled HFS Plus volume. /dev/rdisk2s2: The volume name is 2TB /dev/rdisk2s2: ** Checking extents overflow file. /dev/rdisk2s2: ** Checking catalog file. /dev/rdisk2s2: ** Checking multi-linked files. /dev/rdisk2s2: ** Checking catalog hierarchy. /dev/rdisk2s2: ** Checking extended attributes file. /dev/rdisk2s2: ** Checking multi-linked directories. /dev/rdisk2s2: Invalid parent for directory inode (id = 11770766) /dev/rdisk2s2: (It should be 19 instead of 18) /dev/rdisk2s2: Invalid name for directory inode (id = 11770766) /dev/rdisk2s2: (It should be dir_11770766 instead of temp11770766) /dev/rdisk2s2: Incorrect number of directory hard links /dev/rdisk2s2: ** The volume 2TB could not be verified completely. /dev/rdisk2s2: fsck_hfs completed at Sat Feb 15 09:02:06 2020 On a ubuntu VM, I am seeing: $ sudo fsck.hfsplus -dfy /dev/sda2 ** /dev/sda2 Using cacheBlockSize=32K cacheTotalBlock=1024 cacheSize=32768K. ** Checking HFS Plus volume. ** Checking Extents Overflow file. ** Checking Catalog file. ** Checking multi-linked files. ** Checking Catalog hierarchy. ** Volume check failed. volume check failed with error 5 volume type is pure HFS+ primary MDB is at block 0 0x00 alternate MDB is at block 0 0x00 primary VHB is at block 2 0x02 alternate VHB is at block 3711042830 0xdd32050e sector size = 512 0x200 VolumeObject flags = 0x07 total sectors for volume = 3711042832 0xdd320510 total sectors for embedded volume = 0 0x00 I tried to rebuild the catalog using the -r option (on ubuntu) but that failed: $ sudo fsck.hfsplus -dfyr /dev/sda2 ** /dev/sda2 Using cacheBlockSize=32K cacheTotalBlock=1024 cacheSize=32768K. could not get volume block 2, err 5 could not get alternate volume header at 3711042830, err 5 unknown volume type primary MDB is at block 0 0x00 alternate MDB is at block 0 0x00 primary VHB is at block 0 0x00 alternate VHB is at block 0 0x00 sector size = 512 0x200 VolumeObject flags = 0x01 total sectors for volume = 3711042832 0xdd320510 total sectors for embedded volume = 0 0x00

The HDD is a brand new MyPassport WD 4Tb. I recently used it as my main backup and before I had the time to reformat another drive for a second backup (which means that some data on that drive are crucial to recover), this new HD stopped mounting on my MacBook Pro Mojave where it was always attached to (I don't know what happened). I tried DiskUtility which failed. I tried fsck_hfs in Recovery or Single User Mode on 2 different Apple computer as well as on Linux Mint... all failed. The returned error is Invalid Key Length and Catalog File not found for extent. I tried Stellar Data Recovery which ran for a full day and now it is stuck at the beginning of the yellow phase 3 of 4. It has not crashed, no error message is displayed. I tried their new Sellar Volume Repair which failed. I tried iBoySoft Data Recovery which crashes everytime I do a deep scan. I do not understand why such disk failure is so difficult to repair! What can I do? Advice will be deeply appreciated.

I am trying to mount an external HD with exFAT, but apparently the latest unmount was non-successful, and now the disk requires an automatic fsck. When macos tries to perform the fsck, this happens

Process:               fsck_exfat 
Path:                  /System/Library/Filesystems/exfat.fs/Contents/Resources/fsck_exfat
Identifier:            fsck_exfat
Version:               90.200.1
Code Type:             X86-64 (Native)
Parent Process:        diskarbitrationd 
Responsible:           fsck_exfat 
User ID:               0

Date/Time:             2019-04-05 00:13:11.857 +0100
OS Version:            Mac OS X 10.14.3 (18D109)
Report Version:        12
Bridge OS Version:     3.3 (16P3133)
Anonymous UUID:        972E6B24-EE1F-B5A0-2545-E9EE3AE52D78


Time Awake Since Boot: 980000 seconds

System Integrity Protection: enabled

Crashed Thread:        0  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_CRASH (SIGABRT)
Exception Codes:       0x0000000000000000, 0x0000000000000000
Exception Note:        EXC_CORPSE_NOTIFY

Application Specific Information:
dyld3 mode
Assertion failed: (result->data == NULL), function fsck_exfat_cache_recycle, file /BuildRoot/Library/Caches/com.apple.xbs/Sources/exfat/exfat-90.200.1/fsck/fsck_exfat_cache.c, line 248.
 

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   libsystem_kernel.dylib        	0x00007fff6ff9d23e __pthread_kill + 10
1   libsystem_pthread.dylib       	0x00007fff70053c1c pthread_kill + 285
2   libsystem_c.dylib             	0x00007fff6ff061c9 abort + 127
3   libsystem_c.dylib             	0x00007fff6fece868 __assert_rtn + 320
4   fsck_exfat                    	0x00000001099961a1 0x10998e000 + 33185
5   fsck_exfat                    	0x000000010999634e 0x10998e000 + 33614
6   fsck_exfat                    	0x00000001099953ff 0x10998e000 + 29695
7   fsck_exfat                    	0x0000000109993068 0x10998e000 + 20584
8   fsck_exfat                    	0x0000000109993461 0x10998e000 + 21601
9   libdyld.dylib                 	0x00007fff6fe5ded9 start + 1

Thread 1:
0   libsystem_pthread.dylib       	0x00007fff700503f8 start_wqthread + 0
1   ???                           	0x0000000054485244 0 + 1414025796

Thread 0 crashed with X86 Thread State (64-bit):
  rax: 0x0000000000000000  rbx: 0x00000001146785c0  rcx: 0x00007ffee6271998  rdx: 0x0000000000000000
  rdi: 0x0000000000000507  rsi: 0x0000000000000006  rbp: 0x00007ffee62719d0  rsp: 0x00007ffee6271998
   r8: 0x00000000000000f8   r9: 0xcccccccccccccccd  r10: 0x0000000000000000  r11: 0x0000000000000206
  r12: 0x0000000000000507  r13: 0x0000000109ac9000  r14: 0x0000000000000006  r15: 0x000000000000002d
  rip: 0x00007fff6ff9d23e  rfl: 0x0000000000000206  cr2: 0x00007fffa2c37188
  
Logical CPU:     0
Error Code:      0x02000148
Trap Number:     133


Binary Images:
       0x10998e000 -        0x109999fff  fsck_exfat (90.200.1)  /System/Library/Filesystems/exfat.fs/Contents/Resources/fsck_exfat
       0x1145c2000 -        0x114640a87  dyld (655.1)  /usr/lib/dyld
    0x7fff42bd5000 -     0x7fff43022fef  com.apple.CoreFoundation (6.9 - 1562)  /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
    0x7fff6cf1f000 -     0x7fff6cf20ff7  libDiagnosticMessagesClient.dylib (107)  /usr/lib/libDiagnosticMessagesClient.dylib
    0x7fff6d2d1000 -     0x7fff6d2d2ffb  libSystem.B.dylib (1252.200.5)  /usr/lib/libSystem.B.dylib
    0x7fff6d52b000 -     0x7fff6d582ff7  libc++.1.dylib (400.9.4)  /usr/lib/libc++.1.dylib
    0x7fff6d583000 -     0x7fff6d598fff  libc++abi.dylib (400.17)  /usr/lib/libc++abi.dylib
    0x7fff6e1e7000 -     0x7fff6e44affb  libicucore.A.dylib (62109.0.1)  /usr/lib/libicucore.A.dylib
    0x7fff6ed79000 -     0x7fff6f4fffe7  libobjc.A.dylib (750.1)  /usr/lib/libobjc.A.dylib
    0x7fff6fc5c000 -     0x7fff6fc6effb  libz.1.dylib (70.200.4)  /usr/lib/libz.1.dylib
    0x7fff6fcdf000 -     0x7fff6fce3ff3  libcache.dylib (81)  /usr/lib/system/libcache.dylib
    0x7fff6fce4000 -     0x7fff6fceeff3  libcommonCrypto.dylib (60118.220.1)  /usr/lib/system/libcommonCrypto.dylib
    0x7fff6fcef000 -     0x7fff6fcf6fff  libcompiler_rt.dylib (63.4)  /usr/lib/system/libcompiler_rt.dylib
    0x7fff6fcf7000 -     0x7fff6fd00ff3  libcopyfile.dylib (146.200.3)  /usr/lib/system/libcopyfile.dylib
    0x7fff6fd01000 -     0x7fff6fd85fdf  libcorecrypto.dylib (602.230.1)  /usr/lib/system/libcorecrypto.dylib
    0x7fff6fe0c000 -     0x7fff6fe46ff7  libdispatch.dylib (1008.220.2)  /usr/lib/system/libdispatch.dylib
    0x7fff6fe47000 -     0x7fff6fe76ff3  libdyld.dylib (655.1)  /usr/lib/system/libdyld.dylib
    0x7fff6fe77000 -     0x7fff6fe77ffb  libkeymgr.dylib (30)  /usr/lib/system/libkeymgr.dylib
    0x7fff6fe85000 -     0x7fff6fe85ff7  liblaunch.dylib (1336.240.2)  /usr/lib/system/liblaunch.dylib
    0x7fff6fe86000 -     0x7fff6fe8bfff  libmacho.dylib (921)  /usr/lib/system/libmacho.dylib
    0x7fff6fe8c000 -     0x7fff6fe8effb  libquarantine.dylib (86.220.1)  /usr/lib/system/libquarantine.dylib
    0x7fff6fe8f000 -     0x7fff6fe90ff3  libremovefile.dylib (45.200.2)  /usr/lib/system/libremovefile.dylib
    0x7fff6fe91000 -     0x7fff6fea8ff3  libsystem_asl.dylib (356.200.4)  /usr/lib/system/libsystem_asl.dylib
    0x7fff6fea9000 -     0x7fff6fea9fff  libsystem_blocks.dylib (73)  /usr/lib/system/libsystem_blocks.dylib
    0x7fff6feaa000 -     0x7fff6ff32fff  libsystem_c.dylib (1272.200.26)  /usr/lib/system/libsystem_c.dylib
    0x7fff6ff33000 -     0x7fff6ff36ff7  libsystem_configuration.dylib (963.200.27)  /usr/lib/system/libsystem_configuration.dylib
    0x7fff6ff37000 -     0x7fff6ff3aff7  libsystem_coreservices.dylib (66)  /usr/lib/system/libsystem_coreservices.dylib
    0x7fff6ff3b000 -     0x7fff6ff41ffb  libsystem_darwin.dylib (1272.200.26)  /usr/lib/system/libsystem_darwin.dylib
    0x7fff6ff42000 -     0x7fff6ff48ff7  libsystem_dnssd.dylib (878.240.1)  /usr/lib/system/libsystem_dnssd.dylib
    0x7fff6ff49000 -     0x7fff6ff95ff3  libsystem_info.dylib (517.200.9)  /usr/lib/system/libsystem_info.dylib
    0x7fff6ff96000 -     0x7fff6ffbeff7  libsystem_kernel.dylib (4903.241.1)  /usr/lib/system/libsystem_kernel.dylib
    0x7fff6ffbf000 -     0x7fff7000aff7  libsystem_m.dylib (3158.200.7)  /usr/lib/system/libsystem_m.dylib
    0x7fff7000b000 -     0x7fff7002fff7  libsystem_malloc.dylib (166.220.1)  /usr/lib/system/libsystem_malloc.dylib
    0x7fff70030000 -     0x7fff7003bff3  libsystem_networkextension.dylib (767.240.1)  /usr/lib/system/libsystem_networkextension.dylib
    0x7fff7003c000 -     0x7fff70043fff  libsystem_notify.dylib (172.200.21)  /usr/lib/system/libsystem_notify.dylib
    0x7fff70044000 -     0x7fff7004dfef  libsystem_platform.dylib (177.200.16)  /usr/lib/system/libsystem_platform.dylib
    0x7fff7004e000 -     0x7fff70058fff  libsystem_pthread.dylib (330.230.1)  /usr/lib/system/libsystem_pthread.dylib
    0x7fff70059000 -     0x7fff7005cff7  libsystem_sandbox.dylib (851.230.3)  /usr/lib/system/libsystem_sandbox.dylib
    0x7fff7005d000 -     0x7fff7005fff3  libsystem_secinit.dylib (30.220.1)  /usr/lib/system/libsystem_secinit.dylib
    0x7fff70060000 -     0x7fff70067ff7  libsystem_symptoms.dylib (820.237.2)  /usr/lib/system/libsystem_symptoms.dylib
    0x7fff70068000 -     0x7fff7007dff7  libsystem_trace.dylib (906.220.1)  /usr/lib/system/libsystem_trace.dylib
    0x7fff7007f000 -     0x7fff70084ffb  libunwind.dylib (35.4)  /usr/lib/system/libunwind.dylib
    0x7fff70085000 -     0x7fff700b5fff  libxpc.dylib (1336.240.2)  /usr/lib/system/libxpc.dylib

External Modification Summary:
  Calls made by other processes targeting this process:
    task_for_pid: 0
    thread_create: 0
    thread_set_state: 0
  Calls made by this process:
    task_for_pid: 0
    thread_create: 0
    thread_set_state: 0
  Calls made by all processes on this machine:
    task_for_pid: 602965
    thread_create: 0
    thread_set_state: 0

VM Region Summary:
ReadOnly portion of Libraries: Total=234.6M resident=0K(0%) swapped_out_or_unallocated=234.6M(100%)
Writable regions: Total=356.0M written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=356.0M(100%)
 
                                VIRTUAL   REGION 
REGION TYPE                        SIZE    COUNT (non-coalesced) 
===========                     =======  ======= 
Dispatch continuations            24.0M        2 
Kernel Alloc Once                    8K        2 
MALLOC                           276.2M       23 
MALLOC guard page                   16K        5 
MALLOC_LARGE (reserved)           46.3M        2         reserved VM address space (unallocated)
STACK GUARD                       56.0M        3 
Stack                             8712K        3 
VM_ALLOCATE                          4K        2 
__DATA                            4664K       44 
__LINKEDIT                       216.1M        4 
__TEXT                            18.5M       44 
__UNICODE                          564K        2 
shared memory                        8K        3 
===========                     =======  ======= 
TOTAL                            650.8M      126 
TOTAL, minus reserved VM space   604.5M      126

It brings the whole system down with it. The mac reboots. Is this a known issue? I could not find anything googling. Do you have a workaround for it?

I have an orphan directory on my main disk. 1. I restart the computer in single user mode. 2. In single user mode, the main disk / is mounted as read-only. 3. I type /sbin/fsck -fy. 4. fsck points the problems but does not fix them. I suppose because the disk must be unmounted or because the disk is read-only. 4. I try to unmount the disk by using umount / or umount /dev/disk2s1, I get a Resource busy, try diskutil umount error. 5. I try diskutil umount. I get an error telling me that diskutil cannot run from single user mode. The main disk is APFS. WTH is that? How am I suppose to fix the problem?