Date: Mon, 1 May 2006 20:32:55 +0100 From: Greg Eden <greg@wholemeal.net> To: freebsd-proliant@freebsd.org Subject: Re: freebsd-proliant Digest, Vol 21, Issue 5 Message-ID: <1CBC6F85-AA8D-41C0-81F8-1803309CEE03@wholemeal.net> In-Reply-To: <20060429120039.1A5B816A516@hub.freebsd.org> References: <20060429120039.1A5B816A516@hub.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> My question is, is there anything on the os and software level that > could > cause this behavior? or is it most likely bad hardware? I am concerned > because I noted an instance of the same error in the ilo logs of > our other > dl380, although on module 1, and i thought that the odds of both > having > bad ram/boards might be slim. Sadly not as slim as you'd like or hope. I had 3 DL360s and a DL380 delivered last year. One DL360 had bad EEC RAM (was reported in logs fortunately). Another DL360 had a dodgy SCSI backplace which meant drives would go missing. So that was 2 out of 4 delivered faulty. Having said that HP dealt with the faults quickly and sent advance replacements swiftly. And once running the machines have had up times of 6 months+, limited only by reboots for maintenance. Which is why I bought them :) best. greg.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1CBC6F85-AA8D-41C0-81F8-1803309CEE03>