a hard disk drive
/ HDD /
Picture an old jukebox or a record player, but with several shiny records stacked on one spindle, all spinning together very fast. A tiny arm carries a needle that can swing in to any track and read the music etched there. A hard disk drive works on the same idea, except the 'records' are smooth metal platters coated with a magnetic film, the 'music' is your data stored as tiny magnetised spots, and the needle is a read/write head that floats a hair's breadth above the surface.
Concretely, inside the sealed case are one or more rigid platters mounted on a spindle that spins constantly (commonly 5400 or 7200 revolutions per minute). Each platter surface is divided into concentric rings called tracks, and each track into small arcs called sectors (traditionally 512 bytes, now often 4 KB), which are the smallest units the drive reads or writes. A read/write head, one per surface, is mounted on a single moving arm. To read a given sector the drive must do three things in order: move the arm so the head sits over the right track (seek time), wait for the spinning platter to bring the wanted sector under the head (rotational latency), then read the bits as they pass by (transfer time). Because all heads move together, the matching tracks at the same arm position across all platters form a vertical set called a cylinder.
Why it matters: an HDD is mechanical, so its speed is dominated by physical movement, not electronics. A random access that needs a long seek and a half-rotation wait can take around 10 milliseconds — an eternity to a CPU. This single fact is why disk scheduling algorithms exist (to cut total arm movement), why sequential access is vastly faster than random access on a disk, and why so much OS design tries to avoid touching the disk. SSDs, with no moving parts, change this calculus completely.
A 7200 RPM drive spins once every about 8.3 ms, so its average rotational latency (half a turn) is about 4.2 ms. Add an average seek of about 9 ms and one random read costs around 13 ms — in that same time a 3 GHz CPU could have executed tens of millions of instructions.
Mechanical movement, not electronics, sets a disk's pace.
A common misconception is that disk capacity and disk speed go together. They do not: a huge disk can be slow because random access still pays the same mechanical seek-and-rotate cost no matter how many bytes it holds.