Well, reality is implementation specific :-) I've seen plenty cases in the recent past where hardware fails shortly after being pushed into service. Shipping issues, manufacturing quality, environmental issues, installation problems, and hitting edge-case bugs in new products are all things that I've seen cause gear to be considered 'DoA' or fail before even seeing the light of production.
I think burn-in testing is important espically when you start dealing with large populations of identical parts, since you want to be able to suss out any kind of "oopses" in your batch before they cause real problems. -n On Thu, Jan 30, 2014 at 8:12 AM, Corey Quinn <[email protected]> wrote: > In 2014 this strikes me as bizarre. I'm not denying what you're seeing, but > it doesn't match my experiences. > > I've seen rare cases of DOA, but virtually no fails-in-24-hours scenarios > over the past five years. > > On Jan 30, 2014, at 7:34 AM, Mike Julian <[email protected]> wrote: > > We constantly find memory, network, and hard drive failures very early on > after turning over to a customer. Sometimes as soon as we start to deploy an > OS/software to them. It happens *quite* often. > > > On Thu, Jan 30, 2014 at 9:29 AM, Edmund White <[email protected]> wrote: >> >> Is it really necessary to burn-in modern hardware (that isn't Supermicro)? >> >> I come from the HP perspective and really don't do anything of that sort. >> What do you expect to catch during burn-in? >> http://serverfault.com/q/518239/13325 >> >> However, if you're using modern HP boxes (Gen8), you can run a diagnostic >> loop with the built-in Intelligent Provisioning tool (press F10) or just >> load the current HP Service Pack for ProLiant DVD/ISO (HP SPP). The latter >> is important because it brings all component firmware up to date and can >> allow you to run timed tests or a specific number of loops through the >> installed hardware. >> >> See: >> >> http://www8.hp.com/us/en/products/server-software/product-detail.html?oid=5104018#!tab=features >> >> -- >> Edmund White >> >> >> From: Mike Julian <[email protected]> >> Date: Thursday, January 30, 2014 at 8:12 AM >> To: LOPSA Discuss <[email protected]> >> >> Subject: [lopsa-discuss] Hardware burn-in tools >> >> Hey all, >> >> We're investigating options for doing hardware burn-ins on servers before >> we hand them off to customers, thanks to a long history of hardware failures >> within 24-72 hours of handing them over. >> >> We're an all-Dell shop, though we are also looking at moving to HP >> sometime soon-ish (leaving us with supporting both Dell and HP). >> >> Ideally, we'd love something that can easily be automated and is >> Linux-based. >> >> What tool recommendations do you have? >> >> -Mike > > > _______________________________________________ > Discuss mailing list > [email protected] > https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss > This list provided by the League of Professional System Administrators > http://lopsa.org/ > > > _______________________________________________ > Discuss mailing list > [email protected] > https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss > This list provided by the League of Professional System Administrators > http://lopsa.org/ > -- ------------------------------------------- nathan hruby <[email protected]> metaphysically wrinkle-free ------------------------------------------- _______________________________________________ Discuss mailing list [email protected] https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss This list provided by the League of Professional System Administrators http://lopsa.org/
