Data Recovery Case File · Desktop Externals & Aging Drives · Most of the Work Already Done
Shucked, and Now Unreadable
His enquiry described a small piece of ordinary tinkering with an unexpected result. A 3TB Seagate drive "that was originally in an enclosure. I took it out, and now I can't access my photos, videos and other data on the 3TB drive." This is the companion to a warning this archive gives often, seen from the other side: he has discovered that on many external drives, the enclosure board was doing considerably more than joining two connectors together. There are two reasons a shucked drive becomes unreadable, both common on drives of that capacity — and in most cases the remedy is simply to put it back.
| Media | 3TB hard drive removed from its original external enclosure — contents inaccessible once connected directly; enclosure retained |
| Reported situation | Drive functioning normally within its enclosure · removed by the owner and connected directly · data no longer accessible · no fault or noise reported |
| Fault class | Enclosure-dependent presentation — hardware encryption or sector-size translation performed by the bridge board; drive and data intact |
| Equipment used | Original enclosure board retained and tested · sector-size presentation identified · read through the original bridge where encryption or translation applied · contents verified by opening |
The decode: two reasons, both fixable
Reason one — hardware encryption. A great many external drives encrypt their contents in the enclosure's bridge board, transparently and without the owner ever being told. No password is set and nothing announces it; the drive simply works when plugged in. Remove that board and connect the bare drive elsewhere and the raw contents are ciphertext — the drive appears unformatted or unreadable, and the data looks destroyed. It is not. The key lives in the board he still has.
Reason two — sector-size translation, which matters especially at 3TB. Hard drives of that generation use 4096-byte physical sectors while presenting 512-byte logical sectors, and enclosure bridges vary in which they present to the host. A drive initialised while its bridge reported one sector size will have its partition structures laid out on that assumption. Connect it directly, where the sector size is reported differently, and the offsets no longer line up — so the partition table cannot be read and the drive appears unpartitioned. Again nothing has been damaged; the same bytes are simply being interpreted against the wrong ruler.
Why both look identical from outside: in each case a perfectly healthy drive presents as raw, unformatted or unrecognised. That is exactly the state that invites somebody to accept an offer to initialise it — which is the one thing that would turn a reversible situation into a real loss, because it writes fresh structures over the originals.
The remedy, which is usually simple: put the drive back in its own enclosure and read it there. That single step resolves both causes at once, because it restores the board that holds the key and presents the sector size the volume was built for. The enclosure must be its own — a different case of the same model will not necessarily carry the same key, and swapping bridges is not a reliable substitute.
The lesson worth keeping: the enclosure is part of the storage system, not packaging around it. Anybody shucking a drive should keep the original case and board, and should treat "it no longer reads" as a presentation problem to be reversed rather than evidence of failure.
On the bench
The original enclosure board was retained and tested rather than set aside, since on drives of this kind it may hold the encryption key and it certainly determines how the volume is presented. The sector-size presentation was identified and compared against the layout the partition structures assumed — the difference that makes a healthy drive appear unpartitioned. Where encryption or translation applied, the drive was read through its own bridge so that both were satisfied, and the contents verified by opening before delivery on fresh media.
The outcome
The drive read through its original bridge with both encryption and sector presentation satisfied, and the contents verified and delivered. Free assessment, one fixed written figure including VAT, no recovery, no fee. The decode, for anyone whose shucked drive stopped reading: the enclosure board was doing more than connecting things — many externals encrypt transparently in that board, so a bare drive returns ciphertext that looks like an unformatted disk; and on drives around 3TB, bridges differ in the sector size they report, so a volume built under one presentation cannot be parsed under another and appears unpartitioned; both look identical from outside and neither has damaged anything. Put the drive back in its own enclosure, and never accept an offer to initialise it.
Drive that stopped reading after you took it out of its case
Put it back in the original enclosure — that single step fixes both of the usual causes. Many external drives encrypt their contents inside the enclosure's own circuit board, transparently, with no password and no indication to the owner; take the drive out and the raw contents are meaningless, so a perfectly healthy disk appears unformatted. Separately, drives around 3TB and above depend on what sector size the bridge reports to the computer, and a volume laid out under one presentation can't be parsed under another, which also makes the drive look unpartitioned. Neither has damaged anything. Keep the original case and board — a different enclosure of the same model won't necessarily carry the same key. And whatever happens, don't accept any offer to initialise or format the drive, because that's what turns a reversible situation into a real loss.
Put it back in its own case — or call Glasgow Data Recovery on 0141 404 0294; original bridge tested and used, sector presentation identified, contents verified by opening.
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.