Disk Utility can’t repair or mount my Mac hard drive, and I’m worried about losing important files. I need advice on safe Mac hard drive recovery options, what tools to try next, and how to avoid making the drive worse.
Deleted files are often not gone right away. A normal delete or quick format usually just removes the file system’s pointer to the data. The actual blocks may still be sitting there until something overwrites them, the drive’s controller clears them, or the device has a physical failure.
So the first thing to do is stop using that drive as much as you can. Normal computer use can quietly write a lot of stuff in the background, including caches, logs, swap files, app data, and updates. Any of that can land on top of data you’re trying to recover.
If it’s an external drive, unplug it. If the missing files were on the Mac’s internal drive, keep usage to a minimum and don’t install recovery software onto that same volume.
Start with the simple, safer checks before running scans. Look in the macOS Trash first. For an external drive, it may have its own hidden trash folder. Open the drive in Finder, press Shift + Command + Period to show hidden files, then check the .Trashes folder. If the files are there, you may be able to restore them with “Put Back.”
After that, check Time Machine if it was enabled. Open Time Machine, go back to a snapshot from before the files were deleted, choose what you need, and restore it. A backup restore is usually a lot safer than scanning the original drive for deleted files.
If there’s no usable backup, then move on to recovery software. A tool like Disk Drill can scan common Mac file systems like APFS and HFS+, and it supports both file-system scans and file-signature scans.
Those two scan types work a little differently. A file-system scan tries to rebuild deleted records, including names, folders, paths, and other metadata. A signature scan looks through the raw storage for recognizable file patterns. That can still find files when the directory information is damaged, but the original filenames and folder structure may be missing.
If the drive seems unstable, don’t keep hammering it with scans. Slow reads, disappearing from the system, I/O errors, or random disconnects can point to a failing device. In that case, make a sector-by-sector or byte-for-byte image first, then scan the image instead of the original drive. That keeps extra reads off the failing hardware and gives you a stable copy to work from.
Mechanical warning signs are more serious. Clicking, grinding, repeated spin-up attempts, recalibration sounds, or weird spinning behavior can mean damaged heads, motors, bearings, or platters. Repeatedly powering it on or running long scans can make the damage worse. If the data is valuable, disconnect the drive and talk to a professional clean-room recovery service.
Whatever you recover, save it somewhere else. Do not restore recovered files back onto the same drive you’re recovering from, since that can overwrite more recoverable data.
Once you get through the recovery attempt, set up backups so this is not a one-shot situation next time. Time Machine is good for local versioned backups, and an off-site or cloud backup covers things like theft, fire, physical damage, or another drive failure. Until then, keep the original drive untouched as much as possible and work from the least risky option toward the more aggressive ones.
If FileVault is enabled, the recovery path changes because no scanner is going to magically read the files until the APFS volume is unlocked first. Before buying or running anything, check whether the disk shows as an encrypted volume in Disk Utility or Terminal, and make sure you have the Mac login password or recovery key, since Disk Drill and similar tools can only help after that access problem is solved.
Disk Utility failing doesn’t mean the files are gone, and it also doesn’t mean you should click Erase, Initialize, or “fix” every prompt macOS throws at you. Before recovery software, I’d try the boring hardware checks: different cable, different port, no USB hub, and if it’s a bare SATA drive, a different enclosure or dock. A flaky adapter can look exactly like a dying disk. If it still won’t mount but shows up in Disk Utility or diskutil list, then yeah, image it first if possible and scan the image with something like Disk Drill rather than the original. If the drive doesn’t show up at all, makes noises, or drops out during reads, stop testing it. At that point the cheap DIY path can turn an annoying recovery into a much worse one.
Boot from another Mac or an external macOS installer before you do anything else to the problem drive. If this is the internal drive, every normal boot can write logs, swap, Spotlight data, and other junk to the same disk you are trying to recover. Recovery Mode is better than a normal boot, but don’t reinstall macOS, don’t create a new user, and don’t let it “set up” the disk.
I slightly disagree with the idea that imaging is always the first move in every case. It is the safest technical answer, but if the drive is barely staying online and you can briefly see folders, I’d grab the most important stuff first to another disk. Photos, documents, project folders, whatever cannot be replaced. A full clone can take hours and may die halfway through. If the drive is stable enough, then yes, clone/image it and scan the clone with Disk Drill or another recovery app instead of beating up the original.
Small caveat people forget: if this is an SSD, especially an internal Mac SSD, deleted-file recovery can be much less successful because of TRIM and APFS behavior. Recovery software may still help with damaged directories, lost partitions, or unmounted volumes, but it is not magic if the storage has already cleared the blocks. For a clicking spinning hard drive, stop. For an SSD that appears normally but will not mount, keep it read-only as much as possible, work from another boot device, and recover to a completely separate drive. Never save recovered files back onto the same disk.