Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Help with 69845 disk utility error?

B

bigsmile01

macrumors member
Original poster
Apr 17, 2013
56
4
Lately, my Mac has been acting slightly weird with finder tasks. For example, if try to unzip a 1MB file in the Finder it can take 3+ minutes! I use OneDrive to store my documents folder. And often the Finder will say it needs to download files that already exist locally. And then it will just get stuck.

Everything was fine when I was on 12.7.2. The issues only happened since I updated to 12.7.3.

I decided to run First Aid in Disk Utility.

This is how my Mac drive is set up:

Screen Shot 2024-02-27 at 19.22.08.jpg


When I run First Aid on “Macintosh HD - Data”, I get the following error message:


Code: 
Running First Aid on “Macintosh HD - Data” (disk1s5)


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/rdisk1s5
Checking the container superblock.
Checking the checkpoint with transaction ID 29922235.
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/rdisk1s5.
Checking the APFS volume superblock.
The volume Macintosh HD - Data was formatted by diskmanagementd (1934.141.2) and last modified by apfs_kext (1934.141.2.700.2).
Checking the object map.
Checking the snapshot metadata tree.
Checking the snapshot metadata.
Checking snapshot 1 of 2 (com.apple.TimeMachine.2024-02-27-110338.local)
error: doc-id tree: record exists for doc-id 247234, file-id 10818223 but no inode references this doc-id
warning: snapshot fsroot / file key rolling / doc-id tree corruptions are not repaired; they'll go away once the snapshot is deleted
Checking snapshot 2 of 2 (com.apple.TimeMachine.2024-02-27-173042.local)
error: doc-id tree: record exists for doc-id 247234, file-id 10818223 but no inode references this doc-id
Checking the document ID tree.
Checking the fsroot tree.
error: doc-id tree: record exists for doc-id 247234, file-id 10818223 but no inode references this doc-id
Checking the extent ref tree.
Verifying volume object map space.
The volume /dev/rdisk1s5 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
error: Try running fsck against the entire APFS container instead of a volume
The volume /dev/rdisk1s5 could not be verified completely.
File system check exit code is 8.
Restoring the original state found as mounted.
File system verify or repair failed. : (-69845)


Operation successful.

First Aid found corruption that needs to be repaired. To repair the startup volume, run First Aid from Recovery.

How can I fix this? I am surprised there is corruption, because I only did a clean reinstall a few months ago.

Steps I have tried:
  • Running Disk Utility from Recovery (e.g. by holding down CMD+R during start up). It produces the exact same error message.
  • Running first Aid on the other drives on my system (When I do this, First Aid completes successful. It's only on “Macintosh HD - Data” it produces the error).
Environment:
  • MacOS 12.7.3 (21H1015)
  • MacBookPro11,5 (15-inch, Mid 2015)
 
bogdanw said:
From recovery, unmount the volumes before running First Aid and, as suggested in the error message and Apple's documentation:
" Try running fsck against the entire APFS container instead of a volume"
“Repair volumes, then containers, then disks”
https://support.apple.com/HT210898
https://support.apple.com/en-us/HT210898
Click to expand...
Thanks for your help! I tried unmounting the disk, but using first aid still produces the same error as in the opening post.

I am struggling with running fsck. I followed this guide on Apple Insider. I opened terminal and entered diskutil list.

This is what it displayed:
Code: 
/dev/disk0 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *1.0 TB     disk0
   1:                        EFI ⁨EFI⁩                     209.7 MB   disk0s1
   2:                 Apple_APFS ⁨Container disk1⁩         930.0 GB   disk0s2
   3:       Microsoft Basic Data ⁨BOOTCAMP⁩                70.3 GB    disk0s3


/dev/disk1 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +930.0 GB   disk1
                                 Physical Store disk0s2
   1:                APFS Volume ⁨Macintosh HD⁩            15.4 GB    disk1s1
   2:              APFS Snapshot ⁨com.apple.os.update-...⁩ 15.4 GB    disk1s1s1
   3:                APFS Volume ⁨Preboot⁩                 411.6 MB   disk1s2
   4:                APFS Volume ⁨Recovery⁩                1.1 GB     disk1s3
   5:                APFS Volume ⁨VM⁩                      1.1 MB     disk1s4
   6:                APFS Volume ⁨Macintosh HD - Data⁩     422.3 GB   disk1s5

I then entered "/sbin/fsck -fy". But it just says
"warning: option -f is not implemented, ignoring
error: container /dev/rdisk1 is mounted"

It says this, even though I clicked on unmount on disk utility.

Any ideas how to run the fsck command? Thanks!
 
bogdanw said:
From Terminal, try:
Code: 
diskutil umount /dev/disk1s5
then
Code: 
fsck_apfs /dev/disk1s5
Click to expand...
Thank you so much for your continued help.

I tried running the commands both from booting into Recovery and from inside MacOS.


From Recovery:
When I try the unmount command, it says the following:
Code: 
Unmount failed for /dev/disk1s5

When I try the fsck command, it says
Code: 
fsck_adps: command not found.

From MacOS:
When I try the unmount command, it says the following:

Code: 
Volume Macintosh HD - Data on disk1s5 failed to unmount: dissented by PID 1 (/sbin/launchd)
Dissenter parent PPID 0 (kernel_task)

When I try the fsck command, it says:
Code: 
error: container /dev/rdisk1 is mounted with write access.
 
From your first post, I see that it performs on rdisk1s5, not disk1s5.
Try from Recovery
Code: 
diskutil umount /dev/rdisk1s5
and
Code: 
fsck_apfs /dev/rdisk1s5
Don't misspell it as fsck_adps, it's FSCK_APFS :)
 
  • Like
Reactions: bigsmile01
bogdanw said:
From your first post, I see that it performs on rdisk1s5, not disk1s5.
Try from Recovery
Code: 
diskutil umount /dev/rdisk1s5
and
Code: 
fsck_apfs /dev/rdisk1s5
Don't misspell it as fsck_adps, it's FSCK_APFS :)
Click to expand...
Thanks again for the continued help:

When I try diskutil umount /dev/rdisk1s5 in recovery, it says:
Unmount failed for /dev/rdisk1s5

When I try fsck_apfs /dev/rdisk1s5, it says:
error: unable to access /dev/rdisk1s5: No such file
 
bogdanw said:
Run diskutil list before to ensure that the disk number is correct.
If you have a bootable installer, boot from it and try with Disk Utility or from Terminal.

Create a bootable installer for macOS
https://support.apple.com/101578
Click to expand...
Thank you so, so, so much! I made a bootable installer and was able to unmount the disk and run FSCK check. It found some orphans which it told me to delete. I was then able to successfully run first aid on all volumes and all the weirdness has gone.

Thank you so much for taking the time to help me, and also for being so patient. 👍
 
  • Like
Reactions: bogdanw
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back