Case record · Logical & corruption · SDR-2025-0311
A Cyclic Redundancy Check, and My Life's Work.
The Toshiba desktop hard drive died while in use. It vanished from File Explorer
, and in Disk Management every attempt returned the same cyclic redundancy check
message. He had run Windows error-checking twice before contacting us. His summary needed no translation, everything I have ever drawn is on there
, and he had no way of knowing whether the fault lay in the disk or the software.
Seeing the same thing yourself?
0800 6890668
The translation.
A CRC error means the data got through and then failed the checksum travelling with it: the drive produced something it could not stand behind. Two types of fault produce a CRC error. One is a broken file system returning garbage from perfectly good sectors; the other is a drive surface that has started to fail. It is important to tell them apart, because the second gets worse with every retry, and Windows, left alone, will keep retrying until something gives.
Kit used on this job.
What happens in a case →| Which platform | Its role in this case | Why we use it |
|---|---|---|
| DeepSpar Disk Imager 4 | Read the disk with the retry count held down, logging weak sectors instead of battling them | Head-map-driven imaging, with per-head timeouts, resets and power-cycle control |
| R-Studio Technician | Rebuilt the NTFS structures once the image was complete | Wide filesystem support, with RAID rebuilds you can trust |
| ACE Lab PC-3000 Express | Checked SMART and the defect list at firmware level before a single imaging pass | Talks to drives using maker-specific commands beyond the ordinary ATA instruction set |
In the lab.
Work out which of the two faults this is
Before we even tried to read anything off this disk we did a "firmware" check: SMART counters, grown defect list, reallocation history. The results were clear, with reallocations rising and pending sectors waiting, and indicated that this was hardware wearing out as opposed to a file system that had gone haywire. So, therefore, the proper responses to these two types of problems are polar opposites of one another.
One gentle pass, with the retries held down
When imaging the drive, we employed a short timeout for how long to wait before moving to another area and limited the number of attempts in each region. We chose to log and skip regions that did not complete, rather than continuing to "pound" them; once the imaging was completed, we returned to those problematic areas with a new approach (angle). The logic is simple: on a surface that is breaking down, the fiftieth attempt at a bad sector kills the drive far more often than it recovers the sector.
Mend the filesystem where mistakes cost nothing
With the image safe all of these tasks were done on it, not the drive. The master file table was bad over the failing area of the disk and in two rounds of Windows error checking parts of it had been deleted. We rebuilt the records that survived and created a map of the truly unreadable areas so he could get an exact account of what did not survive.
The result.
Nearly everything was recovered from the image: all of the drawings, all of the surveys and a written list of the few files that did not survive. Most of those had been cut short by the error checking, not by the disk. Everything was compared to his priority folders before any money changed hands.
Similar cases on the index.
Other cases in Logical & corruption.
Does this sound like your own drive?
As always, the rule holds as in every case above: turn it off first, and let a free diagnosis come before any decision.