Stop all disk writes immediately if the drive holds anything you cannot afford to lose. First, swap the cable and port and check whether Disk Utility can see the drive at all with Show All Devices enabled. If the disk still will not mount, move to non-destructive diagnostics like First Aid or diskutil commands, or image the drive before anyone reformats it.
TL;DR:
- Most mounting failures stem from simple issues like faulty cables, insufficient power, or connections; testing different ports and cables can resolve 40 to 85 percent of problems.
- Disk Utility’s “Show All Devices” setting is essential for detecting drives that are physically connected but not mounted, with gray volumes indicating file system issues rather than hardware failure.
- Running First Aid on a drive with physical or mechanical damage can cause further harm; imaging the drive before repair is crucial when errors cannot be fixed.
- Use
diskutilcommands in Terminal for detailed diagnostics, verifying, and repairing disks, but avoid commands that can erase data if the drive shows signs of hardware failure.- Persistent signs of physical failure, such as clicking noises, heat, or physical damage, require professional data recovery services rather than DIY troubleshooting to prevent irreversible data loss.
Before touching Disk Utility or Terminal, rule out the boring stuff. A shocking number of “dead drive” panics turn out to be a bad cable or a sleepy USB hub, and you can eliminate both in about five minutes.
Start with power and motion. Spinning hard drives should hum or click faintly when powered. If you hear nothing at all, and there’s no LED activity, the drive may not be receiving power, which points to the enclosure, the cable, or the drive’s own circuit board rather than the file system.
Cables cause more mounting failures than most people expect. Insufficient power delivery and marginal cables are a documented, common cause of drives that refuse to mount, especially bus-powered portable drives plugged into a hub instead of directly into the Mac. A cable that charges your phone fine may not carry the data lines a drive needs.
Run through this sequence before anything else:
Pro Tip: Keep one dedicated, verified data cable in your bag labeled “known good.” When troubleshooting, that single cable rules out an entire category of problems in seconds.
Simple checks like these resolve a large share of mounting complaints before any repair tool gets involved. Roughly 40 to 85 percent of mounting issues clear up with basic steps like a cable swap, a different port, or a reboot, depending on the underlying symptom. That range is wide because “not mounting” covers everything from a loose connector to a failing head assembly, and the fix that works for one has zero effect on the other.
If the drive shows up on another computer but not yours, the problem lives in your Mac’s ports, drivers, or system state, not the drive itself. That distinction changes everything about what you try next.
Disk Utility is the first real diagnostic tool to reach for once physical checks are done, and it tells you more than most people realize if you know where to look.
Open Disk Utility, then click View in the menu bar and select Show All Devices. This step matters more than it sounds. Disk Utility hides physical devices by default, showing only mounted volumes, so a drive that’s electrically connected but not mounted can look completely absent until you toggle this setting.
With all devices visible, you’re looking at two layers: the physical disk (listed by brand and size, like “500.11 GB APPLE SSD”) and the volumes underneath it (like “Macintosh HD” or “BACKUP”). A grayed-out volume name under a visible physical disk means the drive is detected but its file system isn’t mounting, which points to a software or format issue rather than dead hardware.
Steps to attempt a manual mount:
First Aid checks and repairs the directory structure and file system metadata. On a healthy but corrupted volume, it typically finishes in a few minutes and reports “The volume appears to be OK” or lists repairs it made. On a large or failing drive, it can run for well over an hour, and a spinning progress bar with no movement for a long stretch is itself a warning sign.
Here’s the catch that most quick-fix articles skip: First Aid can repair many file system errors, but running it on a mechanically marginal drive, one that’s clicking, overheating, or intermittently dropping, can push it past the point of recovery. First Aid writes to the disk while it repairs. If the drive is failing physically, that write activity is exactly what you were trying to avoid.
Pro Tip: If First Aid reports errors it “could not repair,” stop. Do not run it again. That message means the underlying structure is too damaged for a software fix, and your next move should be imaging the drive, not repeating the repair.
One error deserves special mention because it shows up constantly in support forums: com.apple.DiskManagement.disenter. This isn’t a single specific problem. It’s a generic macOS error meaning the mount operation failed, and the real cause could be anything from a corrupted directory to a dying drive controller.
| Disk Utility Outcome | Likely Cause | Recommended Next Step |
|---|---|---|
| Volume mounts, no errors shown | Temporary glitch or loose connection | Continue normal use; back up soon |
| First Aid repairs errors, volume mounts | Minor file system corruption | Back up immediately, monitor drive health |
| First Aid fails, “could not repair” | Significant file system damage | Stop; image the drive before further action |
| Mount grayed out, disk visible | Encryption lock or severe corruption | Enter password, or move to imaging |
| Disk invisible even with Show All Devices | Power, cable, or hardware failure | Recheck cable/power; consider professional evaluation |
| disenter error repeatedly | Ambiguous mount failure | Try diskutil in Terminal; escalate if it recurs |
Terminal gives you the same information as Disk Utility, plus finer control, without the graphical layer sometimes getting in the way. It’s not scarier than the GUI once you know the vocabulary.
Open Terminal and start with a command that only reads information and changes nothing:
diskutil list and press Return. This prints every disk macOS can see, labeled disk0, disk1, disk2, and so on, with volumes beneath each labeled disk2s1, disk2s2, etc. The diskN is the physical drive; diskNsM is a specific partition or volume on it.diskutil mount /dev/disk2s2 (substituting your actual identifier). A success message returns the mount path; a failure returns an error you can search or troubleshoot further.diskutil mountDisk /dev/disk2 attempts to mount every partition on that physical disk at once.diskutil verifyDisk /dev/disk2 before attempting any repair. Verify is read-only. It tells you what’s wrong without changing anything on the disk.diskutil repairDisk /dev/disk2 or, for a specific volume, diskutil repairVolume /dev/disk2s2.A few safety notes matter more here than the syntax itself:
verifyDisk before repairDisk. Verify costs you nothing; repair writes to the disk and cannot be undone.diskutil eraseDisk or any formatting command while troubleshooting a mount failure. That’s a data-destruction command, not a diagnostic one.diskutil operation, stop immediately. Continued read attempts on a physically failing drive increase the risk of permanent data loss.If diskutil repairVolume reports success but the volume still won’t mount afterward, that’s a signal the damage goes deeper than the file system layer, possibly into the drive’s firmware or physical media, and it’s time to stop running commands and start imaging or calling in help.
Format mismatches cause a huge share of “my drive is not mounting” tickets, and the fix depends entirely on which file system you’re dealing with.
macOS reads and writes APFS and HFS+ natively without issue. It reads and writes exFAT and FAT32 as well, making those the best choice for drives shared between Mac and Windows. NTFS is where things get complicated: macOS can read NTFS drives out of the box but cannot write to them without third-party software, and NTFS volumes carry their own mounting quirks.
The NTFS “dirty” flag is worth understanding because it’s easy to misdiagnose as drive failure. Windows Fast Startup can leave an NTFS drive in an unclean state, and macOS refuses to mount a dirty NTFS volume to avoid worsening any inconsistency. The drive isn’t broken. It’s locked out by a flag Windows set.
The fix is straightforward: reattach the drive to a Windows PC, disable Fast Startup in Power Options, and shut down properly (not sleep, not restart) rather than a normal reboot. Reconnect to your Mac afterward, and it should mount normally.
If you need the data now and don’t have Windows handy, a read-only imaging tool can often pull files off an NTFS drive without needing it to fully mount. Once you’ve recovered everything you need, reformatting should always be your last step, never your first, since it destroys whatever remains on the disk permanently.
The order of operations here determines whether you get your files back or lose them permanently trying to save money.
If the drive is detected but behaving unpredictably (mounting intermittently, showing errors, but still spinning), your first move should be a read-only image, not a repair attempt. Creating a full disk image before running any write operation preserves the current state of the drive so that even a failed repair attempt doesn’t cost you the original data. Tools built for this, like ddrescue on the command line or TestDisk’s imaging function, copy sector by sector without altering the source.
DIY recovery software genuinely helps with logical problems: accidental deletion, a corrupted partition table, or a botched format. It does not help with hardware problems, and running it repeatedly against a drive with a failing head or controller wastes your best chance at professional recovery later.
Watch for these signals that DIY has reached its limit:
Once you see any of these, stop. Continuing to power a failing drive or running repeated repair passes on it can cause a head crash or push corruption further, turning a recoverable situation into an unrecoverable one. Professional recovery labs use bench-level tools, donor parts, and controlled environments specifically because consumer software cannot safely handle physical drive failure.
Pro Tip: If you’re unsure whether your drive’s problem is logical or physical, stop guessing and get a free diagnostic evaluation rather than running one more scan “just to check.” A professional read on the drive’s health costs you nothing and can save you from an irreversible mistake.
A reasonable professional recovery provider will evaluate the drive, give you an honest estimate of recoverable data, and only charge if they succeed. That last part matters more than most people realize when comparing options, since it aligns the provider’s incentive with actually getting your files back rather than billing for the attempt.
If your drive clicks, refuses to spin, disconnects repeatedly during a copy, or has survived a drop or liquid exposure, stop all disk writes immediately and stop attempting DIY fixes. Every additional power cycle or scan on a physically failing drive reduces the odds of a full recovery, and that’s the exact point where professional intervention changes outcomes.
A local provider has offered Mac hardware repair and data recovery services in Los Angeles since 2006, working on failed hard drives, SSDs, RAID arrays (RAID 0, 1, 3, and 5), and logic-board level component failures on MacBook, iMac, Mac Mini, and Mac Pro systems. Some providers offer free diagnostics and a no recovery, no charge policy, meaning you pay only for successful data recovery.
Before you call, take a few minutes to document what happened:
| Red Flag | What It Usually Means | DIY-Safe? |
|---|---|---|
| Drive spins, mounts intermittently | Logical corruption or loose connection | Often yes |
| Clicking or grinding sounds | Mechanical head or motor failure | No, stop immediately |
| No spin, no detection anywhere | Power failure or dead controller/board | No |
| Repeated disconnects during copy | Failing connector or drive electronics | No, image first if possible |
| Liquid or impact damage | Physical component damage | No |
| Mac freezes only with drive connected | Possible port or logic-board issue on the Mac | Evaluate Mac separately |
Same-day appointments are available for cases where time matters, and the shop sits centrally at 12041 Wilshire Blvd, Ste 26, between the 405 and Santa Monica Boulevard, close to UCLA and the Getty Center, serving West LA, Santa Monica, Beverly Hills, Brentwood, Westwood, Venice, Hollywood, and Culver City. During intake, expect a physical and electronic evaluation of the drive, an honest estimate of what’s recoverable, secure handling of your media, and a realistic conversation about success odds rather than a blanket promise, since RAID rebuilds, encrypted APFS volumes, and mechanically failed drives all carry different recovery probabilities. Call 310-866-0828 to get a diagnostic scheduled.
Prevention here isn’t complicated, but it does require doing a few unglamorous things consistently rather than reactively after a scare.
Back up using the 3-2-1 backup rule: three copies of your data, on two different types of storage, with one copy offsite or in the cloud. The 3-2-1 backup rule exists precisely because any single drive, no matter how well made, can fail without warning, and having redundancy across different storage types protects you from a single point of failure like a bad firmware update or a controller failure that wipes an entire drive family at once. Test your restores periodically, not just your backups. A backup you’ve never restored from is a hope, not a plan.
A few habits prevent most mounting emergencies before they start:
diskutil eject before unplugging, never pull the cable mid-transfer.None of this eliminates risk entirely, but it shifts failures from catastrophic to inconvenient, which is the entire goal.
Sometimes, but the fix looks very different depending on whether you’re on an Intel Mac or Apple Silicon, and conflating the two wastes time.
NVRAM (nonvolatile RAM) stores small settings macOS needs before fully booting, including some disk and startup preferences. NVRAM retains configuration data even when the Mac is powered off, and a corrupted NVRAM entry can occasionally interfere with how external drives are recognized at startup. On Intel Macs, you reset it by restarting and holding Option, Command, P, and R for about 20 seconds. The SMC (System Management Controller) handles power delivery, including to some USB and Thunderbolt ports, and a separate reset procedure exists for Intel machines when ports stop delivering power correctly.
Apple Silicon changes this entirely. There is no user-resettable SMC on M1, M2, or M3 series Macs, because the functions SMC handled on Intel hardware are now managed differently within Apple’s own silicon. If you find an old guide telling you to hold specific keys to reset SMC on an M-series MacBook, that advice is outdated and won’t do anything.
The Apple Silicon equivalent is a full shutdown, waiting ten seconds, then powering back on, rather than a restart. This clears the same kind of transient state that an NVRAM or SMC reset used to address on Intel hardware. If your drive mounts fine after a full shutdown but not after a simple restart, that’s a useful diagnostic clue pointing toward a low-level system state issue rather than the drive itself.
Improper ejection is one of the most preventable causes of mounting failures, and the correct sequence takes seconds longer than yanking the cable.
To disconnect safely, drag the drive icon from your desktop to the Trash (which becomes an Eject icon), or click the small eject arrow next to the drive’s name in Finder’s sidebar. Wait until the drive icon fully disappears from Finder and the desktop before touching the cable. If you’re using multiple partitions on one physical drive, eject every volume individually, since ejecting only one may leave the physical disk still active.
For a drive that seems stuck mid-file-transfer or unresponsive to normal ejection, open Terminal and run diskutil eject /dev/disk2 (using your drive’s actual identifier from diskutil list). This forces a clean unmount at the system level even when Finder’s icon seems frozen.
To reconnect after any troubleshooting session:
This sequence matters more than it seems. Yanking a drive mid-write is a leading cause of the exact directory corruption that later shows up as a mounting failure, turning a preventable mistake into a repair project.
Software bugs introduced in specific macOS releases have, more than once, broken mounting behavior for certain drive types, particularly around APFS handling and third-party drivers for older enclosures.
Check your current macOS version under the Apple menu, then System Settings, then General, then About. Compare it against Apple’s release notes for known storage-related fixes in recent updates. If your drive stopped mounting immediately after a macOS update and worked fine before, that timing is a strong clue the update introduced or exposed a compatibility issue rather than the drive itself failing.
Before updating further to chase a fix, check whether the specific external drive or enclosure manufacturer has published a compatibility note or firmware update addressing the current macOS version. Enclosure controllers sometimes need firmware updates to keep pace with macOS changes, and an enclosure that was rock solid on last year’s OS can develop mounting issues after a major system update changes how USB or Thunderbolt controllers are addressed.
If you suspect a system bug rather than a hardware problem, testing the same drive on a different Mac running a different macOS version is the fastest way to confirm it. A drive that mounts fine on an older OS version but not on the newest release points squarely at software, not the drive, and often resolves itself with the next point update from Apple as compatibility issues get patched.
Most repeat mounting failures trace back to the same handful of avoidable habits, and fixing them takes less effort than dealing with another emergency.
Rotate drives out before they age into failure territory rather than waiting for symptoms. Mechanical hard drives typically show measurable wear after three to five years of regular use, and SSDs, while more durable in daily handling, still have finite write cycles worth tracking on drives used for constant backups.
Keep firmware current on enclosures, especially ones from smaller manufacturers, since controller firmware updates often specifically address macOS compatibility issues before they become widespread complaints. Standardize on one or two known-good cable types across your setup instead of grabbing whatever cable is closest, since cable-related failures are both common and completely preventable with basic organization.
Finally, treat any single mounting failure as information, not just an inconvenience to clear and forget. A drive that failed to mount once and now works fine isn’t necessarily healthy. It may be an early warning that deserves a backup check and a health scan rather than a shrug, particularly if the drive holds anything irreplaceable.
Most guides treat a mounting failure as a puzzle to solve as fast as possible. That’s the wrong instinct. The right first question isn’t “how do I get this drive working again,” it’s “what’s actually on this drive, and can I afford to lose it if my next step goes wrong.”
Conventional troubleshooting advice tends to march straight into First Aid and repair commands without pausing to ask whether the drive is even a candidate for safe repair in the first place. That sequence works fine for a healthy drive with a corrupted directory. It’s actively dangerous for a drive that’s mechanically failing, because every repair attempt writes to a disk that may not survive many more write cycles.
The judgment this topic actually supports is simple: imaging before repairing, verifying before fixing, and recognizing hardware failure symptoms early aren’t optional caution, they’re the entire difference between a full recovery and a permanent loss. If there’s one thing DIY guides consistently underweight, it’s how often people keep troubleshooting past the point where a professional evaluation would have preserved more options. Free diagnostics exist precisely so that decision doesn’t have to be a gamble.
— Kaya
If you’ve worked through the checks above and your drive still won’t mount, or it’s showing clicking, heat, or physical damage, further DIY attempts risk turning a recoverable situation into a permanent loss. Experienced local providers in Los Angeles handle a range of Mac hardware and data recovery cases, offering in-person evaluations and diagnostic services, often with no charge for diagnostics and no fees unless data is recovered.
Start with a free evaluation of your hard drive before attempting another repair command, or call 310-866-0828 to book a same-day appointment at 12041 Wilshire Blvd, Ste 26, serving West LA, Santa Monica, Beverly Hills, and the surrounding neighborhoods. If the mounting failure turns out to be tied to a damaged port or logic board rather than the drive itself, the same visit can cover a Mac repair evaluation as well.
The most common causes are a bad or underpowered cable, a hidden device setting in Disk Utility, a corrupted file system, or an NTFS drive left in a “dirty” state by Windows. Less commonly, it points to a mechanically failing drive that needs professional evaluation rather than software fixes.
It means macOS can detect the physical device but has not attached its file system to the Finder, usually because of file system corruption, an encryption lock, or a format macOS cannot fully process. Checking Show All Devices in Disk Utility confirms whether the drive is detected at all before you troubleshoot further.
SSDs typically fail to mount due to file system corruption, a failing USB-to-SATA or NVMe bridge chip inside the enclosure, or power delivery issues rather than mechanical wear. Since SSDs don’t show physical failure signs like clicking, run diskutil verifyDisk early to check for underlying corruption before assuming the drive itself has failed.
A drive that won’t eject usually has an open file, a background process (like Time Machine or Spotlight indexing) still accessing it, or an application holding a connection open. Closing all related applications and running diskutil eject /dev/diskN in Terminal forces the unmount when Finder’s eject button fails.
First Aid is safe for drives with simple logical corruption but can worsen damage on a mechanically failing drive, since it writes to the disk during repair. If the drive shows warning signs like clicking or intermittent detection, image it first or get a free diagnostic evaluation before running any repair tool.
Stop disk writes, use macOS Recovery or Share Disk, and unlock FileVault if you can.…
SMART status failing? Stop writes and image the drive first. Get quick OS checks, learn…
Stop writes and power down. TRIM and encryption can erase SSD files in minutes. Get…
Technician led RAID 0 triage: stop writes, image disks read only, reconstruct stripes or escalate…
Power off and take a corroded MacBook to a West LA shop within 4–6 hours…
Fast, practical fixes from a West LA repair shop: Activity Monitor checks, simple cleaning steps,…