What the Noises Mean
A drive making noise is a drive asking you to stop. Here is what each sound means, and why the answer is always the same.
01The Sounds, Translated
Clicking. The read/write head is failing to find its target track and resetting — a cycle called a seek error or, in the worst cases, the "click of death." Each click is an attempt that failed. The actuator arm swings, finds nothing, and returns to its home position to try again. A drive can survive a handful of these; it cannot survive thousands. If you are hearing rhythmic clicking, the drive is already in distress.[1]
Ticking or tapping. Softer than a full click, but just as serious. Lighter ticking usually means the heads are struggling to read individual sectors — the drive is retrying at the hardware level, grinding against bad spots on the platter surface. Sometimes this is early-stage media degradation; sometimes it is a head that is partially damaged and skipping over the surface intermittently.
Grinding or scraping. The most urgent sound. This is physical contact — head touching platter, or a bearing beginning to fail. Grinding means surface damage is happening right now, and every second the drive spins, it may be overwriting the very data you need to recover. Power it off.
Repeated spin-up retries. The drive powers up, spins, then spins down and tries again — sometimes several times before mounting, sometimes never. This points to a failing spindle motor, a power-delivery problem, or the drive's internal firmware deciding it cannot pass its own startup checks. Either way, the drive does not trust itself, and neither should you.
Beeping. Rare, but distinctive: a high-pitched beep from a portable drive almost always means the spindle motor is seized and the USB port cannot supply enough current to unstick it. The drive is not just sick — it is mechanically locked.
Either way, the drive does not trust itself, and neither should you.
02The Answer Is Always the Same
None of these sounds call for a repair tool, a restart, or an attempt to copy files one by one. Every one of them calls for the same response: stop writing to the drive immediately, make a full sector-level image before attempting anything else, and work only from that copy. If the noise is grinding or the motor is seized, skip the imaging step yourself — that job belongs in a cleanroom.
Notes from the bench
- [1]
A drive can survive a handful of failed seeks. It cannot survive thousands, and it counts faster than you can decide. ↩