This disk has a GUID partition table

macOS 'This disk has a GUID partition table' error fix

EP
Erropedia Team
📅 May 27, 2026 📅 Updated Sep 13, 2026 👁 110 views macOS Errors Intermediate
macOS throws this when you try to install on a drive with MBR or hybrid MBR. The fix is rewriting the partition table to pure GPT.

Quick answer

Run sudo gpt destroy /dev/diskX then sudo gpt create -f /dev/diskX and sudo diskutil partitionDisk /dev/diskX GPT JHFS+ "Macintosh HD" 100% — replacing X with your target disk number. This wipes the drive and gives it a fresh pure GPT table.

Context — what's happening here

The macOS installer checks the partition table type before it lets you proceed. It only accepts a pure GUID Partition Table (GPT) — Apple's required format since Intel Macs. The error appears when the disk has an old MBR (Master Boot Record) or a hybrid MBR (mixing MBR and GPT). This typically happens with:

  • USB drives that were previously formatted for Windows or Linux
  • External drives shared between macOS and other OSes
  • Internal drives that had Boot Camp or Linux installed
  • Drives that were dd'ed or cloned from a non-Mac source

The error is macOS's way of saying "I don't trust this partition layout — it's not to spec." And honestly, it's right. A hybrid MBR can confuse the installer and lead to boot failures later. The fix is to nuke the old scheme and start fresh.

Fix steps — the only reliable way

Disk Utility's erase button won't always fix this. If the drive has a hybrid MBR, Disk Utility's erase often just rewrites the GPT part and leaves the MBR layer intact — then you're back to the same error. Terminal is the straight path.

  1. Identify the disk
    Run diskutil list in Terminal. Find your target disk (e.g., /dev/disk2). The identifier is important — double-check you're on the right one or you'll wipe the wrong drive.
  2. Unmount everything on it
    sudo diskutil unmountDisk /dev/diskX
    The gpt command requires the disk to be unmounted before it can touch the partition table.
  3. Destroy the old partition table
    sudo gpt destroy /dev/diskX
    This removes both MBR and GPT structures. The disk becomes raw — no partitions, no scheme. It's scary but necessary.
  4. Create a fresh pure GPT
    sudo gpt create -f /dev/diskX
    The -f flag forces it even if the disk was already GPT. This writes a clean GPT header and table to the first and last sectors. No MBR remnants.
  5. Partition the disk
    sudo diskutil partitionDisk /dev/diskX GPT JHFS+ "Macintosh HD" 100%
    This creates a single JHFS+ (HFS+) partition covering the whole drive. If you want APFS (recommended for macOS High Sierra and later), use APFS instead of JHFS+. For example: sudo diskutil partitionDisk /dev/diskX GPT APFS "Macintosh HD" 100%.
  6. Verify the result
    diskutil list again. You should see GUID_partition_scheme as the partition scheme line. That's your green light.

Now quit Disk Utility and proceed with the installer. It'll accept the drive without complaint.

Alternative fix — if the main one fails

Sometimes gpt destroy returns an error like "resource busy" even after unmounting. This happens when the disk has a kernel-level attachment, like a USB enclosure that macOS insists on managing. Try these in order:

  • Eject and reconnect the drive physically, then try the destroy step again.
  • Use a different USB port — some Mac models (especially 2016–2019 with USB-C) have quirky controller handling that keeps a drive busy across reboots.
  • Boot into Recovery Mode (Cmd+R at startup) and run the same terminal commands there. Recovery Mode loads fewer drivers, so the drive won't be locked.
  • Last resort: Use sudo dd if=/dev/zero of=/dev/diskX bs=512 count=1 to zero out the first sector. This destroys the MBR if GPT commands won't cooperate. Then run gpt create -f /dev/diskX.

Prevention — don't let it happen again

If you're preparing a USB installer for macOS, always format the drive using diskutil partitionDisk with GPT scheme — don't use the "Master Boot Record" option in Disk Utility's partition tab. That MBR option is there for compatibility with older Windows installers, but it'll give you this exact error when you try to install macOS on it.

Also, if you clone a macOS installer to a USB using dd or cp, the source drive's partition table comes with it. If that source was hybrid MBR, you're inheriting the problem. Better to create the installer using Apple's official createinstallmedia command — it writes a clean GPT.

Related Errors in macOS Errors
The operation can’t be completed (error -36) macOS 'The operation can't be completed' error fixed -36 macOS Error -36: Fix Input/Output Errors Fast The disk can't be read or written macOS 'The disk can't be read or written' fix – works every time Fix com.apple.launchd.peruser Error Crash Loop on macOS
macOS disk has a GUID partition table error GUID partition table error macOS fix GUID partition table error macOS installer GUID partition table disk utility GUID partition table rewrite partition table GPT macOS convert MBR to GPT macOS macOS installation stuck GUID partition table terminal fix GUID partition table macOS diskutil GUID partition table gpt command macOS hybrid MBR macOS error macOS Catalina GUID partition table Big Sur GUID partition table Monterey GUID partition table Ventura GUID partition table Sonoma GUID partition table

Was this solution helpful?

EP
Erropedia Team
Tech Support Editors
The Erropedia editorial team researches and documents real-world tech errors from across Windows, Linux, macOS, networking, databases, cloud platforms, and more. Every solution is reviewed for accuracy and updated as software and systems evolve.