'The Disk Can't Be Modified' on Mac? Here's What to Try

You drag a file onto an external drive and Finder refuses: “The disk can’t be modified.” Or you try to rename a folder and the same error appears. Or you attempt to delete a file from the Trash that came off this drive — same wall. The drive shows up, you can read from it, but writes are blocked.

This is a different error from “can’t write to disk.” This one is specific: the volume itself has been marked unmodifiable, either by the system or by its filesystem state.

What macOS is actually telling you

The exact text:

“The operation can’t be completed because the disk can’t be modified.”

It means one of these:

1. The volume is mounted read-only by macOS.
2. The volume is on a filesystem macOS can’t write to (NTFS).
3. The volume’s filesystem is in a recovery state after an unclean dismount.
4. The volume is a system-protected partition (System volume, Recovery, Preboot).
5. The drive’s hardware write-protect switch is engaged.

Each has its own fix.

Quick checks first

1. Check the Get Info readout

Click the volume in Finder → File → Get Info (Cmd+I). At the bottom under Sharing & Permissions:

• “You can read and write” → permissions are fine; the issue is filesystem-level.
• “You can only read” → either filesystem-level read-only or permission-level read-only.

If it says Format: Windows NT (Tuxera) or NTFS, you’ve found your problem — see the NTFS section.

2. Check the mount status in Terminal

mount | grep VolumeName

The output shows mount flags. read-only or ronly in the flag list means macOS mounted the disk read-only.

3. Check for a physical write-protect switch

Some external SSDs (especially older WD MyPassport units) have a tiny physical switch or pin that locks writes. Check the drive’s body. SD cards have a switch on the side — slide it the other way.

Skip the manual huntSweep clears the cruft that triggers most of these errors — caches, logs, leftover daemons. Download Sweep free →

Fix NTFS read-only mode

If the drive was formatted on a Windows machine (NTFS), macOS reads but won’t write to it natively. Options:

Option 1: Reformat to ExFAT (cross-platform)

1. Back up everything on the drive — reformatting wipes it.
2. Disk Utility → select the drive → Erase.
3. Format: ExFAT, Scheme: GUID Partition Map.
4. Erase.

ExFAT works on Windows and Mac with read/write, but doesn’t preserve macOS extended attributes well. Fine for general data, less ideal for backups.

Option 2: Reformat to APFS (Mac-only)

1. Back up first.
2. Disk Utility → Erase → Format: APFS, Scheme: GUID Partition Map.
3. Erase.

APFS is faster and more reliable on Mac, but won’t be readable from Windows without third-party software.

Option 3: Install NTFS write support

Paid options like Paragon NTFS for Mac and Tuxera NTFS, plus free options like Mounty (which uses macOS’s hidden NTFS write support, with caveats). Each adds a kernel extension or system extension that allows writes to NTFS volumes.

Repair an unclean filesystem

If the drive used to be writable and isn’t anymore, it may have been unmounted uncleanly (cable yanked, power lost mid-write).

1. Disk Utility → First Aid on the volume. Let it run to completion.
2. If First Aid passes, eject and reconnect — should mount writable.
3. If First Aid fails:

diskutil verifyVolume /Volumes/<name>
diskutil repairVolume /Volumes/<name>

Detailed output identifies what’s broken. For severe APFS damage, sometimes fsck_apfs -y /dev/disk2s1 (replacing with the correct device) digs deeper than Disk Utility’s GUI version.

If repairs fail entirely, the data is at risk. Copy off what you can while the volume is still mountable read-only, then reformat.

Fix permission-based read-only

If Get Info says “You can only read” but the format isn’t NTFS:

1. Get Info → click the lock at the bottom right → authenticate.
2. Set your user to Read & Write.
3. Check Ignore ownership on this volume if it’s an external drive.

For folders that need bulk permission changes, the gear menu’s Apply to enclosed items propagates permissions down through the tree.

In Terminal, force write permission across the volume:

sudo chmod -R u+rw /Volumes/<VolumeName>

Use cautiously on system volumes; safe on personal external drives.

Diagnose AND clean in one appSweep finds the buildup behind the error and clears it. Try Sweep free →

When the disk is system-protected

Some volumes are intentionally read-only:

• Macintosh HD (the system volume on macOS Catalina+) is read-only by design — it’s the sealed system volume. macOS itself lives there and you can’t modify it.
• Recovery, Preboot, VM are managed partitions. Don’t try to write to them.
• Read-only DMG mounts stay read-only until you copy contents elsewhere.

If you genuinely need to modify Macintosh HD (you almost never do), you’d have to disable SIP and the sealed system volume protection, which weakens macOS security significantly. The right answer is to put your files in /Users/<you> instead.

Force-remount writable

If macOS mounted the volume read-only but the filesystem is actually fine:

sudo mount -uw /Volumes/<VolumeName>

This re-mounts writable. Works for HFS+ and some APFS scenarios; doesn’t help with NTFS.

If the remount fails with an error, the underlying filesystem isn’t ready for writes — repair it first.

Specific scenarios

”Disk can’t be modified” but Trash isn’t full

Trash on external drives lives at /Volumes/<VolumeName>/.Trashes/501/. If the volume is read-only, even moving files to Trash fails. Fixing the read-only mount fixes the Trash.

Read-only after macOS upgrade

After a major macOS upgrade, some external drives mount read-only because the upgrade tightened filesystem checks. Run First Aid; usually clears it.

File copies to the volume work, but folder operations fail

Sometimes the volume root is writable but specific subfolders inherit broken permissions. Get Info on the failing subfolder, fix permissions, and apply to enclosed items.

Disk shows “Read Only” in Disk Utility’s info pane

Confirmation that macOS believes the volume is read-only. Repair, reformat, or check for the write-protect switch.

Recover data before reformatting

If you have to reformat to fix the issue, back up first. Even from a read-only mount you can copy files off:

1. Plug the drive in.
2. Open Finder → drag everything from the drive to a folder on your startup disk or another writable drive.
3. Verify the copied files open correctly.
4. Reformat.

For partial copies (some files fail mid-copy with -36 errors), the source has bad sectors. Use ditto -V /Volumes/Source ~/Recovered in Terminal — ditto is more resilient than Finder for marginal drives. Even that may skip files; what survives is what survives.

When the drive is failing

A drive that flips into read-only mode without explanation, then stays that way, is often failing. Check:

1. S.M.A.R.T. status. Disk Utility → View → Show All Devices → click the physical drive → look for S.M.A.R.T. Status. “Failing” means replace.
2. First Aid output. Repeated errors across multiple runs is a bad sign.
3. Audible clicking from a spinning drive. Mechanical failure.
4. Console.app entries. Search for the drive’s bus identifier; repeated I/O errors are diagnostic.

If two of those apply, your data is at risk every minute the drive is connected. Copy what’s salvageable, then retire the drive.

When the answer is the drive itself

Some drives have firmware quirks that cause read-only modes:

• Older USB-C SSDs that overheat throttle into read-only as a protective measure.
• Some manufacturers (SanDisk Extreme V2 SSDs notably) had firmware bugs that bricked drives or forced read-only states.
• Cheap unbranded drives sometimes ship with marginal firmware that degrades after months of use.

Check the manufacturer’s site for firmware updates. If the drive is on an active recall, get it replaced.

Prevent it from happening again

• Eject before unplugging.
• Use ExFAT or APFS, not NTFS, for drives you’ll write to from a Mac.
• Run First Aid on external drives monthly.
• Don’t fill drives past 95% — APFS gets cranky.
• Keep firmware updated.

The “can’t be modified” error is one macOS error where the answer is almost always one of three things: NTFS, permissions, or a damaged filesystem. Identify which and the fix follows.