Skip to main contentSkip to navigation
Rossmann Repair Group logo - data recovery and MacBook repair

Open-Source Partition Repair vs. Hardware Recovery

TestDisk Alternative for Failed Partition Recovery

Louis Rossmann
Written by
Louis Rossmann
Founder & Chief Technician
Updated March 2026
10 min read

TestDisk is a free, open-source partition recovery tool maintained by Christophe Grenier at CGSecurity. It analyzes partition tables, repairs boot sectors, and rebuilds Master File Table (MFT) entries to restore access to lost volumes. On a physically healthy hard drive with logical corruption, TestDisk is one of the most capable free tools available. If your partition table was overwritten by an accidental disk initialization or a failed OS install, TestDisk is a legitimate first step.

But if TestDisk hangs, reports the wrong drive capacity, finds no partitions on a drive that was full of data, or the drive is clicking or not spinning, the problem is below the partition table. TestDisk operates at the filesystem layer. It cannot fix failed read/write heads, corrupted drive firmware, or SSD controllers locked in a fault state. Those failures require hardware-level access through PC-3000.

When TestDisk Is the Right Tool

TestDisk reads the raw sectors where partition table entries and boot sector records are stored. It searches for known filesystem signatures (NTFS, FAT32, ext2/3/4, HFS+, exFAT) and can reconstruct partition boundaries that were overwritten or corrupted. The tool works when:

  • The drive is detected in BIOS/UEFI with its correct model number and full capacity. If the drive reports 0 bytes or a fraction of its real size, the firmware is damaged and partition table repair will not help
  • The partition table was overwritten by an accidental disk initialization, a failed OS installation, or a repartitioning error. The data is still on the platters; the map that points to it was destroyed
  • A boot sector is corrupted but the backup copy is intact. NTFS stores a backup at the end of the volume; FAT32 keeps one at sector 6. TestDisk can write a corrected primary from the backup
  • The drive makes no abnormal sounds when powered on. No clicking, beeping, grinding, or repetitive ticking
  • The drive is a mechanical hard drive (HDD), not an SSD where TRIM may have erased the data at the flash level

In these scenarios, TestDisk, its companion tool PhotoRec, R-Studio, and similar software are appropriate first steps. If you are working with a degrading drive that still functions but has growing bad sectors, clone it first with GNU ddrescue before running any partition repair.

Where TestDisk Cannot Help

TestDisk sends standard ATA read commands through the operating system. If the drive hardware cannot service those commands, the partition table data is inaccessible regardless of what software runs on top.

Firmware Corruption (Wrong Capacity, BSY State)

A hard drive's firmware lives in the Service Area (SA), a reserved zone on the platters. The SA contains modules that define the drive's capacity, defect maps, and translator tables. If these modules become corrupted, the drive may spin up but report 0 bytes, show an incorrect model string, or enter a BSY (busy) state where it does not respond to any commands. TestDisk needs the drive to be enumerated by the OS with its correct geometry before it can scan for partitions. When the firmware is broken, the drive never reaches that point. PC-3000 sends vendor-specific ATA commands directly to the controller to read, patch, and rewrite SA firmware modules without going through the OS.

Physical Bad Sectors and Head Degradation

If the partition table is stored on sectors with physical media damage, TestDisk will hang waiting for the drive to return data that the heads cannot read. The drive's firmware retries each failed read internally (multiple times per sector) before reporting an error. During retries, TestDisk freezes with no progress indicator. Running TestDisk on a drive with degraded heads forces those heads to scan across damaged platter surfaces, which risks scoring the magnetic coating and extending the damage. PC-3000 disables the drive's internal retry logic, sets strict timeouts, and images accessible sectors first while mapping bad regions for later passes with adjusted head parameters.

SMR Translator Corruption

Many consumer drives 2TB and larger from Seagate, Western Digital, and Toshiba use Shingled Magnetic Recording (SMR). SMR drives maintain an internal translator that maps logical block addresses (LBAs) to physical locations on overlapping write tracks. If this translator becomes corrupted, the drive may report its correct capacity but return zeros or stale data across large address ranges. TestDisk will scan these regions, find no valid partition signatures, and report that no partitions exist, even though the data is still on the platters. Rebuilding an SMR translator requires direct firmware access through PC-3000.

Drive Not Spinning or Not Detected

If a hard drive does not spin at all when powered on (motor seizure) or spins but is not detected by the BIOS, no software can reach it. TestDisk requires the OS to enumerate the drive as a block device before it can scan anything. A dead or undetected drive needs hardware intervention: motor swap for seized spindles, PCB component repair for a dead controller board (with ROM chip transfer), or head swap for heads stuck on the platter surface (stiction).

If TestDisk hangs indefinitely, reports wrong capacity, or the drive makes abnormal sounds: stop the tool and power down the drive. Each read attempt on failing hardware worsens the physical damage. A drive in this state needs hardware-level recovery, not partition table repair.

Dangerous Advice to Avoid

Forums and AI chatbots routinely give advice that sounds reasonable but causes permanent data loss on physically failing drives. If your drive has any symptoms of hardware failure (clicking, wrong capacity, dropped connections, scans running for days), do not follow any of these suggestions.

"Run chkdsk before TestDisk" chkdsk enforces filesystem consistency by deleting orphan file records, truncating cross-linked files, and overwriting metadata. On a degrading drive, this destroys the very data fragments that a professional lab would use to reconstruct files. chkdsk is a repair tool for a healthy filesystem, not a recovery tool for a failing drive.

"Use Rebuild BS on any drive" TestDisk's Rebuild BS (boot sector) performs in-place writes to the drive. On a healthy drive with a corrupted boot sector, this is fine. On a drive with degraded heads or growing bad sectors, those writes force the failing heads to perform write operations, which generate more heat and physical stress than reads. One bad write pass can push a marginal head into full contact with the platter surface.

"Try another recovery tool if TestDisk failed" If TestDisk failed because the drive is physically degrading, running Disk Drill, EaseUS, R-Studio, or any other software will produce the same result: the same read errors, the same freezes, and more stress on the same failing heads. Different software cannot bypass hardware faults. The right next step is to evaluate whether the failure is hardware or software.

TestDisk on SSDs: Partition Repair Works, Data May Not

TestDisk can repair partition tables and boot sectors on SSDs if the SSD controller is operating normally. The tool reads the same LBA sectors regardless of whether the underlying media is magnetic or flash-based. The partition table structure is identical on HDDs and SSDs.

The problem is what happens after the partition table is fixed. On a mechanical hard drive, deleted data stays on the platters until another file overwrites those sectors. On an SSD with TRIM enabled, the controller unmaps the deleted sectors within seconds of the OS sending a delete or format command, returning zeros to any software scan. The NAND cells are then permanently erased during background garbage collection. TestDisk can restore the partition map, but the data those entries pointed to is already inaccessible and will be physically erased by the controller.

TRIM is enabled by default on Windows 7 and later. macOS 10.10.4 and later enables TRIM by default for Apple-branded SSDs; third-party drives require manual activation via the trimforce command. Most modern Linux distributions run periodic TRIM via a scheduled fstrim task rather than continuous inline TRIM. If the SSD was connected via a USB enclosure that does not pass TRIM commands, the data may still exist on the NAND.

For SSDs locked in a fault state (SATAFIRM S11 mode, SM2258XT 100% active time bug, Phison E12 sudden death) where the drive is detected but completely unresponsive, the data is still on the NAND but no software can access it. These require SSD-specific firmware recovery with PC-3000 SSD to push the controller past its fault state or, in some cases, NAND chip removal and direct reading.

How Hardware Recovery Bypasses TestDisk Limitations

TestDisk operates at the logical layer: it reads what the drive's firmware exposes through the OS. PC-3000 operates at the hardware layer: it communicates directly with the drive's controller using vendor-specific commands that bypass the OS entirely. This distinction matters when the drive's firmware is the source of the problem.

Firmware-Level Partition Access

When firmware corruption prevents normal drive initialization, PC-3000 can inject a loader program directly into the drive controller's RAM using vendor-specific commands, bringing the drive online in a diagnostic mode without relying on the corrupted Service Area. For more severe cases where the controller cannot accept a loader, a physical PCB hot swap transfers an initialized donor board to the patient drive's head and disk assembly. Either technique makes the platters accessible so that every sector, including the partition table, MFT, and file data, can be imaged to a target drive.

Controlled Imaging Around Bad Sectors

PC-3000's Data Extractor module images the drive in multiple passes. The first pass reads only sectors that respond within a strict timeout (often 500ms per sector). Sectors that fail are logged and skipped. Subsequent passes retry failed sectors with adjusted parameters: different head offsets, lower read speeds, or targeted single-sector reads. This approach maximizes the percentage of recovered data while minimizing the time degraded heads spend actively scanning, which is the exact opposite of TestDisk's linear scan from sector 0 to the end.

Head Swap and Platter Imaging

If the read/write heads have failed entirely, no amount of partition repair will access the data. The heads must be physically replaced with a matched donor set from the same drive family and firmware revision. This is done in a 0.02 micron ULPA-filtered clean bench to prevent particulate contamination on exposed platters. After the swap, PC-3000 images the drive using head maps that prioritize the working heads and avoid regions where the original heads caused surface damage.

TestDisk Partition Repair vs. PC-3000 Lab Recovery

TestDisk and PC-3000 work at different layers of the storage stack. TestDisk operates above the drive's firmware: it reads the sectors the OS exposes and looks for filesystem structures. PC-3000 operates below the firmware: it communicates with the drive controller directly using vendor-specific hardware commands. One is not a replacement for the other; they solve different categories of failure.

Feature Comparison

CapabilityTestDisk (Partition Repair)Lab Recovery (PC-3000)
Lost or corrupted partition tableScans for partition signatures and rewrites the table. Works when sectors are readableDirect firmware access restores LBA mapping even when partition table sectors are physically damaged
Corrupted boot sector (NTFS/FAT32)Rebuilds from backup copy if backup is intactReads raw platter data below the filesystem layer; does not depend on backup boot sector
Physical bad sectors on the plattersHangs or crashes. Cannot bypass drive-level read errorsPC-3000 disables internal retries, controls head positioning, and images accessible sectors first
Firmware corruption (BSY state, wrong capacity)Cannot access drive. Relies on OS device enumerationVendor-specific ATA commands (VSCs) access and repair Service Area firmware modules
Failed or degraded read/write headsRunning TestDisk accelerates physical damage to plattersHead swap in 0.02 micron ULPA filtered clean bench, then targeted imaging with head maps
SMR translator corruptionReturns zeros or stale data. Cannot access the internal translation layerPC-3000 rebuilds the translator map from the persistent cache on the platters
SSD controller lockup or firmware hangDrive unresponsive to any OS-level commandsPC-3000 SSD sends controller-specific commands to clear the lockup or reads NAND chips directly
CostFree (GPL license)HDD: $100-$2,000. SSD: $200-$1,500. No data, no fee.

Pricing for Hardware-Level Recovery

TestDisk is free. Our hardware recovery starts at $100 for HDDs and $200 for SSDs. These solve different problems: TestDisk works when the drive is healthy and the partition table needs rebuilding. We handle cases where the hardware itself has failed or the firmware is corrupted. Evaluation is free and there is no charge if we cannot recover your data.

Service TierPriceDescription
Simple CopyLow complexity$100

Your drive works, you just need the data moved off it

Functional drive; data transfer to new media

Rush available: +$100

File System RecoveryLow complexityFrom $250

Your drive isn't recognized by your computer, but it's not making unusual sounds

File system corruption. Accessible with professional recovery software but not by the OS

Starting price; final depends on complexity

Firmware RepairMedium complexity – PC-3000 required$600–$900

Your drive is completely inaccessible. It may be detected but shows the wrong size or won't respond

Firmware corruption: ROM, modules, or translator tables corrupted; requires PC-3000 terminal access

Standard drives at lower end; high-density drives at higher end

Head SwapHigh complexity – clean bench surgery50% deposit$1,200–$1,500

Your drive is clicking, beeping, or won't spin. The internal read/write heads have failed

Head stack assembly failure. Transplanting heads from a matching donor drive on a clean bench

50% deposit required. Donor parts are consumed in the repair

Surface / Platter DamageHigh complexity – clean bench surgery50% deposit$2,000

Your drive was dropped, has visible damage, or a head crash scraped the platters

Platter scoring or contamination. Requires platter cleaning and head swap

50% deposit required. Donor parts are consumed in the repair. Most difficult recovery type.

Hardware Repair vs. Software Locks

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.

All tiers: Free evaluation and firm quote before any paid work. No data, no fee on simple copy, file system, and firmware tiers. Head swap and surface damage require a 50% deposit because donor parts are consumed in the attempt.

Target drive: The destination drive we copy recovered data onto. You can supply your own or we provide one at cost. For ultra-high-capacity drives (20TB and above), the target drive costs approximately $400+ due to the large media required. All prices are plus applicable tax.

Service TierPriceDescription
Simple CopyLow complexity$200

Your drive works, you just need the data moved off it

Functional drive; data transfer to new media

Rush available: +$100

File System RecoveryLow complexityFrom $250

Your drive isn't showing up, but it's not physically damaged

File system corruption. Visible to recovery software but not to OS

Starting price; final depends on complexity

Circuit Board RepairMedium complexity – PC-3000 required$600–$900

Your drive won't power on or has shorted components

PCB issues: failed voltage regulators, dead PMICs, shorted capacitors

May require a donor drive (additional cost)

Firmware RecoveryMedium complexity – PC-3000 required$900–$1,200

Your drive is detected but shows the wrong name, wrong size, or no data

Firmware corruption: ROM, modules, or system files corrupted

Price depends on extent of bad areas in NAND

Advanced Board RebuildHigh complexity – precision microsoldering and BGA rework$1,200–$1,500

Your drive's circuit board is severely damaged and requires advanced micro-soldering

Advanced component repair. Micro-soldering to revive native logic board or utilize specialized vendor protocols

50% deposit required upfront; donor drive cost additional

Hardware Repair vs. Software Locks

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.

All tiers: Free evaluation and firm quote before any paid work. No data, no fee on all tiers (advanced board rebuild requires a 50% deposit because donor parts are consumed in the attempt).

Target drive: The destination drive we copy recovered data onto. You can supply your own or we provide one at cost. All prices are plus applicable tax.

Data Recovery Standards & Verification

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.

Transparent History

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.

Media Coverage

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.

Aligned Incentives

Our "No Data, No Charge" policy means we assume the risk of the recovery attempt, not the client.

LR

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

Frequently Asked Questions

What is the difference between TestDisk and PhotoRec?
Both are free, open-source tools by Christophe Grenier (CGSecurity), often bundled in the same download. TestDisk is filesystem-aware: it scans for lost partition signatures, repairs boot sectors, and rebuilds the Master File Table to restore access through the original directory structure. PhotoRec ignores the filesystem entirely and carves raw data by scanning for known file headers (JPEG, ZIP, DOCX, etc.). TestDisk preserves filenames and folder paths when it works. PhotoRec outputs generically named files with no hierarchy. If TestDisk cannot find your partition, PhotoRec is the fallback for raw file extraction on a healthy drive.
Is it safe to run TestDisk on a clicking or beeping hard drive?
No. A clicking drive has failing or failed read/write heads. TestDisk scans every partition table sector and boot sector on the disk, which forces the degraded heads to sweep across platter surfaces. Each read attempt on failing heads risks scoring the magnetic coating and turning a partial failure into a total loss. If your drive clicks, beeps, or makes any repetitive mechanical sound, power it down immediately. Do not run TestDisk, PhotoRec, chkdsk, or any other software.
TestDisk shows my drive as 0 bytes or wrong capacity. What happened?
When a drive reports incorrect capacity, the problem is in the drive's firmware, not the partition table. The Service Area (SA) on the platters stores the firmware modules that tell the controller how many sectors to expose to the host. If SA modules are corrupted, the drive initializes with a wrong LBA count or enters a BSY (busy) state. TestDisk reads the partition table that sits on top of this LBA space; if the firmware reports the wrong capacity, the partition entries TestDisk finds will be meaningless. This requires PC-3000 firmware repair using vendor-specific ATA commands, not partition table editing.
Can TestDisk's 'Rebuild BS' option fix a corrupted boot sector?
On a physically healthy drive, yes. TestDisk can reconstruct an NTFS or FAT32 boot sector by reading the backup copy (NTFS stores a backup boot sector at the end of the volume; FAT32 keeps one at sector 6). If the backup is intact, TestDisk writes a corrected copy to sector 0 and the volume becomes mountable again. This fails when both the primary and backup boot sectors are corrupted (common after firmware glitches or partial overwrites), when the MFT itself is damaged beyond what the boot sector references, or when the sectors containing the boot record are physically unreadable due to bad sectors or head damage.
Does TestDisk work on SSDs?
TestDisk can repair partition tables and boot sectors on SSDs the same way it does on HDDs, provided the SSD controller is responding normally and the drive is detected at its correct capacity. The limitation is TRIM: if files were deleted on an SSD with TRIM enabled (default on Windows 7+ and macOS for Apple-branded SSDs), the controller unmaps those sectors and they return zeros to any software scan. The NAND cells are permanently erased during background garbage collection. TestDisk can find and repair the partition table, but the data those partitions pointed to is already inaccessible. For SSD controller lockups (SATAFIRM S11, SM2258XT hang states), the drive is unresponsive to any software commands and requires firmware-level intervention with PC-3000 SSD.
Why is TestDisk taking days or weeks to scan my drive?
A scan that runs for more than 24 hours on a modern drive is not normal. TestDisk is waiting for the drive to respond to read commands. Each time it hits a physically damaged sector, the drive's firmware retries internally (multiple times per sector) before returning an error. On large-capacity drives using Shingled Magnetic Recording (SMR), a corrupted translator can cause the drive to hang on entire address ranges. Stop the scan, power down the drive, and get a hardware evaluation. Letting TestDisk grind through weeks of read errors accelerates head degradation.

TestDisk could not find your partition?

Free evaluation, no data no fee. Ship your drive to our Austin lab and we diagnose the hardware fault before you owe anything.