Case file · Portable drives · BDR-2025-0625
The BIOS Detects It, but Windows Doesn't.
The drive occupied a strange half-existence: no longer being recognised by my desktop
— although still being detected in the BIOS
. Windows, over USB, offered nothing at all. Present at roll-call, absent in class — and the data unreachable in the gap between.
Same symptoms on your desk?
01273 964902
The decode.
BIOS detection means the drive can complete its identify command and report who it is. Mounting requires far more: sustained reads of partition tables and filesystem metadata, delivered inside the operating system's patience. A drive that manages the first and fails the second is stalling in real work — either firmware faltering when asked for actual user data, or a surface too weak to sustain the reads mounting demands.
Equipment on this case.
How a case runs →| Platform | What it did here | Why this tool |
|---|---|---|
| ACE Lab PC-3000 Express | Determined whether the stall was firmware or surface — the fork the whole case turns on | Speaks the vendor-specific commands that sit outside the standard ATA set |
| PC-3000 Data Extractor | Imaged at the drive's own pace, with no operating-system timeout to satisfy | The imaging half of the PC-3000 platform, driven by the firmware half |
| R-Studio Technician | Rebuilt the NTFS volume from the completed image | Broad filesystem coverage and dependable RAID reconstruction |
On the bench.
Establish which side of the gap the fault sits on
Firmware-level interrogation separated the two possibilities. The service area was intact and the drive's own modules read correctly — so this was not a firmware case. Reads of user data completed, but slowly, and slow is all it takes: Windows had been giving up long before the drive had finished answering.
Image with infinite patience, which is the point
The one thing lab imaging offers that an operating system cannot is willingness to wait. The drive was imaged at whatever speed it could sustain, with timeouts set generously and stalls handled by controlled reset rather than abandonment. It took considerably longer than a healthy drive; it completed.
Mount the volume from the copy
With a full image in hand, the partition and filesystem structures were parsed and the volume assembled — mounting cleanly from the copy in seconds, having refused to mount from the original for weeks.
The outcome.
The volume mounted cleanly from the image with everything present. The drive's half-existence ended in honourable retirement, and its contents went home on hardware that answers promptly.
Related on the index.
More from Portable drives.
Recognise your own drive in this story?
Same rule as every case above: power it down, and let the diagnosis be free before any decision has to be.