What it is
A drive has two parts: the area that holds your files, and a system area the drive uses to run itself. The system area keeps the drive's own settings, its map of worn-out spots, and the instructions it needs to start. If any of that is missing or corrupt, the drive can't present your data to a computer.
Firmware faults happen on hard drives and SSDs alike. On an SSD, the controller often drops into a safe mode and reports itself with a placeholder name and a capacity of a few megabytes.
What you might notice
- Detected as 0 GB, the wrong capacity or the wrong model name.
- An SSD showing a name like SATAFIRM S11.
- The computer hangs when the drive is plugged in.
- Detected one moment, gone the next.
Why recovery software can't help
Recovery software asks the drive for data. A drive with broken firmware can't answer properly, so the software either sees nothing or makes the drive work harder. Firmware updates and reset tools found online are worse: they can overwrite the very information the drive needs.
Firmware problems are repaired with specialized tools that talk to the drive below the level your computer uses, never with downloaded software.
What we do about it
We back up the drive's own firmware first, so nothing is lost if a repair doesn't go as planned. Then the damaged parts are repaired, or rebuilt from a matching source, until the drive can start and be read.
Firmware trouble often travels with worn surfaces. When a drive has run out of spare space for its bad spots, it can't hide them anymore and starts failing reads. In that case we image the drive over several careful passes, skipping damaged areas first and coming back to them. For some SSDs that crash every time they're read, we write a routine to stop the crash long enough to copy the drive.
What's possible, and what isn't
When firmware is the only problem, the files are normally untouched and the outlook is good. If the drive was also encrypted with BitLocker or FileVault, you'll still need the key or password; repairing the firmware doesn't remove the encryption.
If there's physical damage underneath the firmware fault, the evaluation will find it and the quote will say so.