External SSD Not Mounting on macOS: What To Do Next

Run each step once. Repetition is where the damage happens.

1. Change the cable. Use one you know carries data, ideally the cable the drive shipped with. Plenty of spare USB-C cables are charge-only or run at USB 2.0 speed, and a fast NVMe enclosure can behave oddly or fail to power up on one.
2. Plug straight into the Mac. No hub, no dock, no monitor port, no extension lead. Shared bandwidth and limited downstream power cause a surprising share of mounting failures.
3. Try one other computer. One attempt is enough to tell you whether the problem travels with the drive.
4. Open Disk Utility and choose View → Show All Devices. This reveals the physical disk even when no volume mounts, which is the single most useful thing you can learn.
5. Check the system report. Apple menu → About This Mac → More Info → System Report, then look under USB or Thunderbolt/USB4 for the device.

Now read the result:

• Nothing appears anywhere. The Mac cannot see the device electrically. That points to the cable, the enclosure, the bridge chip or a dead drive.
• The physical disk appears but no volume does. The drive is responding. The obstacle is more likely the filesystem, the APFS container or the drive's internal mapping.
• It appears, vanishes, reappears. Stop here. Intermittent behaviour usually means something failing under load, and every retry is another chance for it to drop out mid-write.

If the data is irreplaceable and these checks gave you nothing, that is the moment to stop, not the moment to start downloading recovery utilities.

People say "my SSD died", but a portable SSD is three parts stacked together, and they fail independently.

• The enclosure. Shell, connector and a small board. Connectors crack and solder joints fatigue, and the port absorbs the shock every time the drive is knocked off a desk.
• The bridge. A translator chip that converts USB or Thunderbolt into NVMe or SATA. It is one of the most common failure points in a portable SSD, and it is the best one to have.
• The drive inside. An NVMe or SATA SSD with its own controller, its own firmware and its own NAND flash chips. This is where your data actually lives.

A dead bridge with a healthy drive behind it is a good outcome. In our laboratory the drive comes out of the enclosure and is imaged directly on a native interface, and the enclosure never matters again. That board-level work is done for one purpose only: to make the media readable long enough to copy it. You receive your recovered files, not a repaired device.

Two complications are worth knowing about. Many slim stick-style drives have the flash soldered onto the same board as the bridge, so there is no separate drive to remove and the work happens at chip level. And some enclosures encrypt at the bridge, which makes the flash inside meaningless without that specific bridge or the password that unlocks it. If your drive came with software that asks for a password, say so, and keep the enclosure and cable together.

Should you open it yourself? If the data is irreplaceable, no. Prising apart a glued enclosure is a common way for a recoverable drive to become an unrecoverable one.

The connector on the end of the cable tells you very little about what is running through it. USB-C is a shape. What it carries might be any of several protocols at very different speeds and power levels, and mismatches look exactly like a dead drive.

This matters most when you test on a second computer. If you plug a Thunderbolt enclosure into a Windows laptop with a plain USB-C port and nothing happens, you have learned nothing about the drive. Test on a machine you know supports the same connection, using the drive's own cable, straight into the port.

Heat is the other half of it. A fast NVMe enclosure draws real current and gets genuinely hot. A drive that mounts, copies a few gigabytes and then disappears may have a thermal or power problem rather than a data problem, although a failing controller looks identical from the outside.

If Disk Utility lists the physical disk but the volume underneath is missing or greyed out, the drive is talking to your Mac and the obstacle is in the filesystem structure.

APFS is layered. The physical disk holds a container, and the container holds the volumes. Damage the container metadata and every volume inside it disappears at once, even though the data itself is still sitting on the flash. That is why a drive can look completely empty and still be largely intact.

The dialog that catches people out. macOS offers to initialise the disk (the button reads "Initialize" on a US-English Mac), alongside Ignore and Eject. Choose Ignore or Eject. Initialise opens Disk Utility with your drive selected and erasing one click away.

Run First Aid once, not five times. First Aid runs a filesystem check that writes its conclusions back to the drive. On a healthy drive with light corruption, that is exactly what you want. On a drive with a struggling controller or a badly damaged container, a write in the wrong place makes the damage permanent. If it reports that the volume could not be verified or repaired, stop. Repeat runs do not improve the odds; they simply add more mount attempts and more chances of a failure mid-write.

Also avoid:

• Erasing and reformatting. The common online advice to "reformat and then run recovery software" is written for hard drives. On flash it is often the step that ends the recovery.
• Restoring a Time Machine backup over the top before you know whether that backup is complete.
• Running DIY recovery tools on the failing drive itself. A deep scan means hours of continuous reading from hardware that is already misbehaving. Work from an image or do not work at all. That is the core of what we do in Mac data recovery and SSD data recovery.
• Leaving it plugged in and hoping. A powered SSD is never truly idle.

This part surprises people who have successfully recovered deleted files from a hard drive before.

On a hard drive, deleting a file removes the pointer to it. The data stays on the platters until something else writes over it, which is why deleted file recovery so often works.

Flash cannot behave that way. A block has to be erased before it can be written again, so the operating system sends a TRIM command telling the drive which blocks are no longer in use. The drive's own housekeeping then erases them in the background, often within minutes, and from that point those addresses return nothing but zeros. There is no fragment left to carve out. The data is genuinely gone rather than merely hidden.

Whether TRIM reaches a particular external SSD depends on the enclosure, the connection and the operating system, and you cannot tell from the outside which happened. Assume it did.

Two practical consequences follow:

• If you deleted something by accident, unplug the drive immediately and leave it powered off. Every minute it stays connected gives the controller time to finish tidying up.
• A scan that lists your old filenames is not proof the files survive. Directory entries can outlive their contents, so a tool may show a hopeful list and then produce zero-filled files. We check contents before quoting, which is part of the reason you see and confirm the recovered file list before you pay anything.

Accidental deletion on a spinning external hard drive is a different and usually far more optimistic conversation.

An SSD controller does not store your data where the computer asks it to. It spreads writes across the flash to even out wear, shuffles data in the background, holds spare capacity in reserve, and maintains a translation table mapping every logical address to wherever the data physically ended up. That table is the only thing that makes the flash chips mean anything.

When a controller or its firmware fails, the NAND is often perfectly undamaged and completely unreadable. There is no seized motor to work around and no donor part that hands back the map.

Reading the flash chips directly is possible in some cases, but it is closer to a research problem than a procedure. The data is interleaved across planes, scrambled, and wrapped in error correction that differs by manufacturer and by generation. Some combinations are understood. Some are not.

Encryption narrows it further. Most modern SSDs encrypt what they write to the flash using a key held inside the controller, whether or not you ever set a password. If the controller cannot be brought back, that key context can be gone with it.

Where you set the encryption yourself, we need your own password or recovery key. FileVault on a Mac, or a BitLocker-encrypted external used with Windows: nobody can read those volumes without the credential, ourselves included, and we will not suggest otherwise. If you do have the password, tell us early, because it changes what is possible.

So the honest comparison. A hard drive that has failed mechanically follows a known path: cleanroom, head-stack work, donor parts held in stock, image the platters. An SSD is a data-processing problem, and a proportion of SSD failures currently have no path at all, at any price, from anyone. We would rather tell you that at diagnosis than after you have spent money.

Diagnosis is free, and it is the only way to know which of the faults above you are dealing with.

• Tell us what has already been tried, including First Aid, reformatting or any recovery software. It is not a test. It genuinely changes our approach.
• Bring the enclosure, its cable and any power adapter, plus the model details. If the drive was used with a password or bundled security software, mention it.
• We work from an image wherever the drive allows it, so the original is read as few times as possible.
• You get a fixed written quote before any work begins, and you see the recovered file list and confirm it before you pay. No recovery, no fee on standard cases.
• Everything stays here. The work is done on our own premises in our own in-house cleanroom, nothing is sent overseas, files are handled in line with Singapore's PDPA, and NDAs are available on request.

CBL has been recovering data in Singapore for over 20 years, with more than 140,000 recoveries completed and a rating of 4.9 stars from 909 Google reviews. If you want a sense of how recovery work is priced before you come in, our data recovery cost page sets out how quoting works.

Walk in at 6 Harper Road, Leong Huat Building #05-02, Singapore 369674, beside Tai Seng MRT, Monday to Friday 9.30am to 6.30pm. Weekends and public holidays by appointment. Call +65 6588 0261, WhatsApp +65 8127 7508, or send us the details of the drive and we will tell you what to do with it before you plug it in again.

• Data Recovery Singapore
• Data Recovery Cost in Singapore
• Hard Drive Recovery in Singapore
• SSD Data Recovery in Singapore