Home / Case Studies / Portable Drives
Portable Drives · case file

It Crashed During a Save and Never Came Back

He is careful to rule out the obvious before asking. His LaCie 4TB "stopped being recognised" on his MacBook Pro — the light still comes on, but it is absent from Finder and Disk Utility — and he notes pointedly that it "wasn't dropped or physically damaged". It happened while he was working in a music program with files running off the drive: "The program froze and and eventually computer crashed whilst I was doing a Save", something "quite routine". No physical damage plus a crash during a save points firmly at filesystem corruption — the interrupted write damaged the volume's structures, not the drive, which is the recoverable end of the spectrum.

External DriveCorruption / Filesystem
// case at a glance
MediaLaCie 4TB external hard drive — powering (light on) but unrecognised in Finder and Disk Utility after a computer crash during a save; no physical damage reported.
Reported situationDrive in active use with a music program's files running off it · program froze and the computer crashed during a save operation · drive lights up but is not recognised afterward · absent from Finder and Disk Utility · no drop or physical damage · data recovery sought.
Fault classFilesystem structure corruption from an interrupted write — the volume's structures damaged mid-save so it will not mount, the drive itself healthy and the data intact behind the damage; drive health to be confirmed.
Equipment usedDrive imaged under a hardware write-blocker before any interpretation · drive health confirmed on PC-3000 UDMA, since it powers 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 decode

The decode

His ruling out of physical damage genuinely narrows the diagnosis, and it is the right observation. Drives fail physically or logically, and the two look different. No drop, no knock, and a drive that still powers and lights up strongly suggests the hardware is intact — which directs attention to a logical fault, a problem with the data structures rather than the drive itself. Noting the absence of physical trauma is exactly the useful information it appears to be.

A crash during a save is precisely when filesystem corruption occurs. Saving a file means writing to the drive and updating the volume's structures to record the change. A freeze and crash mid-save interrupts that update, leaving the structures half-written and internally inconsistent. That the failure happened during a save, on a drive with files actively running off it, is the mechanism exactly: the interrupted write corrupted the bookkeeping the system needs to mount the volume.

"Lights up but unrecognised" fits logical corruption, not drive death. The light coming on means the drive has power and its basics work; being unrecognised in Finder and Disk Utility means macOS cannot mount the volume, because the structures it reads are damaged. A physically dead drive behaves differently — this one gets far enough to power and be present at the hardware level, but its volume will not mount. That combination is the recoverable one: healthy drive, damaged structures.

The routine nature of the operation is worth acknowledging, because it reassures. He is right that saving a file is routine — and that is exactly why this kind of loss catches careful people. There was no misuse; an ordinary save met an unlucky crash. The fault is not a sign the drive was mistreated, and it does not imply deeper damage. It is a common, well-understood consequence of an interrupted write.

Recovery rebuilds the structures from their backup copies on an image. The volume's structures carry backup copies, and rebuilding from those restores the files with their names and folders. Where structures are missing, carving recovers file data directly. All of this happens on a write-blocked image so that macOS's First Aid — which writes to the disk and can worsen the corruption — never touches the original, and every option stays open.

The honest prognosis is good, with drive health confirmed first. An interrupted-write corruption on a healthy drive usually recovers well, with the one caveat that whatever file was mid-save may return incomplete — a small, specific loss, reported by name. The drive's physical health is confirmed at the outset to rule out a coincident hardware fault, and the recoverable content stated before any charge.

// on the bench

On the bench

The drive was imaged under a hardware write-blocker before anything interpreted it, 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.

// the outcome

The outcome

Healthy drive imaged, the volume structures rebuilt after the interrupted save, 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: no physical damage plus a crash during a save is filesystem corruption, not a broken drive. The interrupted write damaged the structures, not your data — rebuilt from their backup copies on an image, your files come back.

A drive that stopped mounting after a crash during a save

Don't run Disk Utility's First Aid or let it erase the drive — an interrupted save damages the volume's structures, and First Aid writes to the disk and can deepen the corruption while your data is still intact behind it. A drive that lights up but won't mount, with no physical damage, has a logical fault, not a dead mechanism. Stop replugging it to retry. Have it imaged and recovered from a copy, so the structures can be rebuilt safely.

Sending this in from Staines? Every case starts with a free diagnostic and one fixed written quote before any work — no fix, no fee. If the data is inside a laptop, PC, Mac or server, remove the hard drive or SSD and send us just the drive; we don’t provide an internal drive-removal service, and we don’t recover storage soldered to a motherboard (e.g. Apple Silicon Macs) — only drives that can be removed and sent to us. Post or courier tracked and insured to our Guildford Data Recovery lab — full sending instructions and the shipping form are here.
Start a free diagnostic

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.

// related case files

More cases like this one

Browse all case studies →

Got a device with a story like this?

Free diagnostic, fixed quote, no fix no fee — start now or call the freephone.