macOS 'The disk can't be found' error fix

30-Second Fix: Check the connection

I've lost count of how many times I've seen people panic over this error, only to find a loose USB-C cable. The drive's fine — macOS just lost the handshake.

1. Unplug the drive — properly eject if you can, but if you can't, just yank it. Don't worry, modern macOS handles sudden disconnects fine.
2. Try a different cable. USB-C cables are notoriously flaky. Apple's own Thunderbolt cables are better, but even those wear out. If you're on a MacBook Pro 2021 or later, use the right-side port — the left ones share bandwidth with the display.
3. Plug into a different port. Mac mini users, avoid the ports near the power cord — those share internal USB 2.0 bandwidth. Go for the ones closer to the front.
4. If it's a network volume (AFP, SMB, NFS), check your router. Reboot it. I've seen Sonoma 14.3 drop SMB connections on a 10-minute timeout — restart the router, then reconnect in Finder > Go > Connect to Server.

Still no luck? Move on. This fix works maybe 40% of the time, and you've already spent the easy 30 seconds.

5-Minute Fix: Disk Utility + First Aid

Disk Utility is your next stop. Don't bother with third-party tools — Apple's built-in fsck is solid for basic drive repair.

1. Open Disk Utility (Cmd+Space, type 'Disk Utility').
2. Look at the left sidebar. Click View > Show All Devices — this is critical. By default, Disk Utility hides the physical disk and only shows volumes. You need the top-level device entry.
3. If you see your drive listed but grayed out, select it and click Mount. If it's not there, select View > Show External Disks Only to filter out your internal drive.
4. If the drive appears but won't mount, run First Aid on the volume first (not the whole disk — that takes longer and risks losing data).
5. Wait. First Aid can take 5-10 minutes on a 2TB drive. Don't interrupt it — that's how you turn a fixable disk into a brick.

If First Aid reports errors, run it again. Yes, again. MacOS's fsck sometimes needs two passes — the first fixes directory structure, the second verifies the fix. If it passes clean, try mounting again.

Still no luck? The drive probably has a deeper filesystem corruption or a dead controller. Time for Terminal.

15-Minute Fix: Terminal Commands That Actually Work

You'll need your drive's BSD identifier. Here's how to find it:

diskutil list

Look for the external drive. It'll be something like /dev/disk2 or /dev/disk4. Note the size — your 1TB Samsung T7 should show roughly 1TB. If the size shows as 0 bytes or 'error', the drive's controller is dead. RMA it.

If size looks normal but it won't mount, force it:

sudo diskutil mountDisk /dev/disk2

Replace disk2 with your actual identifier. If it mounts, great — copy your data elsewhere immediately. That drive is on borrowed time.

If it still won't mount, check if the filesystem is damaged:

sudo fsck_exfat -y /dev/disk2s1

Replace exfat with your filesystem type: fsck_hfs for Mac OS Extended, fsck_apfs for APFS, fsck_msdos for FAT32. The -y flag auto-answers 'yes' to repair prompts. Run it without -y first if you want to see what it finds, but honestly, just let it fix.

APFS note: APFS volumes can have a 'container' that isn't mounted. You might see the container (/dev/disk2) but not the volume (/dev/disk2s1). Try:

sudo diskutil apfs unlockVolume /dev/disk2s1

If that asks for a password and you don't have one, the container is encrypted. You need the recovery key or you're out of luck.

When Terminal Fails: Recovery Mode

If your Mac's internal drive is the one showing 'The disk can't be found', you're in a different boat. That usually means a failed SSD controller or corrupted firmware. Here's the last resort:

1. Shut down your Mac completely.
2. For Apple Silicon (M1/M2/M3): Press and hold the power button until 'Loading startup options' appears. For Intel: Cmd+R at startup.
3. Open Terminal from the Utilities menu.
4. Run diskutil list — if your internal drive doesn't show up at all, the hardware is dead. Apple Diagnostics (hold D at boot) will confirm.
5. If it does show up, run First Aid from Recovery's Disk Utility. Recovery mode has a separate copy of Disk Utility that bypasses some macOS-level locks.

One more thing: If you're on a 2017-2019 MacBook Pro with the butterfly keyboard, the flex cable for the SSD is a known failure point. That's not a software fix — you need a new cable or logic board.

Real-world trigger I see most often: Someone plugs a USB-C drive into a 2023 MacBook Pro running Sonoma 14.5, the drive worked fine on Monterey. The culprit is almost always the USB-C cable or a mismatched filesystem (exFAT formatted on Windows, then plugged into a Mac with outdated exFAT drivers). Update to Sonoma 14.7 or later — they fixed the exFAT issues.

If none of this works, your drive is physically failing. Stop wasting time. Clone what you can with ddrescue (install via Homebrew) and buy a new drive. I've seen this error on Seagate, WD, and SanDisk drives — it's rarely the drive's fault until it is.