• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 325
  • Last Modified:

Server reboots during Exchange DB recovery

I am using a Compaq ML 350 G5 with 4 GB RAM, (2) 72 GB Drives RAID 1+0, (4) 320 GB drives RAID 5 using the onboard e200i controller. All drivers are updated to current levels (as of 4/2009). The OS is Windows Server 2008 running Exchange Server 2007. The MDB is approx. 52 GB in size and is contained on the RAID 5 partition. There is approximately 780 GB of free space on this drive.

We had a power outage yesterday which caused the Mailbox DB to become corrupt. After trying other options, I ran Eseutil (/p) to recover the DB. Here is the problem: the server would succesfully run the first two stages of recovery, but during the final cleanup stage, the server unexpectedly reboots.

I am in the process of restoring the DB from backups, but am concerned that the reboots are signs of other underlying issues.

Any guidance/assitance would be VERY much appreciated. I have been battling with this server.
0
BPGAssociates
Asked:
BPGAssociates
  • 3
  • 2
1 Solution
 
SurajCommented:
take the database to a different drive and do the eseutil /p
cos if its some issue with the  disk drive . it can cause the issue....
0
 
Handy HolderSaggar makers bottom knockerCommented:
eseutil is high disk I/O and Proliants may crash during high I/O if they don't have the latest Proliant Support pack installed to match up with the MS storport hotfix. See the note in the introduction of http://support.microsoft.com/kb/932755/en-us. This pretty much applies to all Smart Array controllers, if you have the latest MS OS servicepacks and hotfixes you have to install the latest Proliant Support Pack to make sure the drivers match.
0
 
BPGAssociatesAuthor Commented:
Reviewing the TID, does it apply to Server 2008 x64? I only saw that it applies to Server 2003.
0
Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
Handy HolderSaggar makers bottom knockerCommented:
Didn't know you had 2008, no, doesn't apply to that OS.
0
 
BPGAssociatesAuthor Commented:
I have been talking with an HP engineer and we believe we have the solution:

Apparently, the Proliant MultiFunction GB NIC's are engineered to take advantage of iSCSI Initiator, which is designed to offload disk controller functions, reducing load on the SCSI controller. There are 2 ways of registering the initiator, one is to buy an HP registration package, or the other (easier) is to buy an HP dual port NIC.

One of my peers eliminated his problem by purchasing a Linksys NIC and using it, instead of the HP onboard NIC's. Makes you wonder why HP would even manufacture a motherboard with NIC's if you're going to need to replace the NIC anyway.
0
 
Handy HolderSaggar makers bottom knockerCommented:
Doesn't make any sense at all. The iSCSI and TOE functions should not be causing problems because you haven't turned that functionality on.

Where's this HP engineer from?
0

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now