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.
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.
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.
ASKER
Reviewing the TID, does it apply to Server 2008 x64? I only saw that it applies to Server 2003.
Didn't know you had 2008, no, doesn't apply to that OS.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
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?
Where's this HP engineer from?
cos if its some issue with the disk drive . it can cause the issue....