Question Locked

Windows 2003 R2 x64 - IBM 325e freezes on irregular basis

0 helpful
9 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I am having an intermittent ?lock up? that is driving me nuts. I am pretty much ready to throw the towel in.

We have an IBM eServer 325 (8835) 1U server with dual AMD Opterons, 4 Gig RAM, dual onboard 10/100/1000 NICS, onboard Rage XL video and onboard IDE with 2 drives (sliced into 3 partitions). We are running Windows Server 2003 R2 x64 (using Windows to mirror drives) and Exchange 2007 (basic roles with FSE 2007). Small office network with a Windows 2003 DC in the same rack.

About every 6 or 7 days the box ?freezes?. The first indication of the problem is that clients lose their Outlook connection to Exchange. When I log onto the console I can view the logs, but there are never any relevant errors. I can never reboot the box. The more ?stuff? I try to open, the quicker the box completely locks up 100%.

I have noticed two constants when the problem happens. First of all, the system clock (in the tray) is always frozen at the instant the problem started (Windows event logging also stops at the same instant). Secondly, the two NIC tray icons are missing from the tray. I can view the device manager and everything appears fine there even though the icons are gone. If I try to ?remote? in during the problem, I get half way and then the screen goes black. I always end up having to pull the AC plug and let the box recycle that way. Once done, all is well and darn near perfect for another 6 or 7 days (other than the mirrors need to re-synch). On the DC there are no errors indicating a problem on the other box (other than a warning that the Exchange box has the wrong time, etc).

This problem has occurred since we built it with W2K3 several months ago. I have no idea what was on the box previous to that.

I have swapped memory, drives, CPU?s and finally the entire box with another 325e thinking this was a hardware problem. I keep getting the exact same results. I have upgraded every driver from the IBM site and even installed the latest drivers for the AMD processor and chip set from the AMD site. I have upgraded the BIOS and the firmware on the NICs and BMC. MSI made the IBM 325?s, so I looked on their web site too and took their appropriate drivers. I have taken all the Windows suggested updates and patches. I have spent days googling the problem. No changes.

I am reluctant to reformat and start over because I don?t think it will solve the problem. Is there some AMD/Opteron/Windows 2003 R2 x64 issue/incompatibility I am missing? Does some hardware (like the BMC) just not play well with Windows 2003? Any and all help is greatly appreciated.

Thanks.

Charlie

9 replies

by cmiller5400

Are you teaming the NIC's? If so, maybe just use one of them and disable the other?

The other thought that I had was to thoroughly test the RAM. I have seen crazy things happen with bad ram.

Good luck!!

Edit: spelling

by charlieo

Nope. I have the second NIC disabled. I have even tried using the second NIC rather than the 1st. I agree about the RAM... especially with older RAM. Unfortunately I have completely swapped out the RAM (with OEM) and had no luck. I have also run the IBM diagnostic against all of the RAM. I think my problems have something to do with the baseband management controller, if I had to guess. . . . but I can't find anyone who has the scoop on the MSI BMC in the server.

Thanks again.

Charlie

by mark.hough

I had a similar problem with Windows 2003 R2 x64 on Sun Hardware. The problem was finally cured when we turned off Windows software mirroring!

It's worth a try, I almost went mad trying to find the cause.

by Former member

It might be as simple as putting in a new bios battery and putting in more ram, double the ram that you have (if possible), this will give the server a bit of elbow room as it were.

Please post back if you have any more problems or questions.

by charlieo

Thanks for the suggestion but I don't think adding more than 4GIG will make a difference. The box is very lightly used.

by bsiegler

I have 2 of these servers, and it's driving me crazy. Did you ever find a solution to this problem? I have x64 linux on the other server, and I've noticed the uptime has never exceeded 24 hours. Was it the BMC, or did you give up? BTW did you get bios 1.36 loaded, or just 1.33? I did the update to 1.36, but it never took. I only point this out because one of the fixes was for a calculation error!

by bsiegler

I have 2 of these servers, and it's driving me crazy. Did you ever find a solution to this problem? I have x64 linux on the other server, and I've noticed the uptime has never exceeded 24 hours. Was it the BMC, or did you give up? BTW did you get bios 1.36 loaded, or just 1.33? I did the update to 1.36, but it never took. I only point this out because one of the fixes was for a calculation error!

by bsiegler

Excellent news. This is ONLY an issue with
2003 x64 and the IBM eServer 325. I recently
loaded Windows 2008 x64 / 2007 Exchange, and
the server is VERY stable!

Cheers

This discussion is closed to new replies.