3 ms·
The author probably bought all of those hard drives at once, from the same vendor. They're very likely in the same batch. What if something goes bad with a dri
by colindean 11y ago
The author probably bought all of those hard drives at once, from the same vendor. They're very likely in the same batch.
What if something goes bad with a drive? Well, ZFS to the rescue. Maybe even two.
What if the whole batch was bad?
I've built my NAS with not quite as much storage but more drives using drives from different vendors and different batches from different manufacturers.
- rsync 11y agoIt is good to be concerned about batching disk drives, as you imply. However, given that the problems that arise with a bad batch are physical ones, properly burning in the drives does, I think, alleviate those concerns. We burn ours in for 5-6 days[1] before we put them into production and history shows this weeds out the bad ones. If there was an entirely bad batch, we would catch it that way. In my opinion, far, far more likely to find yourself with fake-new drives than with an actual "bad batch". We see that all the time from amazon sellers that claim brand new drives, but SMART says otherwise... [1] with a zero tolerance policy for even the tiniest deviation from normal in the SMART output. Even a blip and that drive is out.
- rgbrenner 11y agoIf there was an entirely bad batch, we would catch it that way. You're a very optimistic guy. That test would not have caught IBM deathstars or the more recent Seagate 3tb barracuda failures. I lost 6 of the 8 drives in my NAS due to that last one.. luckily not all at the same time.