Call us — 01865 593000
Mon–Fri · 9am–5:30pm · No fix, no fee
Start a free diagnostic →

Data Recovery Case File · Portable Drives · Two Faults, One Question

Where the Encryption Lives Decides Everything Here

His enquiry contains two problems and they interact. An external drive holding family photographs and old backups: "the drive was passcode protected but the passwords are lost, and the drive no longer turns on. I'm not sure what brand it is — there doesn't seem to be any label on it." Either fault alone would be ordinary. Together, the outcome turns on a single question nobody asks when they buy a drive: whether the protection lives in the enclosure or on the disk.

MediaUnbranded external hard drive with passcode protection of undetermined type — not powering; credential no longer known; family photographic content and system backups held
Reported situationExternal drive holding family photographs and computer backups · drive protected by a passcode · passcode no longer known · drive no longer powering on · no manufacturer marking present · contents required
Fault classPower failure combined with unknown credential — encryption implementation determinative; hardware-encrypted enclosures binding data to the failed electronics
Equipment usedEncryption implementation identified from the enclosure electronics before any conclusion · drive removed and assessed on a native connection · encrypted signature checked against known implementations · host-side credential and keychain sources established as an alternative route

The decode: two implementations that look identical from outside

The first kind — software protection. A program installed on the computer encrypts the data before it is written, and the drive itself is an ordinary drive holding scrambled content. The enclosure is irrelevant to the encryption, so a dead enclosure is just a dead enclosure — the disk comes out, reads on a native connection, and the only remaining obstacle is the password.

The second kind — hardware protection. A controller in the enclosure encrypts everything on the way through, with the key held in that controller. The disk inside holds data no computer can interpret without it. Here a failed enclosure is a much more serious matter, because the electronics that failed are the same electronics holding the key.

Why nobody knows which they have: both are sold as password-protected drives, both prompt for a code, and both look identical in use. The distinction is in the specification and almost never in anybody's memory, which is why it is established from the enclosure's electronics rather than from what the owner recalls.

So the first step is not the password: it is opening the enclosure and identifying what is in it. That answers whether the power failure is an inconvenience or the whole case, and it costs nothing but the assessment.

Why the missing label matters less than it seems: drives carry their model and manufacturer internally, readable as soon as they respond. An unlabelled case tells you nothing and the disk inside will identify itself.

On the lost password, and this is worth pursuing in parallel: passwords for such drives are frequently stored by the computer that used them — in a keychain, a credential manager, or the manufacturer's own utility. The machine that accessed the drive is often the place the password still exists, and it is worth searching before concluding it is gone.

Being honest about the worst case: hardware encryption plus failed enclosure electronics plus a lost credential is among the least recoverable combinations in this archive. That should be said before anybody spends anything, and the assessment establishes whether it applies.

What must not happen: no attempts to force or reset the protection. Some implementations erase on repeated failures, by design.

On the bench

The encryption implementation was identified from the enclosure electronics before any conclusion — software protection leaving an ordinary drive whose enclosure is irrelevant, while hardware protection holds the key in the enclosure controller, so the same failure is an inconvenience in one case and determinative in the other. The drive was removed and assessed on a native connection, the encrypted signature checked against known implementations, and host-side credential and keychain sources established as an alternative route.

The outcome

The implementation identified before any conclusion, the disk assessed natively and host-side credential sources pursued in parallel. Free assessment, one fixed written figure including VAT; where a drive has to be opened, 50% of parts and labour is payable upfront with the balance only on success — otherwise no recovery, no fee. The decode: it depends entirely on where the protection lives. Software encryption leaves an ordinary drive and a dead enclosure is merely a dead enclosure. Hardware encryption keeps the key in the enclosure controller — so the electronics that failed are the electronics holding it.

Password-protected drive that has also stopped working

Search the computer that used to access it before anything else — passwords for these drives are frequently stored in a keychain, a credential manager, or the manufacturer's own utility, and the machine is often where the password still exists. Then know that everything depends on where the protection lives. If a program on your computer did the encrypting, the drive inside is ordinary and a dead enclosure is just a dead enclosure. If a controller in the enclosure did it, the key lives in the electronics that failed, which is a much harder position. Both are sold the same way and look identical in use. Don't attempt to reset the protection — some implementations erase after repeated failures.

Encrypted drive that won't power on?
Check the old computer for the password — then call Oxford Data Recovery on 01865 593000; implementation identified from the enclosure electronics before any conclusion, disk assessed on a native connection.
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.