What "Tested" Actually Means: Drive Burn-In Testing Explained
Every listing says the drive was tested. Almost none say what that means, and the difference between a power-on check and a proper burn-in is the difference between a drive that fails in week two and one that runs for years. This covers what testing should include and what to ask.
What does "tested" actually mean on a used drive?
Anything from thirty seconds to three days, depending on the seller.
At the bottom: the drive was powered on, detected, and listed. That is not testing; it is confirming the drive is not dead.
At the top: the drive was run under sustained load for an extended period, its health data was read before and after, its entire surface was scanned, and it was rejected if anything moved. That is burn-in testing, and it is what "tested" should mean.
The gap between those two is where used drive risk lives. Our grading guide covers what each grade should include.
What is burn-in testing?
Running a drive under load for long enough that early-life failures show up before the drive ships.
Drive failures cluster at two points: very early in life, and at end of life. Burn-in exists to catch the first group. A drive that survives sustained load for a day or more has passed the point where most early failures occur.
A proper burn-in includes four things.
Health data read before the test — hours, reallocated sectors, pending sectors, error counts. Our drive health guide covers what each value means.
Sustained read and write load across the whole drive, for hours rather than minutes.
A full surface scan that touches every sector and records any that are slow or unreadable.
Health data read after the test, compared with the before. A drive whose error counts moved during the test is rejected, even if it still works.
Why does a full surface scan matter?
Because a drive can be perfectly healthy in the areas it has used and failing in the areas it has not.
Sectors that were never written since the drive was last in service have never been checked. A power-on test does not touch them. A surface scan does, and it is where marginal drives reveal themselves — sectors that read slowly, sectors that need retries, sectors that get reallocated during the scan.
The number to ask about is reallocated sectors. A drive with zero is healthy. A drive with a handful is usable but ageing. A drive where the count moved during testing is one that is actively degrading. Our drive lifespan guide covers what those counts predict.
What about testing SSDs?
Different failure modes, same principle.
An SSD burn-in checks remaining endurance (how much of the drive’s rated write life has been used), media errors, and sustained write performance under load. A used SSD with most of its endurance consumed is not a bargain regardless of how it performs today — our SSD endurance guide covers reading the numbers.
Also worth asking on an SSD: was it cryptographically erased or overwritten? A previous owner’s data on a used SSD is both a security issue and a sign of a careless seller. Our sanitisation guide covers what proper erasure looks like.
What should I ask a seller?
Five questions, and the answers tell you what kind of seller you are dealing with.
How long was the drive under load? Hours is a real answer. "It was tested" is not.
Was the full surface scanned?
What are the power-on hours? The drive reports this exactly. A seller who cannot say has not looked.
What is the reallocated sector count? Same — the drive reports it.
Was it sanitised? For any drive that held someone else’s data.
A seller who answers all five without hesitation has done the work. One who answers none has powered it on and listed it.
Does testing replace warranty?
No. It reduces the chance you will need the warranty.
Burn-in catches early failures. It does not predict the random failures that happen mid-life, and it does not catch a drive that will fail in transit — our packing guide covers why that happens. Warranty covers what testing cannot.
So the two questions belong together: what testing was done, and what happens if it fails anyway. A short warranty on a drive with a thorough burn-in is a reasonable combination. A short warranty on a drive that was only powered on is not.
Frequently asked questions
What is burn-in testing for hard drives?
Running a drive under sustained load for hours or days so early-life failures show up before it ships. A proper burn-in reads health data before and after, applies sustained read and write load, scans the full surface, and rejects any drive whose error counts moved.
How long should a hard drive burn-in test take?
Hours at minimum, and a full surface scan on a large drive takes many hours on its own. A test measured in minutes is a power-on check, not a burn-in.
What should I ask before buying a tested drive?
How long it was under load, whether the full surface was scanned, the power-on hours, the reallocated sector count, and whether it was sanitised. A seller who cannot answer has not looked.
Why does the reallocated sector count matter?
It shows how many sectors the drive has had to retire. Zero is healthy. A handful is ageing but usable. A count that moved during testing means the drive is actively degrading and should be rejected.
How are used SSDs tested?
Remaining endurance, media errors and sustained write performance. A used SSD with most of its rated write life consumed is not a bargain regardless of current performance. Also confirm it was cryptographically erased.
Does burn-in testing mean I do not need a warranty?
No. Burn-in catches early failures; warranty covers the mid-life random failures and transit damage that testing cannot predict. The two questions belong together.
Ask us the five questions above about any drive we list. We will answer all of them.
