Data Recovery Case File · Desktop Externals & Aging Drives · The Longest Continuous Write
Drive That Failed Partway Through an Export
His enquiry traced the collapse in the order it happened, which is exactly what makes it readable. A WD 4TB external drive: "I was using video editing software. I went to export a video but it reached a certain point and ended up crashing the app. It then proceeded to crash the file manager on the MacBook, and then eventually crashed the Mac. Since then I have been unable to fully access the files without running into more crashing issues. I am still able to see the files, however some folders are taking a significant time." That cascade — application, then file manager, then the whole machine — is not three faults. It is one drive failing to answer, and progressively larger pieces of software waiting on it. And the operation that exposed it is the most demanding thing he could have been doing.
| Media | WD 4TB external hard drive used for video editing — failure during a long export; host applications and operating system subsequently hanging on access; folder listings slow but present |
| Reported situation | Export progressed then crashed the editing application · file manager and then the operating system subsequently hung · files still visible but access unreliable · directories slow to enumerate |
| Fault class | Progressive media degradation exposed under sustained write load — reads stalling long enough to hang the host; metadata still largely readable |
| Equipment used | Host access halted · assessment on diagnostic instruments rather than a computer · Atola Insight Forensic surface and error-rate mapping · PC-3000 Express with Data Extractor prioritised imaging under per-sector timeouts · project files verified by opening |
The decode: why an export is the hardest test, and what the cascade means
Why exporting finds failing drives: most drive activity is short and intermittent — open a file, save it, copy something, idle. A video export is neither. It reads source footage continuously while writing a large output file, sustained for many minutes or hours, with no pauses in which a struggling drive can recover. It is the closest thing to a stress test that ordinary use provides. So a drive with marginal regions can serve everyday work for months and fail at exactly this moment — which is why this archive sees the same pattern with backups, bulk transfers and operating system upgrades. The export did not damage the drive; it was the first operation demanding enough to reveal it.
What the cascade actually was: the three crashes look like three problems and are one. When software requests data, the request goes to a storage driver which asks the drive and waits. On a failing drive the answer may never come. The editing application blocked first, because it was asking hardest. The file manager blocked next, because it was asked to display the same location. Then the operating system halted, because a core component waiting indefinitely cannot safely be left. So the escalation traces the fault outward from whatever touched the drive most — and every one of those crashes is evidence about the drive rather than about the software.
What "files visible but folders slow" tells us: a hopeful detail. Directory information — names, sizes, dates — is small and stored in a concentrated area; file content is spread across the whole surface. He can still see files, so the concentrated region reads. Folders taking a long time means even that region is being retried. It is a drive in progressive decline rather than one that has stopped, and the window for a clean image is closing while it is used.
Why continuing to browse is expensive: each attempt to open a folder or copy a file is not a quick failure — the machine waits, retries, and keeps the drive working on its weakest ground for as long as it takes to give up, then often crashes and power-cycles it abruptly. An afternoon of trying to rescue files by hand is an afternoon of concentrated punishment. The drive should come off the machine entirely.
On the bench
The drive was not connected to a general-purpose computer again. The Atola Insight Forensic assessed surface condition and error rates directly — where a drive that fails to answer stalls nothing and damages nothing further — turning his crashes into a measured map of where reads still succeeded. Imaging followed on the PC-3000 Express under Data Extractor with per-sector timeouts enforced, which is the decisive difference from what his Mac had been doing: a failing sector is given a strict budget and deferred rather than retried until something hangs. The healthy expanse was captured first, weak neighbourhoods revisited on later passes, and his project files and footage verified by opening and playback.
The outcome
The drive assessed and imaged on instruments that tolerate a stalled read, with the project material verified and delivered. 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, for anyone whose drive failed during an export: a long export is the most sustained demand ordinary use makes of a drive, so it is where marginal drives fail — the export exposed the fault rather than causing it; an application crash followed by the file manager and then the machine is one drive failing to answer with progressively larger software waiting on it, not three separate problems; files still listing while folders crawl means the small directory region reads and the wide content area is struggling; and every further browse is a prolonged retry on the weakest ground.
Drive that crashed your machine during an export or render
Disconnect it and stop trying to rescue files by hand. That cascade — the application freezing, then the file manager, then the whole machine — is one drive failing to answer while progressively bigger pieces of software wait on it, and each attempt keeps the drive grinding away on its weakest areas for minutes before crashing and abruptly power-cycling it. Browsing folders to see what's still readable is one of the most expensive things you can do. Take some encouragement from what you can still see: if files list at all, the small concentrated directory area is readable and only the spread-out content is failing, which is a drive in decline rather than one that has stopped. Don't run repair utilities or disk checks, don't try it on a second machine, and don't leave it connected hoping a copy completes.
Take it off the machine — call Glasgow Data Recovery on 0141 404 0294; assessed on instruments that tolerate a stalled drive, imaged under per-sector timeouts, footage verified by playback.
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.