Data Recovery Case File · Mac Workflows · The Spinning Wait
The beachball was the drive, not the Mac: a mid-transfer stall decoded, the forced restart absolved — and the project files brought home
His sequence is one every Mac user recognises and few can translate. Working on a project, transferring files from one hard drive to another, when "unfortunately one hard drive became unresponsive and would not open. I am a Mac user and the multi-coloured circle appeared. The drive would not eject. I was left with no alternative but to restart my machine." After the restart: the drive "just won't appear" — different leads tried, different machines tried, the elimination complete. The patient: a WD My Passport, 1TB. His ask: a quote for recovery, if possible. Possible — and the decode matters beyond his case, because the spinning wait cursor mid-transfer is one of the most misread moments in Mac life: it looks like the computer struggling. It's almost always the drive.
| Device | WD My Passport 1TB — one side of an active two-drive project transfer; unresponsive mid-copy |
| Reported sequence | Transfer stalls → persistent wait cursor on any access → eject request never completes → forced restart (the only available exit) → drive thereafter invisible; cables and machines eliminated |
| Fault class | Drive failure surfacing under sustained transfer load — the stall, the failed eject and the post-restart silence one continuous event |
| Equipment used | laminar flow bench · donor components as required · ACE Lab PC-3000 Express + Data Extractor |
The decode: what the beachball reports, why the eject couldn't finish — and the restart's full absolution
The wait cursor, translated: the multi-coloured circle means an application is waiting on something that hasn't answered — and when it appears the moment you touch a particular drive, the unanswered party is that drive: reads were issued, the drive stopped returning them, and the system politely spun in place rather than admit the conversation had died. A beachball that follows one specific disk around is not a busy Mac; it's a failing drive holding the session hostage, mid-sentence. Why the eject hung too: ejecting isn't just letting go — the system must finish outstanding operations and write closing bookkeeping to the volume before it releases it, and a drive that has stopped answering can't complete either; the eject request joins the same queue of unanswered business and waits forever alongside everything else. So his two symptoms were one symptom: nothing that needed the drive's cooperation could finish, because the drive had stopped cooperating. The forced restart, formally absolved: "left with no alternative" is exactly right — with the drive unresponsive and the eject impossible, the restart was the only exit the situation offered, and the crucial mechanical fact is that it changed nothing: the drive hadn't been answering before the restart; the failure predates the button. (The post-restart invisibility isn't the restart's harvest — it's the same failure, now visible from the outside instead of from inside a stalled copy dialog.) The timing deserves its usual note: a file transfer is sustained, continuous drive work — precisely the load this archive keeps finding at the scene when marginal drives finish — so "failed mid-transfer" parses as "finished during the workout," with the project transfer holding the stopwatch, not the weapon. His elimination afterwards (leads, machines) was the correct cheap sweep, and its unanimous silence completed the referral his beachball had started.
The recovery
The bench met the drive where the transfer had left it: a mechanism that had failed under load, confirmed under laminar airflow and restored with matched donor attention, the platters clean — the stall-and-stop sequence, for all its drama at the desk, having been mercifully brief in mechanical terms. The PC-3000 then ran the sustained read the drive could no longer survive in the wild, under management: the terabyte imaged with cooperative territory banked first and the load-worn regions negotiated last, coverage closing in the high ninety-nines. The volume mounted whole from the image, and verification honoured the enquiry's context: the project files — including the transfer's in-flight population, intact to the stall — opened and confirmed first, the remainder following. Delivery went out on new media in duplicate, with the report's closing line finishing the absolution in writing: failure preceded and caused the stall; the forced restart neither contributed nor could have been avoided; the transfer was the audience, not the author.
Outcome
The project home, the beachball translated, the restart forgiven — and the filings for the next Mac user watching the circle spin over a copy dialog right now. Follow the beachball to its source: a wait cursor that appears only when one drive is touched has named the patient — stop issuing that drive work (each click queues more unanswered reads), give the eject one fair chance, and accept the forced restart without guilt when it doesn't come; the drive stopped first. Treat transfers as workouts: big copies are sustained load, the classic finisher of marginal drives — which is an argument for keeping transfer sources and destinations young and healthy, and for reading any mid-copy strangeness (slowing, stalling, one beachball) as the stop signal rather than a hiccup. And bank his aftermath discipline: leads, machines, then enquiry — no repair apps aimed at an invisible drive, no repeated restarts to check again. The circle spun because the drive went quiet. Everything it was carrying is speaking again.
Beachball every time you touch one drive
That drive is the patient: stop clicking into it, try one clean eject, and if the eject hangs, the forced restart is legitimate — the failure already happened. Afterwards, do the cheap sweep once (cable, port, second machine) and stop at unanimous silence; don't run recovery apps against a drive that isn't appearing. Note what it was doing when it stalled (transfers and backups are the classic loads) and bring the sequence to the enquiry — mid-task failures recover well when the retries stop early.
The drive stopped first — call Belfast Data Recovery on 028 9002 0144; the in-flight files usually made it.
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.