On Wed, Feb 03, 2010 at 10:21:10AM -0600, Henrik Schmiediche wrote: > I cannot get the node to startup to the point where OMSA runs. It freezes on > startup with the bad RAM.
Just take out all RAM (and note which DIMM was in which slot), insert known-good RAM; then have a look at the ESM log. It will tell you where the errors occured (exact DIMM location). Then move all other RAM in, and perform a extensive memory test. HTH, Tino. > - Henrik > > -----Original Message----- > From: Ryan Miller [mailto:[email protected]] > Sent: Wednesday, February 03, 2010 10:19 AM > To: Henrik Schmiediche; [email protected] > Subject: RE: PowerEdge 1950 ECC question... > > Are you running OMSA? It usually is able to pinpoint which stick is the > cause of single bit errors. It can be helpful to stress the RAM with some > heavy compiles/DMA to make the bad stick throw an SBE sooner. > > > -----Original Message----- > > From: [email protected] [mailto:linux-poweredge- > > [email protected]] On Behalf Of Henrik Schmiediche > > Sent: Wednesday, February 03, 2010 11:09 AM > > To: [email protected] > > Subject: PowerEdge 1950 ECC question... > > > > Hello, > > Is it possible to turn ECC off on the PowerEdge 1950? I have servers > > from > > other manufacturer where this is possible, but I cannot find this > > option in > > the PE 1950. I'd like to test the memory with ECC turned off. > > > > Here is Background: > > > > I have a PowerEdge 1950 (one of over 100+ identical systems) that > > freezes on > > startup. I can reimage the node fine, the freeze on startup persists. > > The > > node passes Dell Diagnostics including overnight memory testing. > > Nothing in > > the ESM log. > > > > I reseated the RAM and other components. No solution. > > > > On a lark I decided to change all 8 memory sticks.. this solved the > > problem! > > The system starts up fine. > > > > So it seems there is a bad memory module, but I have no idea which > > ones. I > > am trying to avoid the one-by-one (or batch-by-batch) testing method > > and I > > was thinking that (maybe) turning ECC off might help locate the bad > > module. > > > > Any ideas? > > > > - Henrik > > > > > > _______________________________________________ > > Linux-PowerEdge mailing list > > [email protected] > > https://lists.us.dell.com/mailman/listinfo/linux-poweredge > > Please read the FAQ at http://lists.us.dell.com/faq > > _______________________________________________ > Linux-PowerEdge mailing list > [email protected] > https://lists.us.dell.com/mailman/listinfo/linux-poweredge > Please read the FAQ at http://lists.us.dell.com/faq -- "What we nourish flourishes." - "Was wir nähren erblüht." www.lichtkreis-chemnitz.de www.tisc.de _______________________________________________ Linux-PowerEdge mailing list [email protected] https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
