Data Recovery Case File · Portable Drives · The Name Comes From the Enclosure
A Product Name Appearing in a Device List Is the Interface Board Introducing Itself
His enquiry includes a cross-check most people do not think to run, and it produced a precise result. A ruggedised portable drive used for photograph backups which will not appear on his new machine, where the indicator lights and the drive is audible — and, tellingly, "I have plugged it into a different computer" — where it appears by its product name and nothing else. That name is not coming from the drive, and knowing where it does come from settles a great deal.
| Media | Ruggedised portable hard drive — enclosure identifying itself by product name on a second host; no volume presented on either host; indicator illuminating and mechanical activity audible |
| Reported situation | Portable drive used for photographic backups · drive not appearing on the owner's current machine · indicator illuminating · mechanical activity audible · drive connected to a second computer of a different platform · that machine listing the device by product name · no volume presented on either machine |
| Fault class | Interface bridge enumerating and reporting its identity with no storage behind it — bridge functional; drive not responding or not completing initialisation |
| Equipment used | Product-name enumeration attributed to the enclosure descriptor rather than to the drive · drive removed from the enclosure and addressed directly with imposed timeouts · current draw measured across the start-up cycle on a controlled bench supply · service area read under strict timeouts in vendor technological modes · imaged under capped timeouts once initialisation was achieved |
The decode: where the name lives, and what its presence rules in and out
What an external drive is made of, for this purpose: two devices. A bridge board that speaks to the computer, and a drive behind it that speaks only to the bridge.
Where the product name is stored: in the bridge. The board carries a descriptor giving the manufacturer and model, which it presents the moment it is connected.
Why it presents that before knowing anything about the drive: the sequence requires it. A device must identify itself to be enumerated at all, and that happens before it reports what storage it has found.
What follows from seeing the name and no volume: a clean division. The cable, the port, the host and the bridge all work, and the drive behind the bridge is not answering.
Why testing on a second platform strengthened that: it removed the machine. Identical behaviour on a different kind of computer eliminates the operating system as well as the hardware.
Why the audible activity matters alongside it: the drive has power. Something is turning, so the bridge is supplying the drive and the drive is at least starting.
What that narrows the fault to: initialisation or the link. Either the drive is not completing its own start-up, or the connection between it and the bridge has failed.
Why the second possibility is worth taking seriously: ruggedised enclosures take shocks. A drive built to be knocked about is connected inside by a link that absorbs those knocks, and that link can fail while everything else survives.
Why the enclosure comes off first regardless: it settles the question immediately. A drive removed and addressed directly either identifies itself or does not.
What must not happen meanwhile: no further connection. A drive failing during initialisation repeats that failure every time.
On the bench
Product-name enumeration was attributed to the enclosure descriptor rather than to the drive — external units comprising a bridge board that speaks to the host and a drive that speaks only to the bridge, with the product name held in the bridge and presented on connection, before any storage is reported. Seeing the name with no volume therefore clears cable, port, host and bridge. Identical behaviour on a second platform eliminated the operating system. The drive was addressed directly.
The outcome
The product name attributed to the enclosure, the drive addressed directly outside it, and the service area read under strict timeouts. Free assessment, one fixed written figure including VAT, 50% of parts and labour upfront with the balance only on successful recovery where the drive is opened. The decode: that name came from the enclosure, not from your drive. It proves the board is working and introduces itself before it knows what storage is attached — which places the fault entirely behind it.
When a computer names your drive but shows no volume
Take the name as information about the enclosure rather than the drive. An external unit is a bridge board that talks to the computer plus a drive that only talks to the bridge, and the product name is stored in the bridge and presented on connection — before it has established what storage is attached. So seeing the name with no volume clears your cable, port, computer and that board in one go. Testing on a different kind of machine, as you did, removes the operating system too.
That name is the enclosure — call Cambridge Data Recovery on 01223 655015; enumeration attributed to the bridge descriptor, drive addressed directly outside it, service area read under strict timeouts.
Request a quote online →
Our case files are drawn from genuine enquiries received by our laboratory over the past ten years, anonymised to protect client confidentiality. Each one describes the diagnostic and recovery procedure our engineers apply to that fault, using the equipment listed.