Mac / External SSD
Mac External Drive Shows in Disk Utility but Not Finder
Scan the disk before forcing a mount or erase.
Disk Utility can show a physical device even when Finder cannot mount its volume. That difference is important: the drive may still be scanable. Finder relies on a successfully mounted volume to display a drive, while Disk Utility communicates with the storage controller directly and can show devices that have no mountable file system.
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 drive just because Finder will not show it.
- Do not click Mount repeatedly when the volume keeps failing to mount.
- Do not force-mount the volume with Terminal commands before scanning.
- Do not save recovered files onto the same drive.
Scan and preview first
Refindo can scan the disk or volume when macOS detects it, then preview recoverable files before recovery.
Likely causes
- The volume is unmounted because file system metadata is damaged.
- APFS container, exFAT, or partition records cannot be opened.
- Permissions, encryption, or mount-state issues.
- Connection instability or media read errors.
Read-only recovery workflow
- Confirm Finder is set to show external disks, then connect the drive directly.
- Open Refindo and select the drive that Disk Utility detects.
- Run Quick Scan, then Deep Scan when the volume is unmounted due to metadata damage.
- Preview important files and recover them to a separate drive.
When to stop self-recovery
- The drive disconnects during the scan or reports read errors.
- The drive holds the only copy of critical work.
- A force-mount attempt has already triggered journal replays or writes.
- The connection or media is visibly unstable.
Related recovery guides
What You Need to Know
Finder vs Disk Utility mount mechanism differences
Finder displays volumes that are mounted through the VFS (Virtual File System) layer. Disk Utility shows both mounted volumes and unmounted devices visible at the IOKit storage layer. When you click Mount in Disk Utility, it asks the VFS layer to attach a file system driver to the device. If the metadata is damaged, this mount request fails. Disk Utility still sees the device because IOKit detection does not require readable file system structures.
Risks of manual mount commands in Terminal
Users sometimes try mounting drives manually using diskutil mount or mount_apfs commands in Terminal. These commands attempt the same operation as the Disk Utility Mount button but with additional flags. Force-mounting with incorrect options can attach a damaged file system in a writable state, allowing the kernel to write journal replays or metadata corrections. This can silently alter structures that recovery tools need.
Finder sidebar and desktop visibility settings
Before assuming a drive is unmountable, check Finder preferences. Under Settings > Sidebar and Settings > General, external disks may be hidden from the sidebar or desktop even when mounted. A drive that appears mounted in Disk Utility but is absent from Finder may simply have its visibility toggled off. This is a preference issue, not a data loss scenario, and no recovery action is needed.
Frequently Asked Questions
Why does Disk Utility see it but Finder does not?
Disk Utility can list devices that do not have a mountable volume for Finder.
Should I click Mount repeatedly?
A single mount attempt is reasonable, but repeated failures mean you should scan before repair.
Should I erase the drive?
Only after recovery is complete and you have verified important files.
Could Finder settings be hiding my external drive?
Yes. Check Finder > Settings > Sidebar and General to confirm external disks are set to appear. If the drive is mounted but hidden by a preference, no recovery is needed.
Is it safe to use Terminal mount commands on an unmountable drive?
Manual mount commands carry risk. Force-mounting a damaged volume can trigger journal replays or metadata writes. Scan the drive first if data matters.