Portable drives · job record · CDF-2025-0625
Boot Screen Sees It; Windows Freezes.
Nine years of a drainage contractor’s paperwork sat on one drive in Merthyr Tydfil — invoices, VAT workings, scanned receipts — with an accountant ringing every week about a year-end shut inside it. The boot screen picks it up, no bother
, he said. Then Windows starts, and the lot stops dead until I pull the lead out
.
Does that match yours? Call us.
0800 6890668
Why that happens.
Neither is lying; they are after different things. The BIOS asks for identification and stops there — a model, a capacity, a few parameters — and a disk that still spins and can talk to its own controller will supply that much. Windows wants the rest of it — the partition table, the filesystem metadata, and one sector after another back within a timeout counted in fractions of a second. Hand them over late and it walks away. Clear the first hurdle, fall at the second, and the drive has failed at the only work that matters. Two causes usually sit behind it: firmware that gives out the moment anything asks for user data, or a surface so tired that reads keep overrunning the window they are given.
What we used on this one.
Every step, in order →| The tools | What it did here | Why it helps |
|---|---|---|
| ACE Lab PC-3000 Express | Answered the question everything else hangs on: bad firmware or worn surface | Opens the maker's service commands, which a plain ATA link will not pass |
| PC-3000 Data Extractor | Copied the disk at whatever speed it could hold, with no deadline on it | Imaging driven from inside the drive's own firmware, by the PC-3000 |
| R-Studio Technician | Reassembled the NTFS volume from the completed image | Reads nearly every file system, and rebuilds arrays you can rely on |
How it went.
Settle that before the disk is touched again
The firmware was sound. Its service area was intact and every module came back from where it belonged. The failure was in the reading: sectors did arrive, but several seconds apart and one at a time. That accounts for the whole symptom, because the wait Windows allows a drive is a fraction of a second, and then it gives up.
Image it with no clock on it at all
An operating system will not wait. A bench imager will, and most of the difference lives there. While the disk goes on answering, the imager sticks with it. Timeouts were opened wide, stalls met with measured resets, and the rate allowed to sink wherever the surface had gone thin. Days later it finished, and it finished whole.
Everything after that is on the copy
The partition and NTFS structures were lifted off the completed image, and the volume was rebuilt from them. What had been refused for weeks opened immediately — ledgers, invoices, receipts.
Signing it off.
A single worn band kept its sectors to the last, and a handful of scanned receipts stayed with them. That was the whole of the loss. Every invoice came up, every VAT workbook came up, and the lot travelled back to Merthyr on fresh media.
Pages people often read next.
Filed under Pocket-size drives as well.
Is that what yours is doing?
Power it down, get it to us, and hold off on any decision until the diagnosis says what can still be read.