Storage System Verify or Repair Failed
See original GitHub issueGetting this return after setting the parameters for the partition resize:
Running MacBook Air M1 2020
error: doc-id tree: record exists for doc-id 64, file-id 9665861 but no inode references this doc-id
Checking the extent ref tree
Checking the file key rolling tree
Verifying volume object map space
The volume /dev/rdisk3s5 was found to be corrupt and needs to be repaired
Checking volume /dev/rdisk3s6
Checking the APFS volume superblock
Checking the object map
Checking the snapshot metadata tree
Checking the snapshot metadata
Checking the fsroot tree
Checking the extent ref tree
Verifying volume object map space
The volume /dev/rdisk3s6 appears to be OK
Verifying allocated space
Performing deferred repairs
error: doc-id tree record exists f
The container /dev/disk0s2 could not be verified completely
Storage system check exit code is 8
Error: -69716: Storage system verify or repair failed
Failed to run process: {cmd}
root : ERROR Process execution failed
Traceback (most recent call last):
File "/private/tmp/asahi-install/main.py", line 802, in <module>
InstallerMain().main()
File "/private/tmp/asahi-install/main.py", line 654, in main
while self.main_loop():
File "/private/tmp/asahi-install/main.py", line 774, in main_loop
return self.action_resize(parts_resizable)
File "/private/tmp/asahi-install/main.py", line 594, in action_resize
self.dutil.resizeContainer(target.name, val)
File "/private/tmp/asahi-install/diskutil.py", line 191, in resizeContainer
self.action("apfs", "resizeContainer", name, size, verbose=2)
File "/private/tmp/asahi-install/diskutil.py", line 37, in action
subprocess.run(["diskutil"] + list(args), check=True)
File "/private/tmp/asahi-install/Frameworks/Python.framework/Versions/3.9/lib/python3.9/subprocess.py", line 528, in run
raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command '['diskutil', 'apfs', 'resizeContainer', 'disk0s2', '116980187136']' returned non-zero exit status 1.
Dont really contribute much, so if there are details you guys must know please let me know so I can fill out more accurate bug reports.
Issue Analytics
- State:
- Created 2 years ago
- Comments:8 (1 by maintainers)
Top Results From Across the Web
Storage System Verify or Repair Failed, How to Fix - macReports
Fix the storage system verify or repair failed error ... This issue most often occurs when trying to update your Mac when there...
Read more >Storage system verify or repair failed 69716 - Apple Discussions
Storage system verify or repair failed 69716. I need to update my OS from Mojave to Catalina, although the update is recommending to...
Read more >Fix 'Storage/File System Verify or Repair Failed' 69716/69845
If the Mac error "Storage system verify or repair failed 69716" occurs when installing macOS on a fusion drive, you likely need to...
Read more >[FIXED] “File System Verify or Repair Failed” on Mac
How to Fix "File System Verify or Repair Failed" on Your Mac · 1. In the Disk Utility, choose View on the menu...
Read more >What to do with: Storage system check exit code is ... - MPU Talk
What to do with: Storage system check exit code is 65. Storage system verify or repair failed. : (-69716) · Boot into recovery...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I had a similar issue, where
/dev/disk3s5
had warnings that wouldn’t go away, and I solved it as follows:diskutil unmountdisk /dev/disk3
fsck_apfs /dev/disk3
(and hit y in response to the various prompts)I believe unmounting was the important part.
Rebooting into recovery (hold down power button until the spinner appears), launching disk utility and using the “first aid” button has fixed this error for me.