To check a drive's health, use the Benchmark and Diagnostics tab in S.A.K. Utility: on the Diagnostics sub-tab, click Scan SMART. The app reads each drive's built-in health report, called SMART, and shows PASS, WARN, or FAIL. Check Disk Errors, on the same sub-tab, separately scans each drive's file system.
When to use this
Use this when a PC is slow, freezes, or makes odd drive noises, before you trust an old drive with new data, or when you are about to back up or sell a machine.
What you need
- Administrator rights. Check Disk Errors asks for them with a Windows prompt. Scan SMART does not ask. Without them Windows usually lets it read an NVMe drive but not a SATA or USB one, so click Run as Admin first.
Steps
Read the drive's health report
Click Run as Admin in the status bar, and approve the Windows prompt.
Open the Benchmark and Diagnostics tab.
Click the Diagnostics sub-tab.
In Storage Health (S.M.A.R.T.), click Scan SMART.
Read the table. Each drive is named by its Windows number and model, such as PhysicalDrive0 (Samsung SSD 980), so two drives of one model can be told apart. Any warnings appear in text below it, each starting with the drive it is about. A drive the app could not read still gets a row, and the text below says why.
One row for each drive the app could read
Scan for file system errors
On the Diagnostics sub-tab, go to System Maintenance.
The four maintenance tools Turn on the Log switch at the bottom of the tab to see the messages.
Click Check Disk Errors. It starts straight away.
Approve the Windows prompt if one appears.
Read the result in the log, such as Scanned 2 drives: 0 errors, 0 repairs recommended, followed by a report for each drive. The status bar only says Completed or Failed.
The totals, then one entry for each drive
What the health report means
Health column:
Point at a Health value to see why, in the drive's own terms.
- PASS: the drive reports no problem, and nothing it counts has reached the app's warning levels.
- WARN: the drive's own check passes, but it counts something worth watching: reallocated, pending or uncorrectable sectors, cable errors, an NVMe SSD at 80 percent or more of its rated life, or NVMe media errors. Back up important data, and check the drive again soon.
- FAIL: the drive itself says it is failing: its own SMART self-assessment failed, a SMART value is past the failure threshold the drive sets, or an NVMe SSD's spare capacity is below its own threshold. Back up the drive now and plan to replace it.
- N/A: the app could not judge the drive's health, because it could not read the drive or what it read was not enough. Temp and Hours then show N/A. This is not a clean result.
Other columns:
- Type: how the drive connects, such as SATA, NVMe or USB, as the hardware scan names it from the bus Windows reports. A drive in a USB enclosure shows USB, whatever is inside. Scan SMART asks Windows for the bus itself, so it does not wait for a hardware scan. Only when Windows names no bus does it show what smartctl reports.
- Temp: the current temperature.
- Hours: the total hours the drive has been powered on.
- Wear: the share of rated life used on an NVMe SSD. Other drives show N/A.
The text below the table also flags a temperature over 55 C and more than 50,000 powered-on hours. These do not change the Health column, so read them even when it says PASS.
How it works
Scan SMART runs a bundled copy of the open-source smartctl tool, which only reads from the drive. Scan Hardware on the same sub-tab starts this scan by itself when it finishes.
Check Disk Errors runs Windows' online volume scan on every writable local volume with a drive letter, and reports the result the scan returns for each one. An NTFS drive Windows calls removable, such as an NTFS USB stick, is the exception: Windows cannot take the snapshot its online scan needs on such a drive, so S.A.K. takes the volume offline and runs a read-only chkdsk, the same check as Check File System in Partition Manager. After each drive, S.A.K. waits 15 seconds before it reports, because Windows can crash if a disk is removed seconds after a check. Leave the drive plugged in until the run ends. Mapped network drives are left out, because the scan cannot reach them, and the report says so: it names each one it can see as skipped, and always ends by saying network drives are not checked. A FAT, FAT32 or exFAT drive, such as most USB sticks, is left out too, because the online scan reads NTFS and ReFS only: the report names it as not checked, with the file system and the read-only chkdsk command to check it instead. The summary counts it with the drives that could not be checked, and the result names it, such as (U: is FAT32), but it does not count as a failure. A drive that could not be checked is always named, with the reason. It never schedules a repair. Each drive's entry in the log shows one of these:
- No errors found.
- Errors found and fixed by Windows while the drive stayed online. The file system did this itself during the scan. Nothing further is needed, though it is worth asking why it happened.
- Errors found with Repair recommended. Windows needs a repair to fix them.
- A line with the scan's own result word, such as
ScanNeedsRetry. The scan gave no answer about the drive, so it counts as not checked. - No errors found (read-only chkdsk). A removable NTFS drive that chkdsk read without changing anything.
- Errors found by a read-only chkdsk, which fixed none of them, with Repair recommended.
- Not checked (D: is in use, so it was not checked. Close the files and programs using it, then check it again. Nothing was changed.) Something had the removable drive open, so it was not read. Close it and run the check again.
- Scan failed (Windows could not take the snapshot it reads D: through, so D: was not checked. Nothing was changed.) A fixed drive whose snapshot Windows could not take.
Good to know
- Windows refused access: the text under the table says Run S.A.K. Utility as administrator to read this drive. Click Run as Admin and scan again. Some drives in USB enclosures do not pass the report through at all, even then.
- PASS is not a guarantee: drives can fail without warning. Keep backups either way.
- Repairs: the app does not repair file system errors. If it recommends a repair, back up first, then run
chkdsk X: /ffrom an administrator Command Prompt. - Time limits: a drive with many files can take a while. Check Disk Errors gives each drive up to 30 minutes and a whole run up to two hours. A drive that runs out of time counts as not checked, and the run reports Scanned 1 of 2 drives; 1 could not be checked, with the drive named after it, such as (D:).
- No Cancel button: the other tools on the tab are locked while it runs. If you close the app, it asks you first.