Koozali.org: home of the SME Server
Contribs.org Forums => General Discussion => Topic started by: Terry on August 30, 2008, 12:09:15 AM
-
Contribs 7.3
Basic install with VMWare server, running Exchange in the VM.
Want to upgrade from 767M to 2G.
Swapped the ram in the server, server booted the first time but the VM server would not start.
Rebooted, now no services would start, could only login at the terminal, no ssh, no httpd, nothing. Watching the boot it would just get past the hardware detect, then something would flash FAIL in red and drop me to a login, no idea what was failing.
I put the old ram back in and the server came right up. Any idea's?
-
Not knowing what motherboard you have, I would question if it supports the ram. I would also suggest testing the memory.
Bob
-
It's an older MSI, the BIOS reports 2 gigs on POST. I made sure to pickup what the manual says it supported. The book is here somewhere...
-
Well, odd as odd can be, reinstalled the ram and it's working fine.
-
My experience: If strange things is hapening with the Vmware Server then to run the configuration script once more might repair it all. (I had one Vmware Server crash after a power failure, and running the installation config script repaired it all.)
-
Just in case others are following this, thought I'd add my 2 cents.
I have had the odd (as odd can be) problem when RAM wasn't seated properly. When the PC boots (POST) most PC's are set in BIOS to not actually check the RAM as they boot faster, they simply check the memory size fitted. They fail if they start writing to the bad RAM area (which might be on a second stick etc) which would explain why it started to boot OK.
Also, with RAM these days having very small connections, it is easy to not get them in right. RAM can also be affected by speed - you shouldn't mix/match manufacturers even for the same supposed speed. Not all RAM is the same.
That having been said, for servers, if I have any doubt, I run a memory tester (DOS program) I picked up from somewhere on the net and made a bootable CD. It is a true tester in that it writes ones, zeros, bit patterns and random patterns. Leave it going for 30 minutes or so. It picks up RAM problems easily and has proven to me without having to lift the lid off the box whether it's hardware or software. Good for suspect RAM (damaged by lightening etc).
-
I run a memory tester (DOS program) I picked up from somewhere on the net and made a bootable CD.
Or use the memtest option on the SME server CD.