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/
