My old Mac’s HFS-formatted drive won’t mount anymore, and I’m trying to recover important files before the disk gets worse. What are the safest HFS recovery steps or tools for an older Mac without risking more data loss?
First thing: stop writing to that drive if you can. That matters more than which recovery app you use.
Deleted files on HFS or HFS+ usually aren’t wiped right away, even if you emptied the Trash. macOS mostly marks that space as available, and the actual data can sit there until something else gets saved over it. So the files may still be recoverable, but every bit of drive activity makes the odds worse.
If this is your Mac’s internal drive, try not to keep using it like normal. Don’t install apps on it, don’t download anything to it, and avoid leaving it running longer than needed. If it’s an external drive, just disconnect it until you’re ready to scan it.
And yes, it’s worth trying even without a backup. For normal deletion, accidental formatting, or a drive that still appears in Disk Utility, recovery software can often find a lot. If the drive is making clicking sounds, won’t spin up, or isn’t detected at all, that’s a different situation and probably needs a recovery lab.
For a simpler tool, Disk Drill is a reasonable option because you can scan first and preview files before deciding whether to recover them.
The basic process is:
1. Install it somewhere else.
If you’re recovering the internal Mac drive, install Disk Drill on an external USB drive or another disk. If the lost files are on an external drive, install Disk Drill on the Mac instead. Don’t put the recovery software on the same drive you’re trying to recover from.
2. Select the problem drive.
Open Disk Drill, find the drive that had the missing files, and choose it from the list.
3. Start the scan.
Click Search for lost data. Large drives can take a while. You can peek at found items before the scan finishes, but letting it complete usually gives you the best shot.
4. Preview what it finds.
After the scan, the results are usually grouped by type, like documents, photos, videos, and so on. Use the preview option, the little eye icon, to check whether the files are actually intact.
5. Pick the files you want back.
Check the files you need, then choose Recover.
6. Save them to a different drive.
This part is easy to mess up. Don’t recover files back onto the same drive you scanned. Save them to another disk, another partition, or some other safe location.
One extra thing with older HFS+ Macs: journaling can sometimes help recovery tools bring back file names and folder paths, not just raw recovered files. But that journal gets reused over time too, so waiting and continuing to use the drive can erase some of the useful clues.
If Disk Drill’s scan shows your files and the previews look good, that’s usually a strong sign. At that point the main thing is getting the recovered copies onto a separate drive before anything gets overwritten.
1 Like
If the drive will not mount, assume you may only get one decent read attempt before it gets worse. I would not make the first attempt a repair. Disk Utility “First Aid” can be useful on a healthy volume with a minor catalog issue, but on a dying HFS/HFS+ disk it may change the directory structures you’re hoping a recovery tool can still interpret.
The safer order is: get another drive that is at least as large, make a clone or disk image of the bad disk, then scan the copy. On older Macs, that might mean Target Disk Mode, an external enclosure, or booting from another Mac/system drive so the bad disk is not being used as the startup volume. If you are comfortable with command-line tools, ddrescue is often used because it can skip bad sectors and come back to them later. If not, use a recovery app that can create or work from a disk image. Disk Drill is fine for the scanning part, but I would still rather scan an image than keep hammering the original drive for hours.
A small trap with old HFS volumes: if the disk appears and disappears, or makes repeated clicking/spin-up sounds, stop trying software fixes. That is when the “cheap” attempts can turn into the reason a lab gets less back later. But if the disk is stable enough to be seen by the Mac, image it first, save recovered files to a completely different disk, and avoid any tool that promises to “fix” the volume before you have copied off what you can.
A “successful” recovery can still be a bad recovery if you save old Mac files onto the wrong kind of destination disk. With HFS and older HFS+ volumes, some files may depend on resource forks, old Finder metadata, classic Mac file types, or package structure. If you dump everything straight to a FAT/exFAT USB stick or a Windows-formatted drive, you might get files that appear copied but don’t behave right later.
I agree with the image-first advice above. I would make that the dividing line between “safe attempt” and “gambling.” Don’t run First Aid yet, don’t rebuild the catalog yet, and don’t let the machine sit there repeatedly trying to mount the drive. The safest version is boring: clone the whole device to another disk or image, put the original aside, then experiment on the copy.
A detail people miss with older Macs is that “HFS” can mean two different things in casual conversation. If it was formatted as “Mac OS Extended,” that’s HFS+. If it is truly old “Mac OS Standard,” that’s HFS, and support gets thinner. Some modern recovery tools are much better with HFS+ than with original HFS. If the disk is from a late OS 9 / early OS X Mac, check what it actually is before assuming every app will understand it.
For the least risky path, I’d do something like this:
-
Remove the bad disk from normal use
If it is the startup drive, don’t keep booting from it. Boot from another drive, use Target Disk Mode if the Mac supports it, or put the drive in an enclosure. The goal is to keep macOS from writing logs, caches, Spotlight data, or other junk to the damaged volume. -
Check whether it is mechanically healthy enough to read
If it clicks, spins down, vanishes from Disk Utility, or takes multiple tries just to appear, stop. That is not a “try another app” situation. Software recovery assumes the drive can stay online long enough to read it. -
Clone the whole disk, not just the visible volume
If you can use ddrescue, clone the device level disk to another disk or image. That way you preserve the partition map, HFS catalog, extents, and whatever damaged pieces still exist. A normal Finder copy is not recovery. It only copies files the system can already understand. -
Work only from the clone or image
This is where tools like Disk Drill, R-Studio, Data Rescue, etc. make more sense. Disk Drill is fine if you want a friendlier interface and previews, but I would not point it at a failing original for a long scan unless I had no other option. Long scans are exactly the kind of constant reads that finish off weak drives. -
Recover to a Mac-native destination if the files are old Mac files
Use APFS or HFS+ for the save location if possible. If the files are just JPEGs, PDFs, MP3s, and modern Office docs, exFAT is usually less of a problem. But for old applications, Quark files, classic Mac archives, fonts, or anything from the OS 9 era, stay on a Mac-formatted destination until you know what you have.
Another small thing: don’t judge the recovery only by file count. A tool may find thousands of “files” by carving raw data, but that can lose names, folders, dates, and sometimes fork data. A smaller result that preserves the original folder tree may be more useful than a giant pile of unnamed recovered fragments.
If you do get a readable image, keep that image even after recovering the obvious files. You may later realize something important is missing, or that another tool handles the old HFS structures better. The original disk may not give you a second chance, but a good image will.
A disk that won’t mount but stays visible in Disk Utility is a very different problem from a disk that keeps dropping off the bus. In the first case, software recovery may be reasonable. In the second case, the cable, enclosure, adapter, or the drive itself may be failing, and repeated scans can make the situation worse fast.
The angle I’d be careful with is the connection method. Old Mac drives are often IDE/PATA, early SATA, FireWire, or sitting behind some cheap USB bridge that does not handle read errors well. If the drive pauses on a bad sector and the USB adapter resets, your recovery program may look like it froze or the disk may disappear halfway through. That is not always the recovery app’s fault. If you have the option, a better enclosure, FireWire Target Disk Mode, or connecting the drive to a machine that sees it reliably can matter more than switching between recovery programs.
I agree with the image-first advice, but I’d make the first “test” very small. Don’t start with a full deep scan just to see what happens. See whether the device appears consistently, whether its size is reported correctly, and whether you can read a little from the front and middle of the disk without it vanishing. If it behaves badly during that, stop and rethink. If it behaves well, then clone/image it and scan the copy.
Disk Drill or a similar tool is fine after that, especially if you want previews and a less technical interface. I would not use its recovery destination on the same disk, and I would not let it “helpfully” fix anything before you have a copy. Treat “recover files” and “repair the volume” as separate jobs. Recovery comes first. Repair is something you try later on a duplicate if you still care about making the old volume mountable.
For the recovered files, keep the first save boring and Mac-native if possible. An HFS+ or APFS external disk is safer than dumping old Mac files onto a random PC-formatted USB stick. After you have the files and have checked the important ones, then make extra copies wherever you want. The first pass should be about preserving as much structure and metadata as possible, not about convenience.