His Samsung T7 portable SSD stopped cooperating with a specific, familiar pair of symptoms. On his MacBook Pro he gets "The disk you attached was not readable by this computer", and although restarting did not help, "The drive shows up on Disk Utility but is grayed out". An SSD that appears in Disk Utility but sits greyed out and unreadable has a logical fault, not a dead controller — the drive is communicating and its presence is detected; what has failed is the volume's structures, which is the more recoverable end of the SSD-fault spectrum.
| Media | Samsung T7 portable SSD, 1TB, USB — detected by macOS and visible in Disk Utility but greyed out and reported unreadable, data intact and wanted |
| Reported situation | MacBook Pro reporting the disk not readable · restart attempted without effect · drive appearing in Disk Utility but greyed out · volume not mounting · SSD otherwise responsive to the system |
| Fault class | Filesystem or partition structure corruption on a responsive SSD — the drive detected and communicating, its volume unmountable behind damaged structures, distinct from a controller failure where the drive would not appear at all; SSD health to be confirmed |
| Equipment used | Drive imaged under a hardware write-blocker before any interpretation · APFS/HFS+ structures parsed from the image in R-Studio, backup copies of the volume structures located and compared · the SSD's controller and health checked on PC-3000 SSD, since a developing fault can present this way · signature carving for anything the damaged structures no longer reference · recovered files validated by rendering |
Appearing in Disk Utility is the key detail, and it is reassuring. That the drive shows up at all means the SSD is powering, communicating over USB, and being detected — the controller is alive and the drive is responsive. This distinguishes the case sharply from a dead-controller SSD, which would not appear anywhere. The drive is not gone; it is present but unmountable, which is a narrower fault.
Greyed out and "not readable" describes a filesystem macOS cannot parse. When Disk Utility shows a volume greyed out and reports it unreadable, it can see the disk but cannot mount the volume, because the structures that define and describe the filesystem are damaged. The data area behind those structures is typically intact — the fault is in the small records that let the system present the volume, not in the much larger space holding the files.
The productive move is to resist Disk Utility's repair and erase options. Faced with an unreadable volume, macOS offers First Aid, which writes repairs to the disk, and ultimately erase, which formats it. On a drive whose structures are damaged, First Aid can worsen the corruption, and erase would destroy the recoverable data outright. Neither should be run on the original; the drive should be left as-is and recovered from an image.
Recovery reads and rebuilds the structures from a copy. The volume's structures carry backup copies, and rebuilding from those restores the files with their names and organisation. Where structures are missing, signature carving recovers the file data directly from the data area. Running both and reconciling them returns the maximum — organised files where possible, carved files elsewhere — from a drive that is fundamentally healthy but logically broken.
Everything is done on an image, which is the standard protection. The SSD is imaged first under write-blocking, so no repair attempt — and no accidental First Aid or erase — touches the original, and all reconstruction happens on the copy. This keeps every option open and forecloses none, which matters when the drive is responsive and the data is intact.
The SSD's health is checked, because the presentation has more than one cause. Most greyed-out unreadable volumes are purely a structure problem, but a developing SSD fault or a controller issue can present similarly, so the drive's condition is assessed on professional equipment at the outset. The honest prognosis rests on structure-corruption versus a deeper drive fault, established before the work — and in the common case, a responsive T7 with a damaged volume recovers well.
The drive was imaged under a hardware write-blocker before anything interpreted it. APFS/HFS+ structures were parsed from the image in R-Studio, backup copies of the volume structures located and compared, and the SSD's controller and health checked on PC-3000 SSD. Signature carving recovered anything the damaged structures no longer referenced, and the recovered files were validated by rendering.
Responsive SSD imaged, volume structures rebuilt from their backup copies, and the files returned with their organisation. The assessment is free and the quote is a single fixed figure inclusive of VAT; if the data cannot be recovered, there is nothing to pay. The decode: the drive showing in Disk Utility means the controller is alive — greyed out and unreadable is a damaged volume, not a dead drive. Rebuilt from the volume's own backup structures on an image, your files come back, and First Aid never gets to make it worse.
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 outright. The drive appearing in Disk Utility means it's alive and communicating; greyed out and unreadable is a logical fault with the data intact behind it. Stop replugging it to retry. Have it imaged and recovered from a copy, so the structures can be rebuilt without any risk to the original.
Our case files are written up from genuine enquiries our lab has handled for customers across Staines, Surrey and the surrounding area, 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.