I got a “Machine Mount HD Failed” error on my Mac and I’m not sure what caused it or how serious it is. It showed up while I was trying to access or mount my hard drive, and now I can’t tell if the issue is with macOS, the drive itself, or my settings. I need help understanding what this error means and what steps I should take to fix it without losing data.
I quit assuming an external drive is dead the second macOS refuses to mount it. I’ve had too many cases where the drive looked bad at first, then turned out to be a messed up file system and nothing more. Disk Utility still saw it. The activity light kept blinking like normal. The enclosure and drive were fine. macOS was the part throwing a fit.
Before I touch anything risky, I rule out the boring stuff first.
Swap the cable. Plug the drive straight into the Mac. Skip the hub. Try a different USB or Thunderbolt port.
Check Finder settings and make sure external disks aren’t hidden. If the drive shows in Disk Utility and the size looks close to what it should be, I take it as a decent sign. Your Mac is still talking to the hardware.
Then comes the part people rush past. Decide whether the files matter.
If the data matters, don’t start with repair attempts. Pull the data first. I learned this the hard way a while back, and I don’t mess with the order anymore.
For unmounted drives, Disk Drill has usually been the easiest route for me. It reads the storage device directly, so it sometimes sees files even when macOS refuses to mount the volume.
If your files are important, this is the order I’d use:
1. Install and open Disk Drill.
2. Find the unmounted drive in the device list.
3. Make a Byte-to-byte Backup first if the drive seems unstable, slow, or random.
4. Scan the original disk or scan the backup image instead.
5. Look through what it finds.
6. Preview the files you care about and make sure they open.
7. Recover them to a different drive, not back onto the same one.
Once the files are safe somewhere else, you’ve got room to experiment without turning a small problem into a worse one.
If you don’t care about the old contents and you only want the drive usable again, formatting is often the quickest fix.
Reformat the Drive
Reformatting rebuilds the file system from scratch. It wipes the current contents, so this is not the move if you still need the data. Still, for mount issues, I’ve seen it clear things up fast.
1. Open Disk Utility.
2. Click View > Show All Devices.
3. Pick the physical drive, not the volume nested under it.
4. Click Erase.
5. Type a name for the drive.
6. Pick APFS if the drive stays in a Mac-only setup.
7. Pick exFAT if you use both macOS and Windows.
8. Click Erase and wait.
9. Unplug the drive, then plug it back in.
If it mounts normally after this, I’d lean toward file system corruption, not a failed drive.
If you want to try repairs before wiping it, there are a few things worth testing. I’ve had mixed results. Minor damage, sometimes yes. Heavier corruption, not so much.
Method 1: Run First Aid on the Physical Drive
Sometimes the mess is higher up in the partition structure, not inside the volume itself. People miss this and run repairs on the wrong item.
1. Open Disk Utility.
2. Click View > Show All Devices.
3. Select the top-level physical disk.
4. Click First Aid.
5. Confirm the repair.
6. Let it finish.
7. Try mounting the drive again.
If the damage is light, this step is sometimes enough.
Method 2: Kill a Hung fsck Process
I’ve seen macOS get stuck doing a background file system check, and the drive sat there unmounted the whole time. No noise, no clear warning, nothing useful on screen. It looked dead, but it wasn’t.
1. Open Terminal.
2. Run: sudo pkill -f fsck
3. Press Return.
4. Enter your admin password if macOS asks for it.
5. Wait a few seconds.
6. See if the drive mounts on its own.
This does not repair the disk. It stops a stuck background process which might be blocking the mount.
Method 3: Mount It Manually in Terminal
Disk Utility fails in weird ways sometimes. Terminal will occasionally mount a volume when the graphical tools won’t.
1. Open Terminal.
2. Run: diskutil list
3. Find your drive identifier, something like disk4s1.
4. Run: diskutil mount /dev/disk4s1
5. Replace disk4s1 with your own identifier.
6. Press Return.
7. Read the error output if it fails.
When this works, the volume mounts right away. When it doesn’t, the message from Terminal is often more useful than what Disk Utility shows. Sometimes typo city here, so double check the identifier before you hit Return.
Last thing, all of this assumes the drive hardware is still healthy. If the disk does not appear in Disk Utility at all, shows the wrong capacity, clicks, disconnects over and over, or won’t spin up or power on, I’d stop treating it like a mount problem. At that point it looks more like hardware failure. Software tools usually won’t fix much there, and extra trial and error can make recovery harder.
2 Likes
“Machine Mount HD Failed” usually means macOS tried to attach the disk’s file system and failed. It does not always mean the drive is dead. It often points to one of 4 things:
- The file system is damaged.
- The partition map is wrong or unreadable.
- macOS does not like the disk format or encryption state.
- The hardware connection is unstable.
I partly agree with @mikeappsreviewer. If the disk still shows up with the right size, that is a decent sign. I would not jump straight to killing processes in Terminal unless you already ruled out simpler checks. On Macs, mount errors are often tied to permissions, FileVault-encrypted volumes, bad ejects, or a flaky bridge board in the enclosure.
What I’d check next:
Open System Information, then USB or Thunderbolt. See if the Mac detects the device at the hardware level. If it shows there but not as a mountable volume, the issue is higher up than the cable handshake.
Then open Terminal and run:
diskutil list
Look for these clues:
- “Apple_APFS” or “GUID_partition_scheme” means the structure is at least partly visible.
- “FDisk_partition_scheme” on an older or repurposed drive sometimes causes weird behavior on newer Macs.
- A size of 0 bytes, or nonsense capacity, points more toward hardware trouble.
If the drive is APFS, one missed thing is container damage. Disk Utility sometimes shows the physical disk but fails on the APFS container or volume group. In those cases, mounting the volume alone won’t help much.
If your files matter, I’d lean toward recovery before repair. Disk Drill is worth a look on Mac because it often reads an unmounted drive well enough to pull data off before you do anything destructive. Thsi matters more if the drive disconnects, freezes Finder, or takes forever to appear.
If the drive is external and bus-powered, test it on another Mac. Not for “does it mount” only. Watch whether it appears faster, reports full capacity, and stays connected for 5 to 10 minutes. Those details tell you a lot.
If you want more Mac-specific ideas for external disks refusing to mount, this thread is useful:
fixing an external hard drive that will not mount on Mac
Short version. If the disk appears in Disk Utility or System Information, you’re often dealing with file system trouble. If it does not, or the size looks wrong, I’d suspect the enclosure, cable, port, or the drive itself. If the data is important, stop poking at it too much and recover first.
“Machine Mount HD Failed” usually means macOS can see some part of the drive, but it can’t finish attaching the volume so Finder can use it. So no, it does not automatically mean the drive is dead. I agree with parts of what @mikeappsreviewer and @viaggiatoresolare said, but I’d push one thing harder: sometimes this is a macOS mount service glitch, not just file system corruption.
A few checks I’d do that weren’t really covered:
- Restart the Mac fully, then reconnect the drive after login.
- Boot in Safe Mode and test the drive there. If it mounts in Safe Mode, some background software, login item, or third-party disk tool may be interfering.
- Check Console.app for disk arbitration or I/O errors right after the failure. That can tell you whether macOS is refusing the mount or the drive is timing out.
- If it’s an old external enclosure, the SATA-to-USB bridge can be the real problem. I’ve seen perfectly fine drives trapped inside junk enclosures.
If the disk is visible but won’t mount and the files matter, I would recover data before trying anything invasive. Disk Drill is a solid Mac option for unmounted drives because it can scan the disk directly even when Finder won’t cooperate. If the drive is acting weird, make a backup image first.
If the data does not matter, then erase/reformat is the fastest test. If erase fails too, that smells more like hardware.
Also worth checking:
Mac hard drive not mounting fix video guide
Short version:
- Seen in Disk Utility with normal size = probably logical/software issue
- Shows wrong size, disconnects, clicks, freezes = probably hardware/enclosure issue
That error is annoying, but not neccecarily a death sentence for the drive.
“Machine Mount HD Failed” is usually a mount-layer error, not a precise diagnosis. In plain English, the Mac found a disk-like device but could not turn it into a usable volume in Finder.
I mostly agree with @viaggiatoresolare, @sognonotturno, and @mikeappsreviewer, but I would push one extra angle: sometimes this comes from the startup/mount stack itself, especially after a crash, forced unplug, sleep/wake bug, or a stalled external-disk helper process. So I would not assume file system damage first every time.
A few checks that complement what they already covered:
- Try mounting from Recovery Mode Disk Utility. If it mounts there, macOS in your normal boot may be the problem.
- Check whether the disk is actually read-only because of corruption. In Terminal,
diskutil info /dev/diskXcan show mount state and whether the OS is refusing writes. - If it is an external SSD or HDD in an enclosure, test the bare drive in another enclosure if possible. I have seen more bad USB bridge boards than truly dead drives.
- Look in Console for repeated I/O errors, “diskarbitrationd” complaints, or APFS container warnings.
One thing I slightly disagree on: killing random processes is not where I’d start unless logs clearly show something hung.
If the data matters, recover before repairing. Disk Drill is useful here because it can scan an unmounted disk directly.
Disk Drill pros:
- good with unmounted volumes
- simple preview and recovery workflow
- can create a byte-to-byte image first
Disk Drill cons:
- deep scans can take a long time
- recovery quality depends on how damaged the file system is
- full recovery is paid
If the drive shows wrong capacity, drops connection, or makes noise, think hardware first. If it shows normal size, think structure or macOS mount issue first.