Capacity and identity failure

A drive showing the wrong capacity is not empty—it may have failed to describe its data correctly.

A disk that reports zero bytes, a few megabytes, a generic model or a capacity far below its label may be detected electrically while firmware, service data, translation or the enclosure path fails to expose user sectors.

Start a recovery case Call 682-325-7712

Understand the symptom

The capacity reported to the host depends on firmware and translation—not just the platters.

WHY

What is happening

A hard drive identifies itself only after loading internal service information and translating physical media into logical sectors. Damage to firmware modules, heads that cannot read service areas, translator problems, host protected areas, bridge-board limits or electrical faults can produce an incorrect identity or size. Partition recovery is not the first step when the device itself reports the wrong capacity because software cannot address sectors the drive does not expose.

What you may see

Symptoms that change the recovery path.

0 bytes or no media

The host may see a controller response without access to the drive's expected user area.

Small diagnostic capacity

A fallback or incomplete initialization state can expose only a limited placeholder size.

Correct model, wrong size

Firmware translation, enclosure compatibility or device configuration may be inconsistent.

Capacity changes between boots

Intermittent firmware, head, power or bridge behavior indicates an unstable source.

Protect the source

Actions that can make the situation worse.

Initialization writes partition metadata

Creating GPT or MBR data does not restore missing device capacity and can overwrite useful evidence.

Firmware tools can reset state

Vendor and factory utilities are designed for supported working devices, not preservation of failed sources.

Long scans cannot read hidden sectors

Recovery software can only scan the address range the drive exposes and may stress weak hardware.

Do this now

Safe steps before evaluation.

Capture the exact identity

Record the model string, serial, reported capacity, interface and error without accepting write prompts.

Keep the original enclosure

Some external bridges affect sector size, capacity reporting or encryption.

Stop if detection changes

Intermittent size, clicking, resets or slowness are reasons to leave the device powered off.

Document prior tools

List any firmware updater, partition utility, board swap, enclosure change or repair already attempted.

NEPFOSYS process

How a data-first evaluation proceeds.

Identity-path review

The model, firmware response, enclosure, board and physical symptoms are evaluated together.

Restore controlled sector access

Any supported path focuses on stable acquisition rather than making the drive reusable.

Reconstruct from acquired sectors

Partitions, file systems and requested files are analyzed only after the best available image exists.

A clear next step

Preserve the original device before another repair or recovery attempt.

Start a case with the exact symptoms, incident timeline, prior attempts, encryption details, and the files that matter most. NEPFOSYS will route the case to the appropriate DFW intake or nationwide mail-in path.

Start with a case review

Questions, answered

What customers ask before starting.

Does 0 bytes mean the files were erased?

No. It usually means the host is not receiving normal capacity or media access. The physical data may still exist, but the device must expose stable sectors before logical recovery.

Can partition software restore the correct size?

Not when the device itself reports the wrong capacity. Partition tools operate above the hardware and firmware layer and may write new metadata.

Should I remove an external drive from its enclosure?

Keep the original enclosure and bridge with the case. Some models use bridge encryption, sector translation or capacity behavior that matters during recovery.

DFW local · Nationwide mail-in

Protect the device. Start with the facts.

Start my recovery case