Case notes · Portable drives · SDR-2025-0625
The BIOS Finds It; Windows Never Does.
The disk lived in an odd sort of limbo: my desktop won't see it any more
, and yet the BIOS still lists it
at startup. Over USB, Windows produced nothing whatsoever. Marked present at registration, missing from the lesson — with several years of accounts stranded in between.
Seeing the same thing yourself?
0800 6890668
The translation.
Appearing in the BIOS proves only that the disk can answer its identify command and state its name. Mounting asks a great deal more: partition tables and filesystem metadata read steadily, and read inside the timeout the operating system is willing to allow. Manage the first but fail the second and the disk is faltering under genuine work — firmware stumbling once real user data is requested, or a surface too tired to deliver the reads a mount needs.
Kit used on this job.
What happens in a case →| Platform | Its role in this case | Why we use it |
|---|---|---|
| ACE Lab PC-3000 Express | Settled whether firmware or surface was to blame — the junction the case hangs on | Talks to drives using maker-specific commands beyond the ordinary ATA instruction set |
| PC-3000 Data Extractor | Imaged at whatever pace the disk allowed, with no OS timeout to appease | The PC-3000 platform's imaging unit, commanded by its firmware unit |
| R-Studio Technician | Reassembled the NTFS volume out of the finished image | Wide filesystem support, with RAID rebuilds you can trust |
In the lab.
Work out which side of that gap the fault lies on
Questioning the disk at firmware level split the two options apart. Its service area was whole and every internal module returned properly, so firmware was ruled out. User-data reads did finish — just slowly, and slowness alone is enough: Windows had been abandoning the attempt long before the disk got to the end of its answer.
Image without any hurry — that is the whole trick
What a lab imager has that no operating system does is the willingness to wait all day. The disk was copied at whatever rate it could hold, timeouts opened right up, and every stall met with a controlled reset instead of a shrug. It ran far longer than a healthy disk would have. It finished.
Open the volume off the image
Once the image was complete, its partition and filesystem structures were read out and the volume put back together — it opened from the copy in seconds, after months of refusing to open from the disk itself.
The result.
The volume opened from the image nearly complete — one worn region never read, costing a few scanned receipts. The disk's limbo ended in retirement; the accounts went home on media that answers first time.
Similar cases on the index.
Further cases in Portable drives.
Does this sound like your own drive?
The rule holds as in every case above: switch it off, and let a free diagnosis come before any decision.