Mac Disk Utility First Aid Errors — Repair & Volume Recovery
About Mac Disk Utility First Aid Errors
Fix Disk Utility First Aid errors including 'First Aid found corruption that needs to be repaired', 'could not be repaired', and volume header issues. This guide covers everything you need to know about this topic, including common causes, step-by-step solutions, and answers to frequently asked questions.
Here are the key things to understand: First Aid checks and repairs file system errors on HFS+, APFS, and FAT volumes. Cannot repair the boot volume while macOS is running — use Recovery Mode. APFS container errors may require checking both the container and individual volumes. Common issue: 'Volume could not be repaired' means First Aid found errors it cannot fix. fsck (file system check) in single-user mode can fix errors Disk Utility cannot. Understanding these fundamentals will help you diagnose and resolve this issue more effectively.
The most common reasons this occurs include: Power loss or improper shutdown causing file system inconsistency. Bad sectors on HDD or failing flash cells on SSD. APFS snapshot corruption from interrupted Time Machine backups. Volume header or catalog file corruption. Physical disk damage that software cannot repair. Identifying the root cause is the first step toward finding the right solution.
To resolve this, follow these recommended steps: Boot to Recovery Mode (Cmd+R or hold power on M-series), open Disk Utility, run First Aid. If First Aid fails: boot to Recovery > Terminal > diskutil repairVolume /dev/diskXsY. For APFS: run First Aid on the container first, then individual volumes. Try fsck in single-user mode: restart holding Cmd+S, run /sbin/fsck -fy. If repair fails completely: back up what you can, erase the volume, and restore from backup. If these steps do not resolve the issue, consider consulting additional resources or a qualified professional.
This article is part of our Mac Error Codes collection on Error Codes Wiki. We provide comprehensive, up-to-date information to help you find solutions quickly.
Quick Answer
Why can I not run First Aid on my startup disk?
macOS locks the boot volume. Boot into Recovery Mode (Cmd+R) to run First Aid on the startup disk.
Overview
Fix Disk Utility First Aid errors including 'First Aid found corruption that needs to be repaired', 'could not be repaired', and volume header issues.
Key Details
- First Aid checks and repairs file system errors on HFS+, APFS, and FAT volumes
- Cannot repair the boot volume while macOS is running — use Recovery Mode
- APFS container errors may require checking both the container and individual volumes
- Common issue: 'Volume could not be repaired' means First Aid found errors it cannot fix
- fsck (file system check) in single-user mode can fix errors Disk Utility cannot
Common Causes
- Power loss or improper shutdown causing file system inconsistency
- Bad sectors on HDD or failing flash cells on SSD
- APFS snapshot corruption from interrupted Time Machine backups
- Volume header or catalog file corruption
- Physical disk damage that software cannot repair
Steps
- 1Boot to Recovery Mode (Cmd+R or hold power on M-series), open Disk Utility, run First Aid
- 2If First Aid fails: boot to Recovery > Terminal > diskutil repairVolume /dev/diskXsY
- 3For APFS: run First Aid on the container first, then individual volumes
- 4Try fsck in single-user mode: restart holding Cmd+S, run /sbin/fsck -fy
- 5If repair fails completely: back up what you can, erase the volume, and restore from backup