Bench notes · portable drives · MHD-2025-6625
Listed at Boot, Frozen Under Windows.
The accountant kept chasing a year-end that was shut inside a Backup Plus in Staines-upon-Thames, where a drainage contractor had nine years of invoicing, VAT workings and scanned receipts on the one drive. The boot screen lists it every single time
, he said; then the desktop appears and the whole machine locks up until I pull the cable out
.
Much the same fault? Call us.
0800 6890668
In everyday terms.
The two are asking for entirely different things. A BIOS wants an identity — model, capacity, a handful of parameters — and any drive that spins up and answers its own controller can supply one. An operating system wants partition tables, filesystem metadata and thousands of sectors returned inside a short timeout, and it abandons the attempt when they arrive late. A disk that clears the first hurdle and falls at the second is failing at real work, and there are two usual explanations: firmware that collapses once user data is requested, or a surface worn far enough that reads outlast any timeout.
What the bench used here.
How a job is handled →| Tool | Why we used it | What it brings |
|---|---|---|
| ACE Lab PC-3000 Express | Answered the question everything else depends on: firmware, or a worn surface | Reaches the vendor-specific commands that ordinary ATA has no way of issuing |
| PC-3000 Data Extractor | Imaged the disk at the pace it could manage, with no timeout imposed | The PC-3000's imaging module, working under firmware-level control |
| R-Studio Technician | Reconstructed the NTFS volume from the completed image | Its file-system coverage is wide and its array rebuilds hold up |
The lab work.
Settle firmware or surface before either is disturbed
Firmware came back sound: the service area was intact and every module present and readable. The reads were the problem. They did finish, but slowly, with single sectors taking several seconds apiece. That alone accounts for the symptom, since Windows allows a fraction of a second before it stops waiting.
Give the imaging as long as it wants
Bench imaging can afford to wait in a way that an operating system cannot. Provided the disk co-operates, it will stay with the job however long that takes. Timeouts were widened, stalls answered with controlled resets, and throughput left to fall wherever the surface had thinned. The copy ran for days and finished complete.
Open the image, not the drive
Partition and NTFS structures were lifted from the completed image and the volume assembled again from them. Material the drive had refused for weeks came off the copy at once: ledgers, invoices, receipts.
How the job closed.
A single worn band never gave up its sectors, taking a few scanned receipts with it; that is the whole of the loss. Not one invoice or VAT workbook refused to open, and all of it travelled back to Staines-upon-Thames on new media.
More of the jobs we've closed.
Filed under Portable drives too.
Does any of that match your case?
Nothing needs deciding until the diagnosis is back: switch the device off, send it in, and let the findings settle it.