Mac / External SSD
SSD Shows Up but Cannot Open
Recover files before forcing the volume to mount.
A visible SSD that cannot open usually means the hardware identity is present, but the file system cannot provide a normal folder view. Understanding the distinction between the device appearing in the system and a volume being mountable helps clarify why the SSD is "there" but not accessible.
First: do not make the source worse
Treat this as a recovery situation before you treat it as a repair task. The priority is to preserve readable data and avoid new writes to the affected device.
- Do not erase the SSD just because it appears but will not open.
- Do not run repeated First Aid attempts on a volume that fails to mount.
- Do not keep retrying if the SSD opens briefly then disconnects.
- Do not save recovered files onto the same SSD.
Scan and preview first
Refindo can help when the SSD remains detectable and you need to scan files without writing fixes to the source.
Likely causes
- File system metadata damage on APFS, exFAT, NTFS, or FAT32.
- Permission, encryption, or mount-state problems.
- Bad enclosure, cable, hub, or port.
- SSD media or controller issues that affect reads.
Read-only recovery workflow
- Connect the SSD directly with a known-good cable and stable port.
- Open Refindo and select the SSD at the device level even if no volume mounts.
- Run Quick Scan, then Deep Scan when the file system metadata is damaged.
- Preview files and recover them to a different drive.
When to stop self-recovery
- The SSD opens briefly then disconnects, or reads fail partway through.
- The SSD holds the only copy of irreplaceable files.
- The drive reports I/O errors or an incorrect capacity.
- TRIM may have already cleared blocks if files were deleted before this started.
Related recovery guides
What You Need to Know
Device visible vs volume mountable: the distinction
macOS detects storage devices at two levels. The IOKit layer identifies the physical device and its controller, which is why it appears in System Information or Disk Utility. The VFS layer then attempts to mount a file system from that device. When the file system metadata is damaged, the device remains visible but no volume is mountable. Recovery tools can often work at the device level without needing a mounted volume.
How permissions and encryption prevent opening an SSD
macOS file permissions, ACLs, and ownership settings can prevent a user from accessing a mounted volume even when it is technically mountable. FileVault or third-party encryption adds another layer: the volume may mount but remain locked until credentials are provided. If the SSD shows a lock icon in Disk Utility, the issue is likely encryption rather than corruption, and different steps are needed.
Frequently Asked Questions
Why can I see the SSD but not open it?
The operating system can identify the device, but the volume metadata may be damaged or unmountable.
Can permissions cause this?
Permissions can block access in some cases, but unreadable or unmountable volumes should be scanned before repair.
Should I copy files if the SSD opens briefly?
Copy the most important files to another disk first. If reads fail or the drive disconnects, stop.
How do I tell if the problem is encryption vs corruption?
Check Disk Utility. If the volume shows a lock icon, it is likely encrypted and needs credentials. If it shows as unmounted or greyed out without a lock, corruption is more likely.
Can changing ownership or permissions fix access to the SSD?
If the volume is actually mounted but access-denied, adjusting permissions may help. However, if the volume is unmountable, the issue is file system damage, not permissions.