Mac / External SSD
Mac Disk Disappeared After Reboot
Check the device safely before creating new volumes.
A disk that disappears after reboot may have a damaged volume record, a failed mount state, or an unstable connection. Do not create a replacement volume until you have scanned for data. macOS updates can change how APFS volumes are mounted at startup, and a previously stable volume may fail to appear after a system upgrade.
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 create a new volume or container to replace the one that disappeared.
- Do not erase or repartition the disk to make it appear again.
- Do not rely on repeated reboots to fix a disk with damaged metadata.
- Do not save recovered files onto the disk that went missing after restart.
Scan and preview first
Refindo is useful when the disk appears in system storage tools or intermittently connects long enough for a scan.
Likely causes
- APFS container or volume metadata no longer loads after restart.
- External SSD or USB enclosure reconnects inconsistently.
- System update, forced shutdown, or power loss interrupted writes.
- The drive is failing and only appears intermittently.
Read-only recovery workflow
- Reconnect the disk directly to the Mac and wait for it to appear in Disk Utility.
- Open Refindo and select the disk while it is detectable, even briefly.
- Run Quick Scan, then Deep Scan when the volume record will not load after reboot.
- Preview important files and recover them to a separate drive.
When to stop self-recovery
- The disk only appears intermittently and disconnects during the scan.
- The missing disk holds the only copy of critical work.
- The drive shows signs of failing hardware rather than a mount-state issue.
- A macOS update or forced shutdown left the volume unable to mount.
Related recovery guides
What You Need to Know
APFS mount state persistence across reboots
APFS volumes depend on checkpoint data and object maps that are written during normal operation. When macOS shuts down or restarts, it finalizes these structures so the volume can remount cleanly. A forced shutdown, kernel panic, or power loss can leave the checkpoint in an inconsistent state. On the next boot, macOS may refuse to mount the volume because the last known-good checkpoint cannot be verified.
macOS update impact on external volumes
Major macOS updates can change APFS driver versions, security policies, and mount behavior. After an update, an external APFS volume that previously mounted automatically may require re-authentication, fail security checks, or encounter driver incompatibilities. This is especially common with volumes created on older macOS versions that used different APFS feature flags or encryption settings.
Frequently Asked Questions
Should I create a new volume with the same name?
No. Creating a new volume can overwrite metadata that recovery tools may need.
What if the disk only appears sometimes?
Try a stable direct connection once. If it keeps disappearing, stop and consider professional recovery.
Can rebooting again fix it?
Sometimes a mount state clears, but repeated retries do not solve damaged metadata or hardware instability.
Can a macOS update cause a disk to disappear?
Yes. System updates can change APFS driver behavior, security requirements, or mount policies that affect whether external volumes appear automatically after reboot.
Should I reset NVRAM or SMC to fix a missing disk?
NVRAM and SMC resets address startup and hardware configuration issues, not file system damage. They are unlikely to restore a volume with corrupted metadata.