Fsck Error in macOS: How to Fix File System Check

What the fsck Error Means

The fsck (File System Consistency Check) error appears during macOS boot when the system detects inconsistencies in the file system structure (typically APFS or HFS+). Typical output looks like this:

** /dev/disk1s1s1: **
FILE SYSTEM WAS MODIFIED
fsck_hfs (version 1.6.4 [1078]).
...

This means macOS automatically launched a disk check, found corruption (e.g., in the file catalog or allocation blocks), and attempted to repair it. Sometimes the check succeeds, but if errors are serious, the system may:

• Freeze during the check phase.
• Show the error repeatedly on every boot.
• Fail to boot entirely, freezing on the Apple logo.

Fsck runs automatically after:

• An improper shutdown (crash, power failure).
• A forced restart (holding the power button).
• I/O errors on the disk.
• File corruption due to software failures.

Common Causes

Fsck errors rarely occur due to a "bad disk" without underlying causes. Main reasons include:

1. Improper macOS shutdown — most common. Power loss, system hang followed by forced power-off.
2. Physical drive issues — emergence of bad blocks, SSD/HDD wear, controller problems. Checked via SMART status.
3. File system metadata corruption — e.g., due to a write failure during large file operations, working with network drives, or viruses (rare on macOS).
4. Software or driver conflicts — third-party disk utilities, antivirus software, outdated kernel extensions can damage volume structure.
5. Hardware malfunctions — bus issues (SATA/PCIe), cables (for external drives), memory (RAM errors can corrupt disk cache).

Method 1: Check via Disk Utility in Normal Mode

If Mac boots but shows an fsck error or the disk behaves oddly, try the graphical tool.

1. Open Disk Utility via Finder → Applications → Utilities.
2. Select the main disk (e.g., "Macintosh HD") in the left column.
3. Click First Aid.
4. Confirm to run the check. The utility will attempt to repair errors without rebooting.
5. If Disk Utility reports errors it cannot fix, or suggests creating a new volume — this indicates serious damage. Proceed to Method 2.

⚠️ Important: Disk Utility uses the same mechanism as fsck but in a GUI. If errors are deep, it may not succeed.

Method 2: Run fsck in Recovery Mode

This is the most effective method for serious errors blocking boot.

1. Restart Mac into Recovery Mode:
   • Intel: hold Command (⌘) + R at startup.
   • Apple Silicon: hold the power button until the startup options screen appears, select "Options" → "Continue in Recovery Mode".
2. Open Terminal (from the "Utilities" menu at the top).
3. Identify the disk identifier:

   diskutil list
   

   Find the main volume (e.g., APFS Volume disk1s1s1 or disk0s1s1). Note the identifier (the diskXsY part).
4. Run the check (replace disk1s1s1 with your identifier):

   sudo fsck_hfs -fy /dev/disk1s1s1
   

   For APFS disks (modern macOS) use:

   sudo fsck_apfs -y /dev/disk1s1s1
   

   Enter the administrator password when prompted.
5. Interpret results:
   • File system was modified — errors found and fixed. Repeat the command until you see The volume appears to be OK.
   • File system appears to be OK — check passed, no errors.
   • fsck_hfs: volume is mounted — disk is mounted. Unmount it: sudo diskutil unmount /dev/disk1s1s1 and retry.
   • Messages about "orphaned inodes", "invalid node" — serious corruption requiring restore from backup.

Method 3: Check Disk SMART Status

If fsck constantly finds errors, the drive may be physically failing.

1. In Terminal (in normal or recovery mode) run:

   diskutil info / | grep "SMART"
   

   Or for external drives:

   diskutil info /dev/disk2 | grep "SMART"
   

2. Look for SMART Status: Verified (healthy) or Failing (failed).
3. For detailed info use:

   sudo smartctl -a /dev/disk0
   

   (requires installing smartmontools via Homebrew or in recovery mode via brew).
4. If status is "Failing" — immediately back up data and replace the drive. Fsck cannot fix physical damage.

Method 4: Restore from Time Machine

If fsck doesn't help and data is critical, restore the system from a backup.

1. In Recovery Mode open Time Machine (from the "Utilities" menu).
2. Select a backup created before the errors appeared.
3. Follow instructions for a full system restore.
4. After restore, check if the fsck error is gone. If yes — the issue was corrupted system files.

Method 5: Reset NVRAM/PRAM and SMC (for Intel Mac)

Sometimes fsck errors are caused by hardware configuration glitches.

1. Reset NVRAM:
   • Shut down Mac.
   • Power on and immediately hold Option + Command + P + R for 20 seconds.
   • Release and wait for boot.
2. Reset SMC (Intel only):
   • For laptops: shut down, connect power, press Shift + Control + Option + Power for 10 seconds.
   • For desktops: unplug power cable for 15 seconds.
3. After reset, try booting and check if fsck error reappears.

Prevention

To minimize fsck error risk:

• Always shut down Mac via the Apple menu (or wait 10 seconds when frozen before holding the power button).
• Use a UPS (uninterruptible power supply) for desktop Macs — protects against power failures.
• Regularly back up via Time Machine. Restoring from backup solves 90% of fsck issues.
• Check disk monthly via Disk Utility (First Aid) in normal mode.
• Avoid interrupting disk operations (copying large files, defragmentation utilities).
• Update macOS — Apple regularly releases file system fixes.
• For external drives — use quality cables and never disconnect during active writes.