How to Check SSD Health on Windows, Mac, and Linux

Overview

A solid-state drive can feel perfectly fast right up until it starts throwing warnings, slowing under load, or dropping files because of a cable, enclosure, firmware, or NAND wear issue. That is why a proper SSD health check is less about chasing one single percentage score and more about building a repeatable process.

In practical terms, checking SSD health means looking at four things:

• SMART or health data, which reports wear, spare blocks, media errors, temperature, and other controller-level indicators.
• System-reported status, such as whether the operating system sees the drive as healthy, failing, or unsupported for detailed reporting.
• Real-world behavior, including unusually slow writes, disconnects, freezes, file system corruption, or boot delays.
• Context, such as whether the drive is internal or external, SATA or NVMe, connected through USB, Thunderbolt, or a direct motherboard slot.

One important note: SSD health reporting is not perfectly standardized. Two drives can expose different SMART attributes, and a utility may display one vendor’s fields more clearly than another’s. External SSDs can be especially inconsistent because some USB bridge chips do not pass full SMART data to the operating system.

So the goal is not to find a magic universal number. The goal is to answer three useful questions:

1. Is the drive reporting any sign of imminent failure?
2. Is the drive showing normal wear for its age and workload?
3. If something looks wrong, is the issue the SSD itself, the enclosure, the cable, the port, the file system, or the workload?

If you are also trying to understand performance complaints on a backup or portable drive, it can help to pair this health check with a broader slowdown diagnosis. See Why Is My External Hard Drive So Slow? Causes and Fixes That Actually Help for a workflow that covers connection bottlenecks and file transfer behavior.

Step-by-step workflow

Use this workflow on any SSD, whether it is your boot drive, a game library drive, or an external backup SSD.

1. Identify the drive and connection type

Before opening any health tool, note exactly what you are checking:

• Internal NVMe SSD
• Internal SATA SSD
• External SATA SSD in a USB enclosure
• External NVMe SSD in a USB or Thunderbolt enclosure

This matters because direct internal connections usually provide the most complete data. External enclosures sometimes hide or reduce SMART visibility. If a utility shows limited information for an external drive, the SSD may still be fine; the enclosure may just not expose all telemetry.

2. Start with the operating system’s built-in view

Built-in tools are useful because they are quick, safe, and available on almost any system. They may not expose every attribute, but they give you a first-pass answer.

Windows: basic SSD health check

On modern Windows systems, you can begin with the storage settings view if your version exposes health information for supported drives. You can also use command-line tools:

• PowerShell: Get a quick status using storage-related cmdlets where available.
• WMIC: On older setups, wmic diskdrive get status may return a simple status such as OK, but it is very limited and not enough for a serious diagnosis.

If Windows only shows a generic healthy status, treat that as a starting point, not a full verdict. You still want actual SMART details from a drive-aware utility.

Mac: basic SSD health check

On macOS, open System Information and review storage details for the internal drive if available. For external drives, information may be sparse depending on the enclosure. Disk Utility can help you verify volume structure and file system health, but it is not a full SSD wear-analysis tool.

For a quick terminal-based check on supported drives, diskutil info can reveal device details and interface information, which helps confirm whether you are dealing with a USB bottleneck or an internal PCIe device.

Linux: basic SSD health check

Linux typically offers the clearest low-level path. Start by identifying the drive with tools such as lsblk, nvme list, or fdisk -l. Then use SMART or NVMe-specific tools for detailed health data.

Linux users often have the easiest access to raw device telemetry, but the tradeoff is that you need to interpret it carefully.

3. Pull SMART or NVMe health data

This is the core step in any SSD health check.

On Windows

Use a reputable SMART utility that can display:

• Overall health status
• Temperature
• Power-on hours
• Total host writes or data written
• Percentage used or remaining life
• Reallocated sectors or spare block use, where reported
• Media or data integrity errors

Vendor SSD utilities can also be useful when available, especially for firmware checks and proprietary health reporting. If you are checking a gaming upgrade drive, understanding the interface first can avoid false expectations; NVMe vs SATA SSD: Real-World Speed Differences for Everyday Tasks is a useful companion read.

On macOS

macOS can be more restrictive for third-party low-level utilities than Linux, and external drives may reveal little through USB. If your preferred utility does not show complete SMART data, try these practical steps:

1. Confirm whether the SSD is internal or external.
2. Check whether the enclosure supports SMART pass-through.
3. If possible, test the SSD directly in another system or enclosure known to pass SMART data.

For internal Apple storage, health details may be abstracted compared with what you would see on a standard PC NVMe drive. In that case, lean more on system behavior, storage diagnostics, and backup discipline.

On Linux

Linux is typically the most straightforward:

• For SATA and many USB-attached devices: smartctl -a /dev/sdX
• For NVMe devices: nvme smart-log /dev/nvme0

Look for fields such as:

• Critical warning
• Percentage used
• Available spare
• Data units written
• Media and data integrity errors
• Unsafe shutdowns
• Temperature

If you are checking an external SSD and see errors accessing SMART data, the issue may be the USB bridge rather than the drive itself.

4. Interpret the important fields

The most useful SSD health values are usually these:

Overall health or SMART passed/failed
If a drive fails its overall SMART assessment or shows a critical warning, stop treating it as trustworthy. Back up data immediately and plan replacement.

Percentage used or remaining life
Some NVMe drives report wear as percentage used; others show remaining life. Different vendors present this differently, so read the label carefully. A high percentage used means more endurance has been consumed. This alone does not mean the SSD is about to fail, but it does show long-term wear.

Total host writes
This helps you compare real write volume against the drive’s endurance expectations. If you want more context on what endurance numbers really mean, SSD Endurance Explained: How to Read TBW and Pick a Drive That Lasts is worth reading alongside this guide.

Available spare and spare threshold
These fields matter on many NVMe drives. A healthy SSD keeps some spare flash capacity in reserve. If available spare drops close to its threshold, that is a real concern.

Media/data integrity errors
Any nonzero value deserves attention, especially if the number is increasing. One historical error is less alarming than a pattern that grows over time.

Temperature
Heat can affect stability and sustained performance. Short spikes are not the same as constant high temperatures during normal use. If your portable SSD runs unusually hot in a small enclosure, consider airflow, cable quality, and workload.

Unsafe shutdowns
This number can rise because of battery loss, power cuts, hard resets, or unstable enclosures. It does not necessarily mean the SSD is damaged, but repeated increases can help explain corruption or inconsistent behavior.

5. Verify file system health separately

An SSD can be healthy while the file system on top of it is not. If you have crashes, improper disconnects, or sudden power loss, run the file system checks your operating system supports:

• Windows: file system repair and error checking for the volume
• macOS: Disk Utility First Aid
• Linux: the appropriate fsck tool for the file system in use, typically when unmounted

This distinction matters. Drive health telemetry is one layer; volume integrity is another.

6. Run a light real-world performance sanity check

A benchmark is not strictly required to test SSD health, but it can help confirm that a drive is behaving roughly as expected. Do not focus on synthetic peak numbers alone. Instead, watch for:

• Very low write speeds compared with normal behavior
• Big drops after short bursts, especially on nearly full drives
• Random disconnects during transfer
• System freezes when the drive is under load

If you are shopping for a replacement because a portable drive is underperforming, Best External SSDs for Backup, Gaming, and Travel and External SSD vs External HDD: Which Should You Buy in 2026? can help narrow the next step.

7. Decide on an action level

After reviewing status, classify the drive into one of these buckets:

• Normal: SMART clean, no critical warnings, expected temps, no rising integrity errors.
• Watch closely: high wear, elevated temps, frequent unsafe shutdowns, or occasional odd behavior.
• Back up and replace soon: critical warning, SMART fail, growing media errors, repeated corruption, disconnects across systems, or severe instability.

Tools and handoffs

The best SSD health workflow uses more than one layer of checking. Here is a practical way to think about the tool stack.

Built-in OS tools

Use these first because they are fast and safe. They help with identification, connection type, and basic status. Their limitation is depth. They often tell you whether a problem is visible, but not why.

SMART and NVMe utilities

These are the main handoff from basic checks to actual diagnosis. On Linux, command-line tools are often enough. On Windows and macOS, graphical utilities can make interpretation easier, especially for external consumer drives.

If a utility cannot read an external SSD, do not immediately blame the drive. Try:

• A different USB cable
• A different port
• A different enclosure
• A direct internal connection, if practical
• Another OS, especially Linux, for confirmation

Vendor software

Vendor tools can be helpful for firmware updates, secure erase options, and proprietary health indicators. They are also useful when a generic utility shows ambiguous data. The tradeoff is that they usually only support that vendor’s drives.

System logs

Logs are where intermittent failures often become obvious. If SMART looks normal but the drive disconnects, timeouts, controller resets, or USB errors may show up in Event Viewer, Console, or the Linux journal. That is especially important for external SSDs, where the enclosure and cable can be as important as the NAND itself.

Backups as the final handoff

No health check replaces a backup. If the data matters, your workflow should end with verified copies in another location. For home users deciding between directly attached storage and a network backup target, NAS vs External Hard Drive: Best Backup Option for Home Users is a useful next read.

Quality checks

Before you conclude that an SSD is healthy or failing, run through these quality checks to avoid false positives and wasted replacements.

Check the connection path

An external SSD behind a poor cable or unstable hub can look like a dying drive. If the symptoms disappear after changing the cable, port, or enclosure, the SSD itself may not be the problem.

Check free space

Many SSDs slow down noticeably when nearly full. Low free space can also reduce the controller’s room for wear leveling and background cleanup. If the drive is close to capacity, free space before assuming permanent degradation.

Check thermals under the actual workload

A drive that behaves normally at idle but throttles during long writes may need better cooling, a different enclosure, or a lighter sustained write pattern.

Check trends, not one snapshots

A single SMART reading is useful; a series of readings is much better. Record the health status, total writes, temperature range, and any error counters. Recheck after a week or month. Rising error counters matter more than isolated historical numbers.

Check workload fit

Some drives are simply a poor fit for the job. A light-duty portable SSD used for constant video scratch work or game installs can wear or throttle faster than expected. If you are choosing a new drive for gaming or heavy transfer use, Best SSDs for PS5 and PC Gaming: Speed, Heatsinks, and Value can help frame what to prioritize.

Check the enclosure for SMART pass-through support

This is one of the most common reasons people think they cannot test SSD health. If the external enclosure does not pass SMART or NVMe telemetry properly, move the SSD into a better enclosure or test it internally if possible.

When to revisit

The most useful SSD health routine is scheduled, light, and repeatable. You do not need to obsess over the numbers, but you should revisit them at the right times.

Recheck monthly or quarterly if:

• The SSD stores important work or backups
• The drive is used heavily for writes
• The drive is older and has many power-on hours
• You noticed heat, throttling, or disconnect issues before

Recheck immediately if:

• Transfers become unusually slow
• The system freezes when reading or writing the drive
• The external SSD disconnects randomly
• You see file corruption or failed boots
• You had a series of unsafe shutdowns or power losses

Revisit the process itself when:

• Your operating system changes its storage menus or reporting behavior
• Your preferred SMART utility changes feature support
• You move a drive into a new enclosure or host system
• You adopt a new backup strategy and need better monitoring discipline

For a practical maintenance habit, keep a short note with:

• Date checked
• Drive model and serial
• Connection type
• Health result
• Temperature range
• Total writes or percentage used
• Any error counters
• Next review date

That simple log turns SSD health from guesswork into trend tracking. It also makes replacement decisions much easier because you can tell the difference between a one-time glitch and a drive that is clearly getting worse.

Finally, if your SSD shows a critical warning, media errors that keep increasing, or repeated instability across cables, ports, and systems, act first and investigate second: back up the data, reduce write activity, and plan a replacement. Health checks are most valuable when they help you move early rather than react after data loss.