Case file · Desktop externals · BDR-2025-0315
It Beeps and Shows the Wrong Size.
A 4TB Samsung D3 began to beep instead of boot, and its self-description fell apart: sometimes shows up as 3000GB in Bios
, sometimes as 3.5gb with a need to initialize
— an initialise that failed on an Input/output error
. The owner had already pulled it from its case and tried it internally. Behind the noise: three terabytes of music.
Same symptoms on your desk?
01273 964902
The decode.
Beeping is a motor being commanded to spin and physically unable to. Two mechanisms produce it: heads that have settled onto the platter surface instead of parking on their ramp, or a spindle that has seized. The wildly inconsistent capacities follow directly — a drive that never completes spin-up never reads its own identity data, so it reports whatever partial nonsense the bridge can scrape, and the initialise prompt fails because there is nothing behind it to initialise.
Equipment on this case.
How a case runs →| Platform | What it did here | Why this tool |
|---|---|---|
| PC-3000 Data Extractor | Imaged the drive during the single window in which it was reliably spinning | The imaging half of the PC-3000 platform, driven by the firmware half |
| ACE Lab PC-3000 Express | Read the identity and defect structures once the mechanism was turning | Speaks the vendor-specific commands that sit outside the standard ATA set |
| R-Studio Technician | Reconstructed the NTFS volume and the music library's folder tree | Broad filesystem coverage and dependable RAID reconstruction |
On the bench.
Diagnose the beep before touching the enclosure question
The owner's de-casing had changed nothing about the fault, which was useful information in itself: the problem was internal, not the USB bridge. Bench power monitoring showed the motor drawing current, straining, and being cut off by the drive's own protection — a stalled spin-up, repeated.
Free the mechanism, then don't switch it off
The head stack was released from the platter surface and the mechanism checked for the drag that had caused the stall. The moment the platters turned freely, the drive identified correctly as 4TB for the first time in weeks. That window is the whole opportunity on a stalled drive, so imaging started immediately and ran without interruption.
One continuous pass, then rebuild on the copy
The drive was imaged straight through in that single session rather than being powered down and revisited — every additional spin-up on a drive that has already stuck is a fresh chance to stick again. The filesystem was then rebuilt from the image and the library's folder structure restored intact.
The outcome.
The music collection transferred complete to new media, folder structure and metadata intact. The owner's internal-connection experiment had, mercifully, changed nothing that mattered — though it had spent several more spin-up attempts than the drive could really afford.
Related on the index.
More from Desktop externals.
Recognise your own drive in this story?
Same rule as every case above: power it down, and let the diagnosis be free before any decision has to be.