Portable drives · case notes · HUL-2025-0625
The BIOS Finds It. Windows Locks Up.
One drainage contractor in Doncaster had all his documents relating to paperwork over the last 9 years on one external hard drive: scanned receipts, invoices, VAT worksheets etc. His accountant had been calling him each week about the year-end accounts, which were stuck because of this. The boot screen has no bother finding it
, he said. After Windows boots, everything stops until I pull the lead out
.
Sounds like yours? Ring us.
0800 6890668
What causes it.
Both are truthful. They are simply asking two distinct questions. The BIOS requests a name and little else: model number, storage capacity, etc., etc. Any disk that continues to spin and communicate with its internal controller can respond to these requests. Windows requires access to the contents: including the partition table, file system information, followed by sector after sector provided prior to a window of less than a second expiring. If it fails to receive this information within the specified timeframe, Windows removes the drive. Therefore, if a device successfully passes the initial test and fails the secondary test it has failed at its only purpose. Typically, there are two ways a device may fail. First, either the firmware fails immediately upon request for user data or secondly, the read surface is sufficiently degraded such that reads exceed their allowed limits.
The tools this one needed.
The steps we follow →| The gear | What this one did | Why we have it |
|---|---|---|
| ACE Lab PC-3000 Express | Settled the one question that governs the rest: firmware fault or worn media | Reaches the vendor service commands an ordinary ATA connection cannot |
| PC-3000 Data Extractor | Imaged the disk with the timeouts opened right up and no schedule | Copying is run at firmware level, with the PC-3000 in charge |
| R-Studio Technician | Rebuilt the NTFS volume from the image once it was complete | Handles almost any file system, and puts RAID sets back together |
The stages.
Decide which it is before it spins again
The firmware was fine. Its service area read back cleanly, no modules were missing. However, the reading had failed. Sectors did come out, one at a time, several seconds apart. That covers the entire symptom: Windows allows less than a second per sector, and then stops waiting.
Copy it with the timer switched off
Windows will not wait for a slow drive. A bench imager will and that's just about the whole difference. As long as the disk keeps talking, the imager keeps asking. Timeouts were opened right up, stalls dealt with by measured resets, and the read rate allowed to drop to whatever the worn areas would provide. It ran for days and finished the lot.
Everything else is done on the image
The partition table and NTFS structures came from the completed image, and the volume was re-assembled from those. What had been closed for weeks opened on the first attempt (ledgers, invoices, receipts).
How it finished.
Only one bad band on this disk refused access to its sectors right to the very end, and a few scanned receipts were sitting in the band. This was all of the loss. All invoices were present, all of the VAT workbooks were present and all nine years of the data went back to Doncaster on a brand-new drive.
What people read after this.
More from the Pocket-size drives file.
Is yours doing the same?
Turn it off. Get a quote first. Send it to us. The diagnosis comes first. It tells you which files remain accessible/readable and which do not.