A failed Time Machine drive does not mean your backups are gone. The backup data is often still on the media, even if the drive is clicking, the APFS container is corrupted, or a network sparsebundle will not mount. The recovery approach depends on the file system (HFS+ vs. APFS), the storage type (HDD vs. SSD), and the failure mechanism (physical vs. logical).
Do not run Disk Utility First Aid on a drive that is clicking or making unusual sounds. Free evaluation. No data, no fee.
Time Machine backup drives fail for the same reasons any external drive fails: mechanical wear, firmware corruption, physical damage, or logical errors. Several factors make backup drives more vulnerable than typical storage.
Most Time Machine drives are 2.5" portable external HDDs (Seagate Backup Plus, WD My Passport, LaCie Rugged). These drives run constantly during scheduled backups and are frequently moved between locations. The combination of high duty cycles and portability leads to head degradation, spindle bearing wear, and drop damage. A dropped external drive with head damage requires donor head transplant in a clean bench.
Modern consumer 2.5" external drives from Seagate and Western Digital increasingly use Shingled Magnetic Recording (SMR). APFS Time Machine writes generate heavy random metadata updates (snapshots, CoW block allocation). SMR drives handle random writes poorly; the firmware translator must constantly remap logical addresses to physical zones. An interrupted backup (unplugging during a write, power loss) can corrupt the translator, leaving the drive spinning but returning zeros across the entire volume. Recovery requires PC-3000 terminal access to read the raw physical zones, bypassing the corrupted translator. The same approach applies to WD SMR translator failures.
APFS snapshots accumulate as Time Machine creates new backups. If the drive fills up and macOS cannot thin old snapshots, the APFS Space Manager (Spaceman) can desynchronize. The drive may report zero free space or mount as read-only. Attempting to copy data from a read-only APFS volume with corrupted snapshots can trigger persistent Error 36 codes or kernel panics. Do not force-eject or attempt to repair in this state.
Network-stored Time Machine backups (.sparsebundle) depend on a stable connection throughout the backup write. Wi-Fi drops, NAS reboots, or macOS sleep interruptions during a backup can leave the sparsebundle in an inconsistent state. The token file that tracks the current write position corrupts, and macOS refuses to mount the image. The thousands of 8MB band files remain intact; the problem is the metadata wrapper, not the backup data.
Running First Aid on a Time Machine drive with physical symptoms (clicking, grinding, slow response) executes fsck_apfs or fsck_hfs. These utilities perform exhaustive random reads across the entire drive surface to verify every metadata structure. On an APFS Time Machine volume with heavy snapshot fragmentation, this means the read/write heads must sweep back and forth across the platters continuously.
If the heads are already weakened from wear or impact, this forced sweeping accelerates damage. Degraded heads that could have completed a controlled sector-by-sector image under PC-3000 instead fail catastrophically, potentially scoring the platters and making the data permanently unrecoverable. Run First Aid only once, on a drive that sounds and responds normally. If it fails, stop.
Network Time Machine backups stored on a NAS, AirPort Time Capsule, or shared Mac volume use the .sparsebundle format. When the sparsebundle metadata corrupts, standard hard drive recovery software cannot access the backup data. Recovering these backups requires understanding the internal structure of the virtual disk and manually reassembling its components.
A .sparsebundle is a macOS bundle directory that Finder presents as a single file. Inside, it contains a bands subdirectory holding the actual binary data as thousands of individual files. Each band file is named with a sequential hexadecimal number (0, 1, 2, ... a, b, ... 1a, 1b) and stores exactly 8 MiB (8,388,608 bytes) of data. Together, these bands form a virtual block device; the first band maps to byte 0 of the virtual disk, the second to byte 8,388,608, and so on.
Three root-level metadata files control the bundle:Info.plist defines the disk geometry and band size, a token file tracks the active write state, andcom.apple.TimeMachine.MachineID.plist records the backup source machine identifier and verification flags. macOS reads these files through the DiskImages framework (hdiutil) to assemble the bands into a loopback device (/dev/diskX), which is then mounted as a standard APFS or HFS+ volume.
A 1 TB virtual disk only consumes physical space equal to the data written into the bands. Empty bands are not allocated on disk, keeping the sparsebundle's footprint proportional to the backup size rather than the maximum capacity.
Consumer data recovery tools (Disk Drill, EaseUS, R-Studio) operate at the file system level. They require the operating system to mount a volume before scanning it. When a sparsebundle's Info.plist or token file corrupts from a network interruption during a Time Machine write, hdiutil cannot attach the virtual disk. Disk Utility reports the image as unreadable.
Without a mounted volume, consumer tools see only a directory containing thousands of 8 MiB files with hexadecimal names. They have no mechanism to recognize these as sequential chunks of a virtual block device, calculate the band-to-offset mapping, or locate the APFS container header or HFS+ volume header embedded within the concatenated stream.
The same limitation applies to the "sparsebundle already in use" lock error. When a Wi-Fi drop or NAS reboot interrupts a backup write, the NAS file server fails to release the lock on the token file. macOS refuses to attach the bundle, and no consumer tool can bypass this because the problem is in the metadata wrapper, not the backup data itself.
Our approach bypasses the macOS DiskImages framework entirely. If the underlying NAS or external hard drive has a physical failure, we image the host drive first using PC-3000 or DeepSpar Disk Imager to capture the raw sectors containing the sparsebundle directory.
From the imaged copy, we extract the bands directory and concatenate the band files in hexadecimal order to reconstruct the raw virtual disk as a flat binary image. The APFS or HFS+ file system does not begin at byte zero of this image; there is a partition offset defined by the original GUID Partition Table embedded in the early bands. We calculate this offset and locate the volume header.
For HFS+ Time Machine volumes (macOS Catalina and earlier), we parse the catalog B-tree to rebuild the directory structure. HFS+ Time Machine backups use directory hard links, a feature unique to HFS+, to reference unchanged files across incremental backup snapshots without duplicating data. If the catalog file is corrupted, we reconstruct it by cross-referencing the Extent Overflow File and the Allocation Bitmap to map file extents back to their directory entries.
For APFS Time Machine volumes (macOS Big Sur and later), we scan the reconstructed image for checkpoint superblocks and rebuild the Object Map to locate snapshot metadata. Each Time Machine backup corresponds to an APFS snapshot; recovering multiple backup dates requires parsing the snapshot chain from the most recent checkpoint backward. This process runs on the flat image, not on the original media, so it can be repeated without risk. For related Mac data recovery scenarios involving the internal drive rather than the backup, a different approach applies.
Every Time Machine recovery starts with a forensic image of the source drive. We do not mount the drive in macOS or attempt file system repair on the original media. The imaging step creates a sector-level clone that preserves the current state of the media for offline analysis.
If the drive has physical symptoms, we address those first. For clicking or beeping HDDs, we open the drive in a 0.02µm ULPA-filtered clean bench and transplant matched donor heads. For drives with firmware corruption (detected but wrong capacity, no mount), we access the Service Area through PC-3000 to repair the translator and module tables. For SSDs with board damage, we perform component-level repair under a microscope.
The drive is connected to PC-3000 (HDDs) or PC-3000 SSD (solid state drives). We create a complete sector-by-sector image to a healthy target drive. For unstable HDDs with bad sectors, we use DeepSpar Disk Imager with head maps and selective read retries to maximize data capture while minimizing stress on the degraded media.
On the image, we parse the Time Machine file system structures. For HFS+ volumes, we reconstruct the catalog B-tree to map file names, directory paths, and backup timestamps from the Backups.backupdb hierarchy. For APFS volumes, we scan for checkpoint superblocks and reconstruct the Object Map to locate snapshot data. For sparsebundles, we reassemble the 8MB band files by parsing the band index and reconstructing the token metadata.
Recovered backup data is extracted and verified: files are checked for integrity, directory structures are confirmed against the Time Machine backup index. The recovered data is copied to a new external drive and shipped back via insured carrier. If the backup drive contained multiple backup snapshots, we recover as many snapshots as the media condition allows.
Some users configure external SSDs (Samsung T7, SanDisk Extreme) as Time Machine destinations. SSD recovery follows different rules than HDD recovery. If macOS sent TRIM commands to the SSD controller (which happens when deleting old backups or reformatting), the affected blocks are purged from the Flash Translation Layer. The controller returns zeros for those addresses regardless of what software you run.
For a full explanation of TRIM behavior across operating systems, see our TRIM and data recovery guide.
The external backup drive itself has failed (clicking, not mounting, corrupted file system). Your Mac still works. You need the backup data recovered from the failed external drive. This is standard external drive recovery: we image the drive, reconstruct the Time Machine file system, and return the backup data.
Your Mac has died (logic board failure, liquid damage, storage failure) and you want to restore from your Time Machine backup. If the backup drive is healthy, you can restore to a new Mac using Migration Assistant. If your Mac's internal storage has failed and you have no backup, see our Mac data recovery service.
Time Machine backup drive recovery is priced by the storage type and failure complexity. Most Time Machine drives are external HDDs; pricing follows the standard hard drive tiers. External SSDs follow SSD pricing.
Your drive works, you just need the data moved off it
$100
3-5 business days
Functional drive; data transfer to new media
Rush available: +$100
Your drive isn't recognized by your computer, but it's not making unusual sounds
From $250
2-4 weeks
File system corruption. Accessible with professional recovery software but not by the OS
Starting price; final depends on complexity
Your drive is completely inaccessible. It may be detected but shows the wrong size or won't respond
$600–$900
3-6 weeks
Firmware corruption: ROM, modules, or translator tables corrupted; requires PC-3000 terminal access
CMR drive: $600. SMR drive: $900.
Your drive is clicking, beeping, or won't spin. The internal read/write heads have failed
$1,200–$1,500
4-8 weeks
Head stack assembly failure. Transplanting heads from a matching donor drive on a clean bench
50% deposit required. CMR: $1,200-$1,500 + donor. SMR: $1,500 + donor.
50% deposit required
Your drive was dropped, has visible damage, or a head crash scraped the platters
$2,000
4-8 weeks
Platter scoring or contamination. Requires platter cleaning and head swap
50% deposit required. Donor parts are consumed in the repair. Most difficult recovery type.
50% deposit required
Our "no data, no fee" policy applies to hardware recovery. We do not bill for unsuccessful physical repairs. If we replace a hard drive read/write head assembly or repair a liquid-damaged logic board to a bootable state, the hardware repair is complete and standard rates apply. If data remains inaccessible due to user-configured software locks, a forgotten passcode, or a remote wipe command, the physical repair is still billable. We cannot bypass user encryption or activation locks.
No data, no fee. Free evaluation and firm quote before any paid work. Full guarantee details. Head swap and surface damage require a 50% deposit because donor parts are consumed in the attempt.
Rush fee: +$100 rush fee to move to the front of the queue.
Donor drives: Donor drives are matching drives used for parts. Typical donor cost: $50–$150 for common drives, $200–$400 for rare or high-capacity models. We source the cheapest compatible donor available.
Target drive: The destination drive we copy recovered data onto. You can supply your own or we provide one at cost plus a small markup. For larger capacities (8TB, 10TB, 16TB and above), target drives cost $400+ extra. All prices are plus applicable tax.
Your drive works, you just need the data moved off it
$200
3-5 business days
Functional drive; data transfer to new media
Rush available: +$100
Your drive isn't showing up, but it's not physically damaged
From $250
2-4 weeks
File system corruption. Visible to recovery software but not to OS
Starting price; final depends on complexity
Your drive won't power on or has shorted components
$450–$600
3-6 weeks
PCB issues: failed voltage regulators, dead PMICs, shorted capacitors
May require a donor drive (additional cost)
Your drive is detected but shows the wrong name, wrong size, or no data
$600–$900
3-6 weeks
Firmware corruption: ROM, modules, or system files corrupted
Price depends on extent of bad areas in NAND
Your drive's circuit board is severely damaged and requires NAND chip transplant to a donor PCB
$1,200–$1,500
4-8 weeks
NAND swap onto donor PCB. Precision microsoldering and BGA rework required
50% deposit required; donor drive cost additional
50% deposit required
Our "no data, no fee" policy applies to hardware recovery. We do not bill for unsuccessful physical repairs. If we replace a hard drive read/write head assembly or repair a liquid-damaged logic board to a bootable state, the hardware repair is complete and standard rates apply. If data remains inaccessible due to user-configured software locks, a forgotten passcode, or a remote wipe command, the physical repair is still billable. We cannot bypass user encryption or activation locks.
No data, no fee. Free evaluation and firm quote before any paid work. Full guarantee details. NAND swap requires a 50% deposit because donor parts are consumed in the attempt.
Rush fee: +$100 rush fee to move to the front of the queue.
Donor drives: A donor drive is a matching SSD used for its circuit board. Typical donor cost: $40–$100 for common models, $150–$300 for discontinued or rare controllers.
Target drive: The destination drive we copy recovered data onto. You can supply your own or we provide one at cost plus a small markup. All prices are plus applicable tax.
No Data, No Charge: If we cannot recover your Time Machine backup data, you pay nothing. Free evaluation with no obligation. Read the full guarantee.
Our Austin lab operates on a transparency-first model. We use industry-standard recovery tools, including PC-3000 and DeepSpar, combined with strict environmental controls to make sure your hard drive is handled safely and properly. This approach allows us to serve clients nationwide with consistent technical standards.
Open-drive work is performed in a ULPA-filtered laminar-flow bench, validated to 0.02 µm particle count, verified using TSI P-Trak instrumentation.
Serving clients nationwide via mail-in service since 2008. Our lead engineer holds PC-3000 and HEX Akademia certifications for hard drive firmware repair and mechanical recovery.
Our repair work has been covered by The Wall Street Journal and Business Insider, with CBC News reporting on our pricing transparency. Louis Rossmann has testified in Right to Repair hearings in multiple states and founded the Repair Preservation Group.
Our "No Data, No Charge" policy means we assume the risk of the recovery attempt, not the client.
Louis Rossmann
Louis Rossmann's well trained staff review our lab protocols to ensure technical accuracy and honest service. Since 2008, his focus has been on clear technical communication and accurate diagnostics rather than sales-driven explanations.
We believe in proving standards rather than just stating them. We use TSI P-Trak instrumentation to verify that clean-air benchmarks are met before any drive is opened.
See our clean bench validation data and particle test video
Info.plist or token metadata is damaged. Without a mounted volume, these tools see thousands of disjointed 8 MiB band files and cannot interpret them as a virtual disk. Lab recovery bypasses the mount step by concatenating band files in hexadecimal order and parsing the HFS+ or APFS file system directly from the reconstructed image.“Sent my hdd for data recovery, process was simple and I was able to pre-authorize an amount. They worked on my drive within 2 days of receiving it and the total cost was literally 1/10th of the amount of another service I got a quote from. Professional, quick, affordable. Nothing to complain about.”
“My satisfaction with Rossmann Repair Group goes beyond just 5 stars. I had a hard drive die some time ago, but I had no idea where I could send it knowing it would be safe, or there being a chance I'd be ripped off.”
“Had a raid 0 array (windows storage pool) (failed 2tb Seagate, and a working 1tb wd blue) recovered last year, it was much cheaper than the $1500 to $3500 Canadian dollars i was quoted by a Canadian data recovery service. the price while expensive was a comparatively reasonable $900USD (about $1100 CAD at the time).”
“Walked in with my wife's dead hard drive, walked out 20 minutes later with it fixed. They were friendly, professional, did the work in a snap, and saved me the hefty repair prices for other (mail in) hard drive recovery services!”
iMac, MacBook, Mac Mini, and Mac Pro data recovery
WD Passport, Seagate Backup Plus, LaCie recovery
APFS container superblock and snapshot corruption
Full HDD recovery service overview
Synology, QNAP, and network storage recovery
SSD TRIM behavior explained
CoreStorage and APFS Fusion Drive data recovery
We assess every drive at no cost. If we recover your backup data, you pay the quoted price. If we cannot recover it, you pay nothing.