His Mac drive filled up and then split the difference on whether it exists. After it "got a full disk space", it "stopped being recognised" by the MacBook — yet the "MacBook system report, it detects the hard drive there", while "drive Utility it does not recognise the hard drive", leaving the data inaccessible. A drive the System Report sees but Disk Utility does not has a volume-level fault, not a dead drive — the hardware is detected at the low level, but its volume is damaged enough that Disk Utility cannot present it, which is the recoverable end of the spectrum, and the full disk is a clue to how it happened.
| Media | External hard drive used with a MacBook that filled to full capacity, then stopped being recognised — detected in the Mac's System Report but absent from Disk Utility, data inaccessible. |
| Reported situation | Drive filled to full disk space · then stopped being recognised by the MacBook · System Report still detecting the drive at the hardware level · Disk Utility not recognising it, so the volume won't present · files needed from the drive. |
| Fault class | Filesystem or volume structure corruption on a detected drive — the hardware seen at the low level but the volume unmountable, plausibly triggered by the disk filling completely; the data intact behind the damaged structures, drive health to be confirmed. |
| Equipment used | Drive imaged under a hardware write-blocker before any interpretation · drive health confirmed on PC-3000 UDMA, since it is detected and the fault appears logical · Mac-native APFS/HFS+ structures parsed from the image in R-Studio, backup copies of the volume structures located and rebuilt · signature carving for anything the damaged structures no longer reference · recovered files validated by rendering. |
The split between System Report and Disk Utility locates the fault precisely, and it is reassuring. System Report lists hardware the Mac detects at a low level; Disk Utility works one level up, reading the volume structures to present the disk for use. A drive that appears in System Report but not Disk Utility is detected as hardware — it powers and communicates — but its volume cannot be read. That is a volume-level fault, not a dead drive: the hardware is fine, the filesystem is damaged.
The full disk is a plausible trigger, which explains the timing. That the drive filled completely and then failed to be recognised is not a coincidence. A volume filled to absolute capacity can leave its filesystem unable to complete operations — no room to update its own structures — and a structure update caught with no free space can corrupt the volume. The disk filling is very likely what damaged the structures, which is why recognition failed at that moment rather than randomly.
Detected-but-not-in-Disk-Utility means the data is intact behind the damage. Because the drive is detected as hardware, the memory holding the files is being reached at the low level; what has failed is the volume structures Disk Utility needs to present it. The data sits intact behind those damaged structures — the fault is in the records that describe the volume, not in the space holding the files. That is the recoverable combination: healthy drive, damaged volume.
The move to resist is Disk Utility's repair and erase, the main hazard. Faced with a volume it cannot present, Disk Utility offers First Aid, which writes repairs to the disk, and erase. On a volume whose structures are damaged — especially one damaged by filling — First Aid can worsen the corruption, and erase would destroy the recoverable data. Neither should be run on the original; the drive should be left as-is and recovered from an image.
The honest prognosis is good, with drive health confirmed first. A detected drive with a volume fault from a full disk usually recovers well. Drive health is verified at the outset to rule out a coincident hardware fault, and the recoverable content confirmed before any charge. The forward note follows the cause: leaving headroom on a drive avoids the full-disk corruption that triggered this, and the recovered data belongs somewhere backed up.
The drive was imaged under a hardware write-blocker before any interpretation, and its health confirmed on PC-3000 UDMA. The Mac-native APFS/HFS+ structures were parsed from the image in R-Studio, backup copies of the volume structures located and rebuilt, and signature carving used for anything the damaged structures no longer referenced. The recovered files were validated by rendering.
Detected drive imaged, the volume structures rebuilt from their backup copies, and the files returned with their organisation. The diagnostic costs nothing and completes within two working days of arrival, and the quote is one fixed written figure with VAT already in it; if the data can't be brought back, no charge is made. The decode: appearing in System Report but not Disk Utility means the drive is detected but its volume is damaged — likely by filling completely — not that the drive is dead. Rebuilt from the volume's own backup structures on an image, your files come back, and First Aid never gets to deepen it.
Don't run First Aid and never click erase — First Aid writes to a volume whose structures are already damaged and can deepen the corruption, and erase destroys your data. The drive appearing in System Report means it's detected as hardware; missing from Disk Utility is a volume fault with the data intact behind it, often triggered by the disk filling completely. Stop replugging it to retry. Have it imaged and recovered from a copy, and in future leave headroom so a full disk can't corrupt the volume.
Our case files are written up from genuine enquiries our lab has handled for customers across Swansea and South Wales, anonymised to protect client confidentiality. Each one describes the diagnostic and recovery approach our engineers apply to that fault, using the equipment listed.
Free diagnostic, fixed quote, no fix no fee — start now or call the freephone.