Portable drives · job record · PLY-2025-0625
Named by the BIOS. Windows Freezes.
Nine years of paperwork lived on one external drive belonging to a drainage contractor in St Austell — scanned receipts, VAT workings, invoices — and an accountant had spent a year chasing a set of year-end figures stuck on it. The boot screen picks it up with no trouble at all
, he told us. Then Windows comes up, and the whole thing stops dead until I unplug it
.
Sounds like yours? Talk it through.
0800 6890668
Why it happens.
Neither of them is lying. They are simply asking different questions. The BIOS wants nothing but a name: model, capacity, a handful of parameters. Anything that spins and can hold a conversation with its own controller will supply that. Windows wants what is on the disk — first the partition table, then the filesystem records, then one sector after another handed back inside a deadline measured in fractions of a second. Overrun it and the drive is dropped. Clearing the first hurdle and falling at the second means failing at the only work a drive exists to do. Two explanations account for most of it. Firmware may collapse the instant anybody asks for user data, or the media may be worn to the point where reads keep running past the time allowed them.
The kit this job called for.
How the job runs →| The kit | What it did here | Why we keep it |
|---|---|---|
| ACE Lab PC-3000 Express | Answered the one question everything else depends on: firmware or worn media | Drops the disk into its maker's service mode, out of reach over plain ATA |
| PC-3000 Data Extractor | Copied the disk with timeouts opened right out and no clock running | The PC-3000 runs the copy through the drive's own firmware |
| R-Studio Technician | Once the image was finished, reassembled the NTFS volume from it | Reads nearly every file system, and rebuilds RAID sets from images |
How it ran.
Settle which of the two it is before it turns again
The firmware was perfectly sound. Its service area read back without difficulty and every module was present. Reading was where it failed. Sectors did emerge, singly, several seconds apart. That accounts for the symptom entirely: Windows allows a good deal less than a second per sector, and once that is gone it stops waiting.
Copy it with no clock running
A slow drive gets no patience from Windows. A bench imager has nothing but patience, and that is very nearly the whole difference between them. While the disk goes on replying, the imager goes on asking. Timeouts were opened right out, stalls were cleared with measured resets, and the read rate was left to fall to whatever the worn regions would give. Several days later it had taken the lot.
Everything after that happens on the image
The completed image yielded up the partition table and the NTFS structures, and out of those the volume was assembled once more. Weeks of being shut opened at a single attempt: ledgers, invoices, receipts.
How it ended up.
A single worn band kept hold of its sectors right through to the finish, with a few scanned receipts inside it. That is the entire loss. All the invoices survived, all the VAT workbooks survived, and nine years of records went back to St Austell on a new drive.
Pages people open after this.
Other cases from the pocket-drive file.
Seeing the same thing?
Leave it switched off and post it in. Nothing happens until the diagnosis, which lists what can still be read and what cannot.