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

Recovery Software vs. Hardware Recovery

DMDE Alternative for Hardware-Level Drive Failure

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

DMDE is one of the best logical recovery tools available. Its partition reconstruction engine, hex editor, and virtual RAID builder make it a first-choice tool for IT professionals dealing with corrupted file systems, deleted partitions, and formatted volumes on physically healthy drives. With licenses starting at $20 (Express) or $95 (Professional), it delivers capabilities that competitors charge several times more for. If your drive is detected by your operating system with its correct model and capacity, and DMDE can complete a scan, use it. But if DMDE is frozen on LBA 0, your recovered files are zero-filled, or the drive is clicking, not spinning, or dropping off the bus mid-scan, the problem is hardware. No software operating through the OS storage stack can bypass broken read/write heads, a locked-up SSD controller, or corrupted drive firmware.

When DMDE Is the Right Tool

DMDE operates at the sector level, reading raw disk data through the operating system's ATA or NVMe driver. It reconstructs partition tables from backup copies, rebuilds MFT entries, and carves files by signature from unallocated space. This approach works when the drive hardware is functional:

  • The drive spins up normally and is detected in BIOS/UEFI with its correct model number and full capacity
  • The drive appears in Disk Management or lsblk with its expected size, even if no volumes mount
  • You need to recover deleted files, a formatted partition, or a corrupted file system on a drive that responds to reads at normal speed
  • The drive produces no unusual sounds (clicking, beeping, grinding) and does not disconnect during extended reads

In these scenarios, DMDE, R-Studio, PhotoRec, and similar tools are appropriate. DMDE's partition search is particularly strong for cases where the MBR or GPT has been overwritten but the file system structures remain intact deeper on the disk. For a free method that handles the same logical recovery scenarios, our ddrescue guide covers sector-level cloning with open-source tools.

Why DMDE Freezes on LBA 0 and Early Sectors

When DMDE's partition search hangs at "Partition searching... #0 LBA" for hours on a drive that should scan at 100+ MB/s, DMDE is not malfunctioning. The drive hardware is failing to respond to standard read commands. Here is what is happening at the hardware layer:

SATA Command Timeouts and BSY State

When a hard drive's read/write heads encounter unreadable sectors, the drive's firmware retries each read multiple times internally before reporting an error to the host. During those retries, the drive holds the SATA bus in BSY (Busy) state. The OS storage driver waits for the drive to release BSY. DMDE waits for the OS. This chain means a single bad sector can stall DMDE for 7-30 seconds depending on the drive firmware's retry configuration. On a drive with thousands of weak sectors, those delays compound into hours or days of apparent freeze.

Degraded Read/Write Heads

A head assembly with degraded magnetic transducers can still read some sectors but fails on others. The drive firmware retries failed reads by repositioning the head and re-attempting, which produces the characteristic clicking sound. Each retry cycle forces the damaged head across the platter surface. DMDE's partition search reads sequentially from the start of the disk, which means it hits the drive's Service Area (where firmware modules and translator tables live) first. If the SA sectors are on a degraded head, DMDE cannot even read the partition table because the drive cannot deliver the first few hundred sectors.

USB Bridge Controller Disconnects

If you are running DMDE through a USB enclosure, the bridge IC (JMicron JMS578, ASMedia ASM1153E, and similar chips) imposes its own timeout. When the drive does not respond within the bridge chip's programmed threshold (often just a few seconds), the bridge resets the USB connection. DMDE sees the device disappear. Some bridge chips also force a 4096-byte logical sector size on drives formatted with 512-byte sectors (the "4Kn vs 512e" translation problem), which can cause DMDE to misalign its MBR and partition table parsing. Connect the drive via direct SATA before concluding that DMDE cannot read it.

SMR Translator Corruption

Modern consumer HDDs use Shingled Magnetic Recording (SMR), where data tracks overlap. SMR drives maintain a secondary translator that maps logical block addresses to physical band locations. When this translator corrupts, the drive may report its full capacity to the OS but return garbage or zeros for most LBA ranges. DMDE will scan the drive and find no recognizable file system structures because the physical-to-logical mapping is broken at the firmware level. Rebuilding an SMR translator requires direct firmware manipulation via PC-3000.

If DMDE has been scanning for more than 30 minutes with less than 1% progress, stop the scan and power down the drive. Continued reads on degraded heads can score the platter surface. The instinct to let the scan finish is understandable, but a drive that takes hours to read megabytes is destroying itself.

Why DMDE Recovers 0-Byte Files from SSDs

DMDE users frequently report reconstructing an entire directory tree from an SSD, only to find every recovered file is 0 bytes, opens as a black image, or plays as silent audio. This is not a DMDE limitation. It is TRIM doing what it was designed to do.

When you delete a file on a modern SSD, the operating system sends a TRIM command notifying the controller that those NAND flash blocks are no longer needed. The controller erases them during its garbage collection cycle so future writes are faster. DMDE recovers the file system metadata (the MFT entry that says "report.docx existed at clusters 40000-40500") because the MFT is stored separately. But when DMDE follows that pointer to read the actual file data, the NAND blocks contain zeros. The metadata survived; the data did not.

You can verify this yourself: open a recovered file in DMDE's hex editor. If the content area is entirely 00 00 00 00 repeating, TRIM has already run. No software, including DMDE, R-Studio, or any commercial tool, can recover data that has been electrically erased at the NAND cell level.

TRIM is enabled by default on Windows 7 and later, on Apple OEM SSDs in macOS (with manual trimforce support for third-party drives added in macOS 10.10.4), and on Linux kernel 3.8+ with fstrim or continuous TRIM. If you deleted files on an SSD and more than a few seconds passed before you realized, TRIM has likely already run on those blocks.

SSD Controller Failures DMDE Cannot Reach

Some SSD failures leave the NAND data intact but make the controller stop communicating with the host. DMDE operates through the OS storage driver. If the controller does not enumerate on the bus, DMDE sees no device to scan.

Phison S11: SATAFIRM S11 Lockup

Phison S11-based SSDs (common in budget Kingston, PNY, and Patriot drives) can enter a firmware lockup where the host system identifies the drive as "SATAFIRM S11" with 0 bytes capacity. The drive is present on SATA but returning invalid identification data. DMDE will either not see the device or see a 0-byte disk with nothing to scan. PC-3000 SSD sends vendor-specific commands to push the controller out of this state and access the NAND contents directly.

NVMe Monolithic BGA Packages

Some modern NVMe SSDs, particularly in thin laptops and mobile devices, use monolithic Ball Grid Array (BGA) packages where the controller, DRAM, and NAND are integrated into a single chip. Standard M.2 NVMe drives use discrete components on a PCB, but in both cases, if the controller fails due to a power surge, the drive stops enumerating on PCIe. The OS sees no device. There is no cable to swap, no enclosure to try. Recovery requires board-level diagnosis: checking power rails with an oscilloscope, replacing failed voltage regulators via microsoldering, or reading NAND chips directly with specialized equipment.

Apple T2 and M-series Encryption

On Macs with T2 chips (2018-2020 Intel Macs) and Apple Silicon (M1/M2/M3/M4), SSD storage is encrypted at the hardware level by the Secure Enclave. The encryption keys are bound to the specific security chip on that specific logic board. If the board dies, the NAND cannot be read by DMDE, PC-3000, or any external tool because the decryption keys died with the board. The only recovery path is repairing the original logic board at the component level to restore Secure Enclave functionality.

DMDE vs. Professional Lab Recovery

CapabilityDMDE ($20 License)Professional Lab (PC-3000)
Sector access methodOS-level ATA/NVMe driver. If the OS cannot enumerate the drive, DMDE cannot access itVendor-specific ATA commands (VSCs) sent directly to the drive firmware via PCIe hardware card, bypassing the OS
Bad sector handlingWaits for the OS timeout (7-30 seconds per sector). No control over drive-internal retry behaviorControls head positioning, read retries, and timeout thresholds at the millisecond level. Skips bad areas and returns later with adjusted parameters
Firmware repairNo. DMDE reads data but cannot modify drive firmware modules, translator tables, or head mapsReads and edits Service Area modules, rebuilds corrupted translator tables, and restores ROM data
Clicking/beeping driveCannot help. Running DMDE on a clicking drive forces damaged heads across the plattersHead swap in a 0.02µm ULPA-filtered clean bench, then PC-3000 imaging with head maps and adaptive parameters
SSD controller lockupCannot access. If the controller does not enumerate, no OS-level tool can reach the NANDPC-3000 SSD communicates with the controller through direct hardware commands to push it out of lockup states
RAID reconstructionVirtual RAID builder works on healthy, readable member imagesRecovers each physically failed member drive first, then reconstructs the array from recovered images
Pricing$20 (Express) / $95 (Professional). Free edition recovers up to 4,000 files per directoryHDD: $100-$2,000. SSD: $200-$1,500. Free evaluation. No data, no fee

How PC-3000 Bypasses What DMDE Cannot

The PC-3000 is a PCIe hardware card manufactured by ACE Lab. It sends vendor-specific ATA commands (VSCs) that a standard motherboard SATA controller cannot issue and that DMDE has no mechanism to send. This gives a technician direct access to drive internals that are invisible to the operating system:

  • Firmware modules in the Service Area, including the translator table that maps logical block addresses to physical platter locations. When this table corrupts, DMDE scans valid LBAs but gets zeros or garbage because the drive's own address mapping is broken
  • Head maps and defect lists that control which heads are active. PC-3000 can disable a damaged head and image only the platters served by healthy heads, then address the damaged head's platters separately with a donor head swap
  • Read timeout control at the hardware level. Instead of waiting 7-30 seconds per bad sector (which is why DMDE freezes), PC-3000 sets millisecond-level timeouts, skips problematic sectors instantly, and returns to them later with adjusted head positioning
  • Selective multi-pass imaging that reads accessible areas first, builds a map of problematic regions, and returns in subsequent passes with different read strategies. DMDE scans sequentially from LBA 0; PC-3000 prioritizes areas most likely to contain your data

How to Tell If DMDE Can Solve Your Problem

Before sending a drive for lab recovery, check these indicators. DMDE users tend to be technically competent; this checklist respects that by focusing on measurable symptoms rather than vague descriptions:

  1. Measure scan throughput. DMDE shows a progress counter. A healthy SATA HDD reads at 80-180 MB/s. If DMDE is averaging less than 1 MB/s, the drive is struggling to read sectors. This means hardware degradation, not a complex logical problem.
  2. Check SMART attributes. Before running DMDE, pull SMART data with smartctl -a /dev/sdX or CrystalDiskInfo. Reallocated Sector Count (ID 5), Current Pending Sector (ID 197), and Uncorrectable Sector Count (ID 198) above zero indicate media or head degradation. High values (hundreds or thousands) mean the drive is actively failing.
  3. Listen to the drive. Clicking, beeping, or rhythmic sweeping indicate mechanical head failure. Power the drive off. Do not run DMDE.
  4. Verify device enumeration. If the drive shows the wrong model name, 0 bytes capacity, or does not appear in BIOS at all, the firmware or controller has failed. DMDE requires a properly enumerated device.

DMDE Can Handle This

  • Drive detected with correct model and full capacity
  • SMART Reallocated Sector Count is zero or single digits
  • Scan throughput stays above 50 MB/s consistently
  • No unusual sounds from the drive enclosure

DMDE Cannot Help Here

  • Drive clicking, beeping, or not spinning up
  • SMART shows hundreds of reallocated or pending sectors
  • Scan throughput below 1 MB/s or frozen at 0%
  • Drive shows wrong model, 0 bytes, or drops off the bus

Hard Drive Recovery Pricing

We quote based on the fault, not the perceived value of your data. Evaluation is free. No data recovered means no charge.

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.

SSD Recovery Pricing

SSD recovery pricing depends on the type of failure, from file system repair through controller-level and board-level intervention.

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.

Frequently Asked Questions

DMDE found my partition but all files are 0 bytes. What happened?
On SSDs, this is a TRIM artifact. DMDE reconstructed the file system metadata (MFT entries, directory tree) from intact sectors, but the actual data blocks behind those pointers were erased by the SSD controller during garbage collection. When you open a recovered file in a hex editor and see only 00 00 00 00, the NAND flash cells holding that data were electrically zeroed by TRIM. This is not a DMDE bug. No software can recover data that has been physically erased at the flash cell level.
DMDE is stuck on 'Partition searching... #0 LBA' for hours. Is it still working?
If DMDE has been scanning LBA 0 or early sectors for more than 30 minutes on a drive that should scan at 100+ MB/s, the drive hardware is failing to respond to read commands. The drive controller is either stuck in a BSY (Busy) state due to firmware corruption or the read/write heads are degraded and timing out on every sector. DMDE is waiting for the OS storage stack to return data that the drive cannot deliver. Stop the scan and power down the drive. Continued reads on degraded heads can score the platter surface.
DMDE costs $20. Why would I pay for professional recovery?
DMDE starting at $20 (Express license) is one of the best values in logical recovery software. If your drive is physically healthy and DMDE can complete a scan, use it. Professional recovery addresses a different category of problem: physical hardware failure where the drive cannot respond to standard read commands. HDD recovery at our lab starts at $100 for simple copies and goes up to $2,000 for platter-level damage. SSD recovery starts at $200 and goes up to $1,500 for advanced board rebuilds. Free evaluation, no charge if we cannot recover data. The $20 software and the lab service solve different problems.
My drive disconnects every time DMDE starts scanning. Why?
USB enclosures use bridge controller ICs (commonly JMicron or ASMedia chips) that translate between USB and SATA protocols. These bridge chips have programmed timeout thresholds. When a drive sector takes longer than the bridge allows (often just a few seconds), the bridge resets the connection and the OS drops the device. DMDE sees the drive disappear mid-scan. This happens because the drive is struggling to read degraded sectors, not because of a USB cable or enclosure defect. Try connecting via direct SATA if possible. If the drive still hangs on SATA, the problem is hardware-level head or firmware degradation.
Can DMDE reconstruct my RAID array?
DMDE has a virtual RAID constructor that can reassemble logical RAID configurations when all member drives are healthy and readable. It works well for RAID 0/1/5 arrays where the controller failed but the individual drives are intact. If one or more member drives have physical damage (clicking, not spinning, firmware-locked), DMDE cannot image those drives. Each failed drive needs hardware-level recovery first, then the virtual RAID reconstruction can proceed on the recovered images. Attempting a virtual RAID build with a physically failing member drive will cause DMDE to hang on every bad sector of that member.

What Customers Say

4.9 across 1,837+ verified Google reviews
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.
Andrew Hansen
View on Google
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.
Kyle Hartley (crazybangles)
View on Google
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).
ChristopolisSeagate
View on Google
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!
Patrick Dughi
View on Google

DMDE found the partition but not the data?

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