PSA to always run a full length SMART check for any drives you buy, even from OEM. The short test and log are not enough, I have bought faulty drives that someone had reset the logs and power on hours.
All passed short SMART test, but failed long SMART test after only a few minutes. Found just one drive that the skrub forgot to wipe and the log showed 6 continuous years of power on usage.
Even from OEM, you will at least know if the hardware is DOA which you can then RMA.
Do people still do that? Used to be common practice to power on equipment and let it sit, either idle or full-tilt, for a couple days before even starting to configure it. Let the factory bugs scatter out.
Yeah, we did that at my last company to make sure our hardware was up to spec. We deployed an IOT device for long term outdoor installations, so it needed to survive very hot temps. We had a refrigerator we gutted and added heat to, and we’d run a simulation with heavier than expected load for a couple days and tossed/RMAd the bad units.
That was a literal burn in, but the same concept ak applies to pretty much everything. If you build/buy a PC, test the hardware (prime95 CPU test, memtest for RAM, etc). Put it through its paces to work out the major bugs before relying on it so you don’t have to RMA a production system.
Secondary PSA Seagate use some godawful numbering scheme on their SMART results, if you’re not aware of the fact you need a calculator understand the raw error count it will freak you the fuck out.
PSA to always run a full length SMART check for any drives you buy, even from OEM. The short test and log are not enough, I have bought faulty drives that someone had reset the logs and power on hours.
All passed short SMART test, but failed long SMART test after only a few minutes. Found just one drive that the skrub forgot to wipe and the log showed 6 continuous years of power on usage.
Even from OEM, you will at least know if the hardware is DOA which you can then RMA.
Fucking people are wild.
Probably performs a good burn-in for them too.
Do people still do that? Used to be common practice to power on equipment and let it sit, either idle or full-tilt, for a couple days before even starting to configure it. Let the factory bugs scatter out.
Never heard of that, interesting
https://en.m.wikipedia.org/wiki/Burn-in
Yeah, we did that at my last company to make sure our hardware was up to spec. We deployed an IOT device for long term outdoor installations, so it needed to survive very hot temps. We had a refrigerator we gutted and added heat to, and we’d run a simulation with heavier than expected load for a couple days and tossed/RMAd the bad units.
That was a literal burn in, but the same concept ak applies to pretty much everything. If you build/buy a PC, test the hardware (prime95 CPU test, memtest for RAM, etc). Put it through its paces to work out the major bugs before relying on it so you don’t have to RMA a production system.
I do; I use a four pass destructive run of badblocks on new drives before implementing them.
Secondary PSA Seagate use some godawful numbering scheme on their SMART results, if you’re not aware of the fact you need a calculator understand the raw error count it will freak you the fuck out.
Accoirding to TFA these drives all passed SMART tests.