Plug-in drives · case notes · BHD-2025-8315
It Beeps, and the Size Is Never the Same.
A d2 under a desk at a Solihull studio held four terabytes of masters — choirs and brass bands — and it had stopped turning and taken to beeping. Ask what it was and the answer moved each time: 750GB in Disk Utility, and it would not mount
, then a row where the size was blank
, and on a colleague's PC zero bytes, not initialised
. Fresh leads and a different dock made no difference.
Sounds like yours? Give us a ring.
0800 6890668
What that means.
A hard disk holds no memory of its own size. Capacity, model string and defect lists all live in service areas written onto the platters, and none of it can be fetched until those platters are moving. Hold the pack still and the drive has nothing to report, so the host gets a different invention on each connection and not one of them is mountable. The beeping is that same deadlock heard from outside: the motor pulling, failing to break the platters loose, resting, pulling again. What pins them is nearly always the head stack, sat down on a surface instead of parked off at the edge.
What did the work here.
The order of the work →| Equipment | The job it did | What it adds |
|---|---|---|
| PC-3000 Data Extractor | Took the entire image inside that single spell of steady spin | Reads the disk from inside its firmware, using the PC-3000's imager |
| ACE Lab PC-3000 Express | Recovered the real model identity and defect tables once the heads were off | Gets at the factory service commands that standard ATA cannot carry |
| R-Studio Technician | Repaired the HFS+ volume so every session came back where the studio filed it | Broad file-system support, with RAID rebuilds that can be trusted |
What we did.
Trust the beep — the trouble was inside the shell
Cable, dock and computer had all been swapped before it reached us, and each swap produced the identical beep, which ruled out everything beyond the aluminium case. A current trace closed the argument: two or three seconds of heavy draw as the motor pulled against something that would not move, then the protection tripping, then round again.
Get the heads off the platters, then keep going
Working in filtered air, the stack was lifted onto its parking ramp and the sliders put under the scope; the surfaces beneath were unmarked, which is never something to assume ahead of time. Given power again the drive introduced itself properly — the full 6TB, the right model, the firmware we expected — and the imager, set up in advance, was started.
One session on the drive; everything else off the copy
The read went start to finish without the power being dropped once, since a stack that has landed already may not come up a second time. Once the image was safe the drive was finished with; mending the volume and sorting folders was all done on the copy.
How it closed.
The whole four terabytes landed on new media with filenames, timestamps and folder structure just as they had been recorded. That is down to the choice he made to stop at the first beep: nothing had scored the surfaces, and the mixes came back sounding as they did on the day.
Other pages worth a look here.
Others under Desktop externals.
Is yours behaving the same way?
Switch the device off, post it in, and decide nothing until the diagnosis comes back to tell you where you stand.