Data Recovery Case File · Mac & Apple Systems · The Remedy Addressed the Host
Clearing the Computer's Settings Cannot Change What the Drive Reports
His enquiry describes a sensible remedy applied to the wrong layer. A portable drive not appearing on his laptop in either the file browser or the disk utility, where "I have tried resetting the settings memory and it hasn't helped" — and which now sometimes reports that the disk attached was not readable. Those settings belong to the computer, not the drive, and the two messages together say something more useful than either alone.
| Media | Portable external hard drive holding professional photographic work — absent from the file browser and disk utility, with an unreadable-volume notice appearing on some occasions |
| Reported situation | Portable drive not appearing in the file browser · not appearing in the disk utility · host settings memory reset without effect · notice subsequently appearing that the attached disk was not readable · professional photographic work held · work dependent on the content |
| Fault class | Intermittent enumeration with unreadable structures when presenting — device alternating between absence and appearance; host-side remedies inapplicable |
| Equipment used | Host settings reset assessed as addressing the wrong layer · alternating symptoms interpreted as intermittent enumeration · drive assessed independently on a controlled bench supply · imaged write-blocked under strict per-sector timeouts during periods of presentation · structures interpreted from the image |
The decode: what the reset does, and what the two messages together mean
What the settings memory he cleared actually holds: the computer's own configuration — display preferences, start-up device selection, volume levels, time zone. It is the machine's memory of how it should behave, and it contains nothing about any attached drive.
Why clearing it is a reasonable thing to have tried: it is widely recommended for a range of odd behaviours and it is harmless. The problem is only that it addresses the host, and a drive that is not presenting itself is not affected by what the computer remembers about its own settings.
Why the distinction generalises: remedies aimed at a computer fix problems the computer is having. When a device is not announcing itself, the computer is behaving correctly by not showing it — there is nothing wrong at that layer to correct.
What his first symptom established: absence from both the file browser and the disk utility. The utility lists every device present, including those whose contents cannot be read, so absence from it means the drive was not announcing itself at all.
Why the second message changes the picture: an unreadable-volume notice only appears for a device that is present. The system must have detected the drive and attempted to read its structures in order to report them unreadable — so on that occasion, it did announce itself.
What the two together therefore mean: the drive is presenting intermittently. Sometimes it completes its introduction and offers structures the system cannot interpret; sometimes it does not appear at all — and that alternation is the real finding.
Why intermittency is the most important thing to act on: it means there are periods when the drive is reachable. Those periods are the opportunity to capture it, and they typically become less frequent rather than more.
Why continued connection attempts spend that opportunity: each is a spin-up and an enumeration attempt on a drive already struggling to complete them. Testing to see whether it appears today is using the window to observe it rather than to copy it.
What the unreadable structures suggest separately: where the drive does present, the description of its volume cannot be interpreted. That may be structural damage, or it may be the drive returning inconsistent data during a marginal read — and the difference is established from an image rather than from the drive.
What must not happen: no accepting any offer to initialise or repair when the unreadable notice appears. That prompt arrives precisely when the drive is presenting, which is the moment a write would do the most damage.
On the bench
The host settings reset was assessed as addressing the wrong layer — that memory holding the computer's own configuration rather than any information about attached devices, so a drive not announcing itself is unaffected. Alternating symptoms were interpreted as intermittent enumeration: absence from the disk utility indicates no announcement, whereas an unreadable-volume notice requires the device to have been detected and its structures read, so the two together establish presentation varying between attempts. Imaging ran write-blocked under strict per-sector timeouts during periods of presentation.
The outcome
The reset assessed as addressing the wrong layer, the alternating symptoms read as intermittent enumeration, and the drive imaged during periods of presentation. 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: those settings hold your computer's configuration, not anything about the drive. And your two messages differ usefully — an unreadable-volume notice needs the drive to be present, so it is appearing sometimes and not others.
When a remedy aimed at the computer does not help
Stop reconnecting to test it, because the drive appearing sometimes is the window rather than a symptom to observe. Resetting your computer's settings memory is harmless and widely suggested, but it holds the machine's own configuration and nothing about attached devices — so a drive that isn't announcing itself is unaffected. Read your two messages as different findings: absence from the disk utility means the drive never presented, while an unreadable-volume notice requires it to have been detected. Together they mean intermittent presentation, and those periods become less frequent over time. Refuse any offer to initialise when it does appear.
Stop testing it — call Easy Data Recovery on 028 9002 0144; host remedies assessed as the wrong layer, alternating symptoms read as intermittent enumeration, imaged under capped timeouts during presentation.
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.