Plug the drive in and it sounds almost normal: the motor spools up, maybe there’s a little head activity — and then it spins back down. Silence. Sometimes it retries on its own; sometimes it just sits there until you power-cycle it and the loop repeats.
A spin-up-then-stop cycle is the drive failing its own startup sequence and deliberately shutting down. Understanding what happens in those few seconds tells you what’s wrong.
What a drive does in its first seconds
At power-on, a drive runs through a fixed routine: spin the platters to speed, unpark the heads, and — this is the part most people don’t know — read its own firmware off the platters. Only a small bootloader lives on the drive’s circuit board; the bulk of a drive’s operating instructions is stored in a reserved area of the platters called the service area. Then it calibrates and reports ready.
A drive that spins down partway through this sequence hit a step it couldn’t complete:
It can’t read its service area. If the heads can’t read the firmware zone — because a head is weak or the service area itself has degraded — the drive aborts and parks. This is common on several drive families with known service-area weaknesses. The data platters may be in perfect shape; the drive just can’t finish booting itself.
A head failed its check. Drives test their heads during startup. Some models respond to a failed head by refusing to come ready and spinning down rather than clicking. Same root cause as a clicking drive, politer symptom.
The motor can’t hold speed. A degrading bearing spins up but can’t stabilize, and the drive gives up. Rarer, and usually preceded by the drive running hot or loud.
It’s not getting stable power. The one cheap cause: a weak USB port or failing enclosure power supply can brown the drive out right at the moment of peak startup draw. Desktop external drives with power bricks deserve a new brick test before any darker conclusions — bricks fail far more often than motors.
What to do
Try the power test first: different cable, different port, powered directly rather than through a hub, replacement power brick if it’s a desktop external. That’s the whole extent of safe DIY here.
If it still cycles on clean power, stop power-cycling it. Each spin-up on a drive with a weak head or degrading service area is another chance for the marginal component to finish failing. The pattern I see too often: drive spins down, person retries it thirty times over a weekend of googling, and by Monday a recoverable drive has become a difficult one.
Free evaluation. Firm quote before any work begins.
What recovery looks like
Spin-down cases are firmware-and-heads territory. Service-area problems can often be worked around by repairing the firmware structures or reading around the damaged modules — specialized work, but with good outcomes. Head weakness means careful imaging that reads the drive gently and doesn’t insist on the failing head doing more than it can. These land in the middle-to-upper part of my $150–$500 range depending on what the evaluation shows, and cases needing physical head replacement get an honest referral to a cleanroom lab instead of an attempt they can’t afford.
The bottom line
A drive that spins up and quits is telling you it failed a specific startup step — usually reading its own firmware or checking its heads. It’s also telling you it still spins, which is genuinely good news for recovery. Keep it that way: stop the retry loop, note what it does, and get it evaluated.
Drive spinning up and shutting back down? Start a case — describe the exact sound sequence and how many seconds it runs, and I’ll tell you what that pattern suggests.