Portable drives · bench file · BHD-2025-8625
The BIOS Finds It; Windows Locks Solid.
A drainage contractor in West Bromwich had nine years on one drive — invoices, VAT workings, scanned receipts — and an accountant ringing weekly about a year-end that was locked inside it. It shows up on the boot screen, every time
, he said. Then Windows loads, and the whole thing seizes until I unplug it
.
Sounds like yours? Give us a ring.
0800 6890668
What that means.
Neither is lying, because they are not asking the same question. The BIOS wants a name badge — model, capacity, a few parameters — and a drive that still spins and answers its own controller can produce that much. Windows wants far more: a partition table, filesystem metadata, and sector after sector returned inside a timeout measured in fractions of a second, and it walks away when they turn up late. Pass the first test and fail the second and the drive is failing at the only work that matters. Two things usually explain it: firmware that falls over the moment user data is asked for, or a surface worn to the point where every read runs past the clock.
What did the work here.
The order of the work →| Equipment | The job it did | What it adds |
|---|---|---|
| ACE Lab PC-3000 Express | Settled the one question the rest turns on: firmware fault or worn surface | Gets at the factory service commands that standard ATA cannot carry |
| PC-3000 Data Extractor | Copied the disk at whatever pace it could manage, with no clock imposed | Reads the disk from inside its firmware, using the PC-3000's imager |
| R-Studio Technician | Put the NTFS volume back together off the finished copy | Broad file-system support, with RAID rebuilds that can be trusted |
What we did.
Answer that before the disk is disturbed at all
The firmware checked out. Its service area was whole and every module read back where it should be. What failed was the reading itself: sectors did come, but several seconds each, one at a time. That is the whole symptom explained, because Windows gives a drive a fraction of a second before it decides nothing is coming.
Take the clock off the imaging entirely
An operating system cannot wait. A bench imager can, and that is most of the difference. So long as the disk keeps answering, the imager stays with it for as long as it takes. Timeouts were opened right up, stalls met with measured resets, and throughput left to sink wherever the surface had thinned. It ran for days and came out complete.
Work on the copy, never the disk
Partition and NTFS structures came off the finished copy, and the volume was put back together from those. What the drive had refused for weeks opened straight away: ledgers, invoices, receipts.
How it closed.
One worn band held on to its sectors to the end, and a handful of scanned receipts went with it. That was the entire loss. Every invoice opened, every VAT workbook opened, and the lot went back to West Bromwich on fresh media.
Other pages worth a look here.
Also filed under Pocket-size drives.
Is yours behaving the same way?
Switch the device off, post it in, and decide nothing until the diagnosis comes back to tell you where you stand.