Case file · Logical & corruption · BDR-2025-0311
Cyclic Redundancy Check on My Life's Work.
Mid-use, a Toshiba external simply became corrupt
: gone from File Explorer, and Disk Management answering every approach with a cyclic redundancy check error
. The owner's summary needed no translation — life's work is on that hard drive
— and he honestly didn't know whether the fault was physical or software.
Same symptoms on your desk?
01273 964902
The decode.
A CRC error means data arrived but failed its own checksum — the drive handed over something it could not vouch for. Two candidates fit that description: a damaged filesystem returning nonsense from intact sectors, or a surface beginning to fail. The distinction matters enormously, because the second candidate gets worse every time you retry. Windows, left alone, will retry indefinitely.
Equipment on this case.
How a case runs →| Platform | What it did here | Why this tool |
|---|---|---|
| DeepSpar Disk Imager 4 | Read the drive with retries capped, mapping weak sectors instead of fighting them | Head-map-aware imaging with per-head timeout, reset and power-cycle control |
| R-Studio Technician | Rebuilt the NTFS structures from the completed image | Broad filesystem coverage and dependable RAID reconstruction |
| ACE Lab PC-3000 Express | Confirmed SMART and defect-list state at firmware level before imaging began | Speaks the vendor-specific commands that sit outside the standard ATA set |
On the bench.
Establish which fault this actually is
Before any read attempt, the drive was interrogated at firmware level — SMART attributes, the grown defect list, reallocation history. The picture was unambiguous: reallocated sectors climbing, pending sectors present. This was hardware degrading, not a filesystem confused, and the treatment for the two is opposite.
Image once, gently, with the retries capped
The drive went onto the imager with tight timeouts and a hard retry ceiling. Failing regions were logged and skipped rather than hammered, then revisited at the end with a different read strategy. The point of a retry limit is simple: on a degrading surface, the fiftieth attempt at a bad sector is more likely to kill the drive than to succeed.
Repair the filesystem where mistakes are free
With a complete image secured, all repair work happened on the copy. The NTFS master file table had taken damage across the failing region; surviving records were rebuilt and the small number of genuinely unreadable areas mapped so we could tell the owner precisely what was affected rather than guessing.
The outcome.
The life's work came off the image effectively whole — a handful of sectors gone, no file of consequence among them, and a written list of exactly which regions had been lost. Verified against his priority folders before a penny changed hands.
Related on the index.
More from Logical & corruption.
Recognise your own drive in this story?
Same rule as every case above: power it down, and let the diagnosis be free before any decision has to be.