Case file · Desktop externals · BDR-2025-0921
It Slows the Whole Computer to a Crawl.
Plugging the drive into the computer became an event: the computer slows right down and almost crashes
when the drive is put in. The owner did some investigating: she found recovery software could see the files. This led her to a very specific and correct conclusion: probably the hdd failing
. Using a new cable didn't make any difference. Family photos were stored on the drive.
Same symptoms on your desk?
01273 964902
The decode.
When one device brings another to its knees, it is monopolising the storage bus with read operations that barely complete. When an OS sends a read request, it will wait until the read operation completes or times out, issue a retry, wait again, etc., all while queuing up every other disk operation. The good news hidden within the bad news was that recovery software could enumerate the files: the directory structures were readable, therefore the photos existed, and the problem was one of reliability rather than existence.
Equipment on this case.
How a job runs here →| The system | What it did on the day | Why this tool |
|---|---|---|
| DeepSpar Disk Imager 4 | Imaged with a hard retry ceiling, so failing sectors couldn't stall the whole pass | Head-map-aware imaging with per-head timeout, reset and power-cycle control |
| ACE Lab PC-3000 Express | Read reallocation and pending-sector data to target the read strategy | Speaks the vendor-specific commands that sit outside the standard ATA set |
| UFS Explorer Professional Recovery | Rebuilt the volume and recovered the photo libraries with folders intact | Stronger than most on the awkward filesystems — APFS, ReFS, XFS, ZFS, Btrfs |
At the bench.
Stop the browsing sessions immediately
Each time she tried to take an exploratory look at that drive, she was putting a small strain on a failing mechanism, and because the file directories were able to be enumerated, she felt like continuing to explore. Firmware-level checks indicated reallocation was far along and pending sectors were building up. This ended any debate.
Cap the retries and let the drive skip its own bad ground
The imaging pass proceeded with strict timeouts and a retry limit. While Windows would continue to wait indefinitely on each problematic sector, the imager would log the problematic sector(s), move forward with acquiring the remaining healthy data, and return later to those problematic areas using a different approach.
Recover the photos and verify them visually
The volume was rebuilt from the completed image and the photo libraries recovered with their folder structure. Images were spot-checked by opening them, because a JPEG can be present, correctly sized and still half grey.
Where it ended up.
The family photos came off the image effectively complete and were verified before sign-off. The computer, unburdened of a drive it had been waiting on, remembered how to be fast.
Related on the index.
More from Desktop externals.
Recognise your own drive in this story?
Same rule as every previous case: shut it down first, and let our diagnostics run, free of charge, before making any decisions.