Desktop drives · bench record · PLY-2025-0315
Every Plug-In Brought a Beep and a Different Capacity.
Four terabytes of finished mixes sat on this d2 under a desk in a Camborne studio — bands, choirs and live sessions built up over years — until the morning the platters stayed put and a beep took their place. Ask it twice and you got two answers. 750GB, according to Disk Utility, and it would not mount
, and then the size column showed nothing at all
. Plugged into a colleague's machine it offered 0 bytes, needs initialising
. New leads and a second dock made no difference.
Sounds like yours? Talk it through.
0800 6890668
Why it happens.
The particulars a drive reports about itself are not held in its electronics. Capacity, model string, defect tables: those live in service areas on the discs themselves, and no part of them can be read while the discs are still. A drive that will not turn therefore has no truthful answer available. It offers an invented one, different on each attempt, and not a single version of it will mount. You are hearing the same deadlock through the case — a hard pull from the motor, no movement in the pack, a pause, then another pull. Nine times out of ten the obstruction is the head stack, settled onto a platter rather than sitting out on its ramp.
The kit this job called for.
How the job runs →| The kit | What it did here | Why we keep it |
|---|---|---|
| PC-3000 Data Extractor | Captured the whole image during the single stretch of reliable rotation available | The PC-3000 runs the copy through the drive's own firmware |
| ACE Lab PC-3000 Express | With the heads lifted clear, pulled the genuine model string and the defect tables | Drops the disk into its maker's service mode, out of reach over plain ATA |
| R-Studio Technician | Put the HFS+ volume back in order, returning each session to the studio's own filing | Reads nearly every file system, and rebuilds RAID sets from images |
How it ran.
What the beeping had told us before it arrived
Different leads, a second dock and another computer had already been through before the parcel reached us, and every one produced the same noise. That puts the trouble inside the aluminium body. A current trace settled the rest: a couple of seconds of heavy draw as the motor strained at a pack that would not budge, protection then cutting in, and the sequence starting over.
Get the stack off the surfaces and keep going
In filtered air the stack came off and went to its park position, and every slider was examined under the microscope. The platters below carried no marking, and that is not an outcome to count on before you look. Powered again, the drive gave its own name properly — 6TB, the correct model string, the firmware revision we expected. The imager had been set up in advance, so copying began there and then.
One spin-up, and everything after that on the image
The read ran to completion with the supply held on throughout, since a stack that has settled once may well not lift again. With a good image in hand, the drive was boxed up. Repairing the volume and putting the folders in order happened entirely on the copy.
How it ended up.
Four terabytes travelled home on fresh media, with filenames, dates and folder tree exactly as the studio had built them. The reason it worked was that somebody stopped at the first beep rather than the tenth. Nothing had been hauled across the recorded surfaces, so each mix plays back as it was cut.
Pages people open after this.
Also tagged: desk drives.
Seeing the same thing?
Leave it switched off and post it in. Nothing happens until the diagnosis, which lists what can still be read and what cannot.