Skip to content
Logic ProFilesLogic ProFiles

Fix Problems

"Disk is too slow or System Overload (-10010)" in Logic Pro

The -10010 alert names two possible causes, and Logic Pro can't always tell them apart. Usually the drive can't read or write audio fast enough — a busy startup disk, a slow external drive or sample streaming. Confirm it with the Drive I/O meter, then move the heavy files somewhere faster.

Owen Hartley Owen Hartley Updated Checked for Logic Pro 13
External drive with a slow progress indicator connected to a Mac running a music project
Disk is too slow or System Overload. (-10010)

Applies to: Logic Pro 13 back to Logic Pro X (wording as users report it).

Most likely causes

  1. Project or samples on a slow or busy drive (most common)
  2. Sampler Virtual Memory streaming too much from disk (common)
  3. High sample rate for a large track count (common)
  4. Drive formatted with an unsupported file system (occasional)
  5. Processor overload reported under the same alert (occasional)

A drive layout that avoids -10010

Recommended Logic Pro drive setup with the startup disk, a project SSD and a separate sample drive
Apple's setup — projects on one external SSD, samples on another, the startup disk left for macOS.

Apple's system overload article describes the same layout in three steps: keep large projects off the startup disk, put Sampler samples on their own drive, and use APFS or Mac OS Extended (Journaled). If you're short of internal space too, Logic Pro 12 and later can move the Sound Library to an external drive — see system requirements for the space it needs.

Still getting the alert?

If the Drive I/O meter stays low while the alert keeps appearing, the "System Overload" half of the message is the real cause. Work through the processor fixes in error -10011.

Fixes, in order

  1. 1. Confirm it's the disk

    Open the Performance Meter (see our system overload guide) and play. If the Drive I/O meter peaks when the alert appears, the drive is the bottleneck. If a Processing Threads bar peaks, follow the CPU fixes instead.

  2. 2. Move the project to a dedicated SSD

    Apple recommends saving high-track-count projects to a dedicated external drive, such as a USB-C SSD, rather than the startup disk.

  3. 3. Give samples their own drive

    Use a separate drive for Sampler samples — Apple says always do this when Sampler Virtual Memory is on.

  4. 4. Check the drive format

    Format project and sample drives as APFS or Mac OS Extended (Journaled). Apple's general troubleshooting article asks for APFS on external drives holding projects or the Sound Library.

  5. 5. Turn off Sampler Virtual Memory

    In Logic Pro > Settings > Audio > Sampler > Virtual Memory, turn Active off when overloads line up with Drive I/O peaks.

  6. 6. Adjust Host Disk Activity

    In the same tab, choose Less for projects with few audio tracks, or Average or Extensive for many.

  7. 7. Try a lower sample rate

    Higher rates mean more data to stream. Apple suggests a lower rate if disk activity causes the alerts.

  8. 8. Don't freeze instrument tracks here

    Frozen tracks play from disk. Apple advises against freezing software instrument tracks when overloads match Drive I/O peaks.

  9. 9. Leave free space on the startup disk

    An older Sound On Sound guide (2008) recommends keeping space free on the boot drive for temporary files and virtual memory.

Sources

Checked November 2026. Logic ProFiles is independent of Apple; menu names can differ slightly between Logic Pro versions.

Frequently asked questions

Does "Disk is too slow" mean my drive is failing?

+

Not necessarily. It means the drive couldn't keep up with Logic Pro at that moment. A busy startup disk or a slow external drive is the usual reason.

What drive should I use for Logic Pro projects?

+

Apple suggests a dedicated external drive such as a USB-C SSD, formatted as APFS or Mac OS Extended (Journaled), with samples on a separate drive.