"fixing" memory error

jeff nichols jeff.n at linuxmail.org
Sun Sep 16 11:28:09 CDT 2007


Could be that the esm was never cleared after replacing the DIMM.
I'd suggest installing dset and running a report. The report will give you a 'before' snapshot you may need later.

Once installed, you can run clearemslog from a shell prompt.
http://support.dell.com/dset

Thanks,
Jeff



> ----- Original Message -----
> From: "Tino Schwarze" <linux-poweredge.lists at tisc.de>
> To: linux-poweredge at dell.com
> Subject: "fixing" memory error
> Date: Sun, 16 Sep 2007 17:21:35 +0200
> 
> 
> Hi there,
> 
> we've got a machine here which hasn't seen OMSA for a long time. Three
> years ago, a multibit ECC fault was detected (we had a broken DIMM
> then). We replaced the DIMM and haven't had any problem since then.
> Recently, the machine got a new OS and we installed OMSA on it. Now the
> error shows up:
> 
> xxxxxx:~ # omreport chassis memory
> Memory Information
> 
> Health : Critical
> [...]
> Details of Memory Array 1
> Index          : 0
> Status         : Critical
> Connector Name : DIMM A
> Type           : DDR-SYNCHRONOUS
> Size           : 1024  MB
> 
> How do we clear the error condition? Do we need to power down, swap the
> DIMM, power on for the BIOS to notice, power off, swap back? Or is there
> an easier way (couldn't find one with omconfig)?
> 
> Thanks,
> 
> Tino.
> 
> --
> www.spiritualdesign-chemnitz.de
> www.craniosacralzentrum.de
> 
> Tino Schwarze * Parkstraße 17h * 09120 Chemnitz
> 
> _______________________________________________
> Linux-PowerEdge mailing list
> Linux-PowerEdge at dell.com
> http://lists.us.dell.com/mailman/listinfo/linux-poweredge
> Please read the FAQ at http://lists.us.dell.com/faq

>


=
Cheap Homeowner Insurance
Instant Free Quote. Compare Rates Affordable Homeowners Insurance.
http://a8-asy.a8ww.net/a8-ads/adftrclick?redirectid=c18ca94ca887925e85b5431471eb3fda


-- 
Powered by Outblaze



More information about the Linux-PowerEdge mailing list