Thrum

What is diskarbitrationd, and why is it using CPU on my Mac?

Last reviewed: 19 November 2026. Path, account, launchd job and man page checked on macOS 26.3.1.

diskarbitrationd is the macOS daemon that notices when disks and volumes appear or disappear, mounts them, and tells apps about the change. It uses CPU when drives, card readers or disk images connect, disconnect or are checked, and is idle the rest of the time. It is part of macOS and must keep running.

diskarbitrationd at a glance

diskarbitrationd
Made byApple (part of macOS, Disk Arbitration)
TypeSystem daemon
Location/usr/libexec/diskarbitrationd
Runs asroot
Started bylaunchd job com.apple.diskarbitrationd
Can you quit it?No. launchd keeps it alive; without it disks would not mount.

What is diskarbitrationd?

Its man page says it notifies clients when disks and file systems appear, governs the mounting of file systems, and arbitrates which client may claim a disk. Apps talk to it through Apple's Disk Arbitration framework, which Apple describes as mechanisms to register for and block disk mount or unmount events.

Finder, Disk Utility, Time Machine and many other services rely on it to learn about drives. It consults /etc/fstab if you have defined custom mount points for particular volumes.

Is diskarbitrationd safe?

Yes. It is installed at /usr/libexec/diskarbitrationd on the read-only system volume, runs as root, and is signed by Apple (com.apple.diskarbitrationd).

Why does diskarbitrationd use so much CPU?

How much CPU is normal for diskarbitrationd?

Idle near 0% CPU when no drives are changing. A short spike when you connect or eject something is normal.

Continuous CPU use with nothing being connected is not typical and usually points to a device that keeps reappearing.

How do you stop diskarbitrationd from using so much CPU?

  1. Watch disk events live. Run diskutil activity in Terminal. It shows disk activity as reported by Disk Arbitration until you press Control-C. Repeated appear and disappear lines for one disk identify the problem device.
  2. List connected disks. Run diskutil list to see every disk and volume. Compare with what you expect to be connected.
  3. Unplug and replace suspect hardware. Disconnect drives, card readers and hubs one at a time. If the activity stops, try a different cable or port for that device.
  4. Eject disk images you are not using. Eject mounted images in Finder so they stop generating events.

When should you worry about diskarbitrationd?

Constant activity with drives repeatedly disappearing can mean a failing drive or cable, and data on that drive may be at risk. Copy important data off it before further testing.

A diskarbitrationd running from anywhere other than /usr/libexec would not be Apple's.

How do you check diskarbitrationd in Activity Monitor and Terminal?

Open Activity Monitor (Applications > Utilities), choose View > All Processes, and type diskarbitrationd in the search field. The CPU tab shows its % CPU. Double-click the row for its parent process, memory details and open files.

In Terminal, the first command lists every diskarbitrationd process with its PID, user, CPU and memory (RSS is resident memory in kilobytes).

ps -axo pid,user,%cpu,%mem,rss,command | grep -F 'diskarbitrationd' | grep -v grep

How can Thrum help with diskarbitrationd?

Thrum keeps a live CPU graph in the menu bar. One click shows the eight processes using the most CPU, so you can see when diskarbitrationd is among them and how much it takes. An optional alert tells you when a process stays above a CPU level you choose (50 to 200% of one core) for 1 to 10 minutes. macOS does not let apps quit processes owned by root or other users, so Thrum shows them for information and leaves stopping them to the steps above.

Thrum is $4.99 once with a 14-day free trial and no account. It requires macOS 26 Tahoe on Apple silicon or Intel.

Questions about diskarbitrationd

Can I stop a drive from mounting automatically?

Disk Arbitration consults /etc/fstab, where a volume can be given its own mount options by UUID or label. Editing it needs care and administrator rights; ejecting the volume in Finder is simpler.

Where does diskarbitrationd log?

Its man page says that started with the -d option it writes detailed information to /var/log/diskarbitrationd.log. On a normal system, messages go to the unified log, which you can view in the Console app.

Sources