Desk drives · job notes · HUL-2025-0315
It Beeps, and Reports a New Size Each Time.
The d2 lived under a desk in a Scunthorpe studio with four terabytes of finished mixes on it — local bands, choirs, live sessions — and one morning it stopped spinning and took to beeping. What size it claimed depended on when you asked. Disk Utility put it at 750GB and would not mount it
, then later the size column came up blank
. On a colleague's laptop it read 0 bytes, needs initialising
. Fresh leads and a different dock changed none of it.
Sounds like yours? Ring us.
0800 6890668
What causes it.
A drive keeps its own particulars on the platters. Capacity, model string, defect tables — all of it lives in service areas on the discs, and none of it can be fetched while the discs are still. A stalled drive therefore has nothing true to hand over. It invents something instead, a different answer on each connection, and not one of those answers will mount. The beep is the same deadlock out loud: the motor pulls, fails to shift the pack, gives up, pulls again. What is holding it, nearly every time, is the head stack itself, resting on a platter rather than parked clear of the edge.
The tools this one needed.
The steps we follow →| The gear | What this one did | Why we have it |
|---|---|---|
| PC-3000 Data Extractor | Took the full image inside the one spell of steady spinning we had | Copying is run at firmware level, with the PC-3000 in charge |
| ACE Lab PC-3000 Express | Read the true model string and the defect tables once the heads were clear | Reaches the vendor service commands an ordinary ATA connection cannot |
| R-Studio Technician | Put the HFS+ volume right, so each session landed back in the studio's own folders | Handles almost any file system, and puts RAID sets back together |
The stages.
The beep had already said what was wrong
Other leads, a second dock and a different computer had all been tried before it came in, and each gave the same beep. That leaves the fault inside the aluminium case. A current trace confirmed the rest: two seconds of heavy draw while the motor hauled at something solid, the protection then cutting in, and the whole cycle starting over.
Lift the heads clear, then carry straight on
Under filtered air the stack was lifted off and parked, and each slider went beneath the scope. Nothing was marked on the surfaces underneath, which is never a thing to assume in advance. Back on power it named itself correctly — 6TB, the right model string, the firmware we were expecting. The imager stood configured and ready, so the copy started at that point.
Spin it up once, and do the rest on the copy
The read ran end to end and the power stayed on throughout, since a stack that lands once does not always lift again. With the image secure, the drive went into a box. Fixing the volume and sorting out the folders was all done on the copy.
How it finished.
Four terabytes went out on new media: filenames, dates and folder structure exactly as the studio kept them. What made that possible was the decision to stop at the very first beep. Nothing had been dragged over the surfaces, so every mix plays back the way it was cut.
What people read after this.
Tagged Desktop externals too.
Is yours doing the same?
Turn it off. Send it to us. The diagnosis comes first. It says which files are still readable and which are not.