If you’re installing Ubuntu on an old laptop or building a new Linux box, the drive you pick matters more than almost any other hardware decision short of RAM capacity. Ubuntu runs fine on a hard drive, but the difference between an HDD and an SSD is the difference between a desktop that feels broken and one that feels instant. Here’s what actually changes, and when the cheaper drive is genuinely good enough.
Boot time and general responsiveness
On a 5400-7200RPM HDD, a typical Ubuntu install (22.04 or 24.04, GNOME desktop) takes 25-45 seconds from GRUB to a usable desktop, longer if you’ve got a pile of startup apps or snap packages, which are notoriously slow to launch from spinning disk because of how they mount squashfs images. On a SATA SSD that drops to 8-15 seconds. On NVMe it’s often under 7 seconds, and the gap feels even bigger in daily use than the raw numbers suggest, because every “nautilus is loading” or “apt is unpacking” moment on an HDD involves the drive head physically seeking across the platter.
Random read/write performance is the real story here, not sequential throughput. Ubuntu’s package system, snap/flatpak runtimes, and systemd itself hammer the disk with lots of small file operations during boot and app launches. HDDs are terrible at this: 75-100 IOPS is normal. A budget SATA SSD does 20,000-50,000+ IOPS. That’s the number that actually explains why the OS feels different, not the sequential MB/s on the box.
Side-by-side numbers
| Metric | HDD (7200RPM) | SATA SSD | NVMe SSD |
|---|---|---|---|
| Cold boot to desktop | 25-45s | 8-15s | 5-9s |
| Random 4K IOPS | 75-100 | 20,000-50,000 | 100,000-500,000+ |
| Sequential read | 120-180 MB/s | 450-550 MB/s | 1,500-7,000 MB/s |
| Typical price per TB (2024-25) | $18-25 | $40-55 | $45-70 |
| Rated lifespan under load | 3-5 years MTBF, fails gradually | 5-10 years, fails predictably via wear | 5-10 years, same wear mechanism |
Package management, compiling, and swap
If you use Ubuntu for development, this is where the SSD pays for itself fastest. apt upgrade on a system with a few hundred packages to update can take 2-4x longer on HDD, mostly from the dpkg unpack/configure step hitting thousands of small files. Compiling anything of real size, a kernel, a large C++ project, Chromium even, turns into an exercise in patience on spinning disk because the build system is constantly reading and writing object files and headers. On SSD those builds are frequently 30-50% faster for I/O-heavy stages.
Swap behavior also changes the calculus. Ubuntu defaults to a swap file or small swap partition, and if your system is RAM-constrained (8GB or less) and swapping actively, an HDD swap means multi-second stalls when memory pressure hits, while SSD swap is barely noticeable. This is one of the strongest arguments for not pairing a modern Ubuntu desktop with 8GB of RAM and a hard drive.
How each one actually fails
HDDs fail mechanically: bearing wear, head crashes, bad sectors that spread, and the classic “clicking” sound that means stop using it immediately and image what you can. Failure is often sudden after a period of warning signs (SMART reallocated sector counts climbing, slow reads on specific files). They also hate being moved while spinning, which matters if this is a laptop drive.
SSDs fail differently: NAND cells wear out from write cycles, and failure tends to be more predictable if you’re tracking SMART data (specifically the wear leveling / media wearout indicator), though controller failures can also kill a drive outright with no warning. For a typical Ubuntu desktop or laptop doing normal use, actual write endurance is a non-issue. You’d need to write tens of terabytes a day for years to wear out even a budget drive from write cycles alone, and most people never get close to that. The exception is a server-type workload or a system running a database with constant write amplification, where you’ll want a drive rated for higher endurance (checking the TBW spec on the listing matters more than the brand name).
What to actually buy
For a daily-driver Ubuntu install, a 500GB-1TB SATA SSD is still the sweet spot for most people, cheap enough to not think about and fast enough that you won’t notice the ceiling versus NVMe in everyday desktop use. If your motherboard has an M.2 slot and you’re buying new anyway, an NVMe SSD isn’t much more expensive and removes any doubt. If you’re working with an older laptop that only has a SATA port, a straightforward SATA SSD upgrade is one of the highest value-per-dollar changes you can make to that machine.
Where an HDD still makes sense: bulk storage. Media libraries, backups, archives, anything you’re not booting from or compiling on. A 4TB internal hard drive costs a fraction of equivalent SSD capacity, and spinning disk is perfectly fine for sequential reads of large files like video. The mistake is putting your root filesystem on it. A common and sensible setup is a smaller SSD for Ubuntu and your home directory’s active files, with a larger HDD mounted for storage that doesn’t need to be fast.
If you’re migrating an existing Ubuntu install from HDD to SSD rather than doing a fresh install, clone the partition with something like dd, Clonezilla, or GParted’s copy function, then resize the filesystem to fill the new drive and update /etc/fstab with the new UUID (find it with blkid). It’s a 30-minute job for most desktop installs and avoids reinstalling everything from scratch.
