Estimate one full sequential read by dividing drive capacity by sustained transfer speed. Many 8–12TB HDDs need roughly 12–24 hours for a single read pass, but inner tracks, USB bridges, concurrent I/O, retries, and drive firmware can extend that window.
A SMART long test, a read-only surface scan, and a destructive multi-pattern badblocks test are not equivalent. Multi-pass write-and-verify burn-in can take several days and destroys existing data. This distinction sets the measurement method, safety margin, and stop condition. This distinction sets the measurement method, safety margin, and stop condition. This distinction sets the measurement method, safety margin, and stop condition.
Calculate a realistic baseline
An 8TB drive averaging 180MB/s needs about 12.3 hours for one ideal decimal-capacity pass; at 120MB/s it needs about 18.5 hours. Add margin for slower inner tracks and command overhead.
Use the drive’s actual sustained rate on the same controller and enclosure. A SATA disk behind a marginal USB bridge can be limited by resets, power, or thermal behavior rather than platter speed.
Run tests on individual disks where possible and record model, firmware, interface, capacity, start time, and expected completion. This makes abnormal stalls distinguishable from a slow but continuous scan.
Judge progress and health together
Normal progress is continuous even if the rate declines toward the inner tracks. Long gaps, repeated kernel resets, I/O errors, or a rising pending-sector count are not normal duration variance.
Check SMART data before and after the scan, including reallocated, pending, offline-uncorrectable, command-timeout, and interface-CRC counters. Interpret changes in context rather than trusting one overall health label.
Use the table below to classify the result.
| Observed state | Verdict | Next action |
|---|---|---|
| Steady progress; rate tapers | Normal full-surface behavior | Let the pass finish |
| No progress; USB/SATA resets | Path instability | Stop and isolate cable, power, enclosure |
| Read errors or SMART counters rise | Media risk | Do not trust the drive |
Choose the least destructive test that answers the question
Use a read-only scan when preserving data is required. Use a destructive write/read burn-in only on an empty drive with the correct device identity verified and no valuable data attached.
Keep enclosure cooling and power stable, and pause scrubs or copies that would make timing meaningless. Testing multiple drives in parallel is reasonable only if the controller, power supply, and cooling can sustain them.
ZimaSpace’s verification-read diagnostic separates media faults from enclosure resets.
HomeServerCalc’s drive burn-in timing table illustrates how capacity and test pattern change total duration.
Retest any suspicious path before trusting the drive
If the scan stalls, repeat a limited read on the affected region using a known-good SATA port, cable, power source, or enclosure. Preserve logs before changing hardware.
A clean second path suggests the original bridge or cable was responsible; recurring media errors or growing SMART counters point back to the drive. Do not add a questionable disk to a degraded array.
Accept the drive when the full pass completes without read errors, resets, or worsening health counters. Stop and replace or return it when errors repeat on a known-good path, regardless of whether the total runtime looked plausible.
Support & Tips
More to Read

What to Check Before Loading a Community Model in Transformers
Use the Transformers Jinja sandbox update to review model provenance, chat templates, remote code, serialized weights, and isolated first runs.

Run Mirage Locally: OCR and Object Detection from One Image
Try Cactus Compute’s small local vision model, validate OCR and object extraction on real inputs, and understand memory, language, and privacy limits.

How to Schedule a Coding Agent in Open WebUI on a Home Server
Set up a report-only coding agent automation in Open WebUI, select its terminal and workspace, and verify permissions, logs, and failure recovery.



