0

I added new HP memory to a server to go from 8 to 32GB. Now I have this error message appearing in /var/log/messages every few seconds.

    Jan  8 20:13:08 vmware01 kernel: EDAC MC0: CE row 2, channel 2,
 label "": (Branch=1 DRAM-Bank=6 RDWR=Read RAS=13788 CAS=2840,
 CE Err=0x2000 (Correctable Non-Mirrored Demand Data ECC))

I've googled for the error message and had no luck. Does anyone have any idea what it means and how to fix it?

Both the BIOS and the operating system see all 32 GB.

Any help with be greatly appreciated.

Jim Blizard
  • 605
  • 1
  • 5
  • 12

2 Answers2

2

The error message basically means that the memory you install is faulty. The system has found that the memory was corrupt and the ECC was able to correct the single bit error and alerted the OS to the fact that the memory is unhappy.

The DRAM in question is the DRAM in Bank 6 (most probably dual channel memory) so look at that location for the faulty ram.

Stephen Thompson
  • 1,482
  • 9
  • 10
2

I recently had this problem with an IBM blade with AMD CPU. It is a 64-bit blade that I've run for years with 8 GB and 32-bit RedHat 3, which means the OS only saw 4 GB. I upgraded it to 64-bit RH 4 and started getting very similar errors. The research I found said the EDAC reporting in the OS appeared at some point in version 4, around 4.5.

That meant I didn't know if it was the 4-8 GB section or just the OS now reporting the problem, so I went to the BIOS to run tests. The basic tests showed no errors but the advanced tests that take hours to run eventually showed the problem. Rotating different RAM modules to different slots indicated 2 of my 4 were bad and that the test quit when it found the first one. Putting a total of 2 GB in the machine with 4 different modules made the machine run fine.

For years the machine wouldn't reboot without a complete power off, which wasn't a problem for a HA database server but I reported the problem too. IBM was nice enough to change my reported 2 RAM modules and the whole motherboard so I can't swear the RAM fixed it.

Bottom line: look really hard at your RAM. You might try a bootable RAM test, such as an OS disk. It appears the standard RAM test programs are 32-bit, so they won't test above 4 GB. A 64-bit OS disk might include one that will.

Keith Stokes
  • 907
  • 5
  • 7