RunTheTests
/

smartctl Output Interpreter

Paste smartctl output and get a verdict built on the five attributes that predict failure.

What you paste

Parsed in your browser — never uploaded

How this reads your output

Paste the report and the attribute table is read into a common shape, then judged. The judgement is deliberately narrow. A drive reports thirty attributes and most of them predict nothing: Backblaze publishes failure statistics across hundreds of thousands of drives and finds five that genuinely correlate with failure. Those five carry the verdict here. Pending sectors are treated as the most urgent, because they describe data that cannot be read right now rather than damage the drive has already contained. Interface errors are separated out entirely, since they are almost always a cable and telling someone their drive is failing when the fix costs a few pounds is the most common wrong answer in this category.

What the results mean

Current pending sectors (197)
Sectors that failed to read and are waiting to be remapped. Unreadable now — this is data loss in progress, and the most urgent value on the list.
Reallocated sectors (5)
Sectors that failed and were remapped to spare area. Damage the drive has contained. A stable count is a drive that took a knock; a growing one is a drive on its way out.
Command timeout (188)
Commands that did not complete. Frequently the cable or the power connector rather than the drive — worth eliminating before condemning anything.
UDMA CRC errors (199)
Corrupted transfers between drive and controller. Almost always a bad data cable. The counter never resets, so what matters is whether it rises after the cable is changed.
Normalised value versus raw
The normalised value is a vendor scale where higher is better and the threshold is the failure floor. The raw value is the actual count, and for the five predictive attributes it is the number that matters.

Common problems and fixes

No attribute table was found
Paste the whole report. A drive in a USB enclosure or behind a RAID controller often reports no table at all, which is the enclosure rather than the drive.
Attributes show huge raw values but the drive seems fine
Check which attribute. Seek error rate and raw read error rate are vendor-encoded and read in the millions on healthy drives — they are noise, not evidence.
The overall self-assessment says PASSED but sectors are reallocated
Both are true. The self-assessment only fails once a vendor threshold is crossed, which is late. Reallocated sectors are worth watching well before that point.
The count went up since last month
That is the finding. A rising count on any of the five predictive attributes means active degradation — plan the replacement rather than waiting for the drive to fail.

Frequently asked questions

Which SMART attributes actually predict drive failure?

Five, with published evidence behind them across hundreds of thousands of drives: reallocated sectors (5), reported uncorrectable errors (187), command timeouts (188), current pending sectors (197) and offline uncorrectable (198). Non-zero values on any of them are worth acting on, and a rising count is worth acting on immediately. The other twenty-five attributes make interesting reading and predict very little.

My drive shows pending sectors — what should I do?

Back up first, before any further diagnosis. Pending sectors are sectors the drive currently cannot read, which means the data in them is already in trouble and the drive is under stress every time something tries. Running a long self-test or a surface scan before copying the data off is a common and expensive mistake.

Does a CRC error mean my drive is failing?

Usually not. Attribute 199 counts corrupted transfers between the drive and the controller, and the overwhelming cause is the data cable — a poorly seated connector, a cheap lead, or one that has been bent behind a case for years. Change the cable and watch the counter: it never resets, so a count that stops growing means the problem is fixed.

Is the report I paste sent anywhere?

No. It is parsed in your browser, and the drive serial number is deliberately excluded from anything the tool exports.

Put this on your own site

Free to embed, no attribution required beyond the source link the frame carries itself. It runs entirely in your visitor's browser, sets no cookies and loads no third-party script.

Embed code
<iframe src="https://runthetests.com/embed/smartctl-interpreter/" width="100%" height="720" style="border:1px solid #e5e5e5;border-radius:8px" title="smartctl Output Interpreter" loading="lazy"></iframe>

Preview it at https://runthetests.com/embed/smartctl-interpreter/. Embedded pages are marked noindex, so yours stays the canonical copy — not this one.

More in Interpreter