Data Recovery Case File · Mac & Apple Ecosystem · Recognised, Not Readable
The Volume Is Seen and Its Contents Are Not
This enquiry is one of the most helpful in the archive. A proprietary blade drive from a 2015 laptop, and the owner writes: "it is a blade drive but not the standard format. I can send you a photo if you'd like to check that you have the correct equipment for this particular drive. The volume is seen and identified correctly, but trying to browse the drive" fails. She has identified the hardware, anticipated the adapter question, and described the fault precisely. All three of those save time and one of them narrows the problem to a single layer.
| Media | Proprietary blade solid-state drive from a 2015 laptop — non-standard connector; volume detected and correctly identified, contents not listable |
| Reported situation | Drive of a proprietary blade format specific to its generation · volume seen and identified correctly by the host · browsing the volume failing · owner offering photographic identification of the connector · specific data required |
| Fault class | Volume recognised with directory structures unreadable — filesystem-level failure over a functioning controller |
| Equipment used | Connector generation confirmed before receipt · encryption status established · read on a generation-matched adapter · imaged write-blocked before any reconstruction · structures rebuilt on the image including surviving backup copies · files validated by opening |
The decode: what "identified correctly" rules out
Why that phrase does so much work: for a volume to be seen and identified, a great deal must already be working. The drive powers, its controller completes initialisation, it reports its capacity and identity, the partition table reads, and the filesystem is recognised well enough for the system to name it and know what it is. Every one of those layers is functioning. The failure is at the next step — reading the directory structures that list what the volume contains.
Why that is the better category: a drive that does not identify at all is a controller problem, which on solid-state media is among the harder positions. Identification succeeding places this entirely at filesystem level, where the work is reconstruction against an image rather than anything done to the device.
Why filesystems fail this way: the catalogue describing a volume's contents is a structure like any other, and it can be damaged by an interrupted write, an unclean shutdown, or a bad region beneath it — while the volume header that identifies the filesystem, which sits elsewhere and is written rarely, remains perfectly intact. That is precisely the split she is seeing.
Why her offer of a photograph matters practically: that generation used a proprietary connector that changed between model years, and the adapters are specific. Sending an image of the connector before the drive travels means the right adapter is in hand when it arrives, rather than the drive sitting on a bench waiting for a part. It is a small courtesy that removes a real delay, and almost nobody thinks of it.
The one thing worth establishing before anything else: whether full-disk encryption was enabled. On that operating system version it was optional and frequently left off — but if it was on, the recovery password or key becomes necessary regardless of the drive's condition, and that should be known at the start rather than discovered midway.
Why the reconstruction usually returns everything: filesystems keep backup copies of their key structures at known positions away from the primary set. Where the primary catalogue is damaged and a copy survives, files come back with their folders and original names rather than as carved output.
What must not be run: the disk utility's repair function. Faced with a volume it can identify and not read, that is exactly what it will offer — and it writes its conclusions over the structures a rebuild would use.
On the bench
The connector generation was confirmed before receipt from the owner's photograph, that model year using a proprietary format for which adapters are specific — which meant the correct adapter was in hand on arrival rather than the drive waiting on a part. Encryption status was established at the outset, since a key requirement changes the position regardless of drive condition. The drive was read on a generation-matched adapter, imaged write-blocked before any reconstruction, and structures rebuilt on the image from their surviving backup copies.
The outcome
The adapter confirmed before arrival, the encryption position settled first and the structures rebuilt from their surviving copies against the image. Free assessment, one fixed written figure including VAT; where a chip has to be removed, 50% of parts and labour is payable upfront with the balance only on success — otherwise no recovery, no fee. The decode, for anyone whose volume is identified but will not list: that phrase rules out a great deal. Identification requires the controller, the partition table and the filesystem header all to be working, so the failure is at the catalogue layer — the better category, and reconstruction against an image. Don't run the repair function.
Volume that's recognised but won't show its contents
Don't run the disk utility's repair — faced with a volume it can name and can't read, that's exactly what it offers, and it writes its conclusions over what a rebuild needs. Take encouragement from being able to say the volume is identified correctly, though, because that rules out a lot: the drive powered, its controller initialised, it reported its identity, the partition table read, and the filesystem header was recognised. All of that works. What's damaged is the catalogue listing the contents, which sits separately and is written constantly, so it's far more exposed. There's usually a backup copy elsewhere on the volume. If your drive uses a proprietary connector, send a photo of it in advance — the adapters are model-specific.
Don't repair it — call Guildford Data Recovery on 01483 901310; connector confirmed before arrival, encryption position established first, structures rebuilt from their surviving copies against the image.
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.