Windows Server 2003 won't Boot - Hangs at Splash Screen

Hi,

We came in this morning to a hung server that users couldn't access.  Upon rebooting it hangs at the Windows Server 2003 splash screen.  Here are the specs & troubleshooting steps attempted so far:

Configuration Info:
* Server Hardware = HP ProLiant ML570 G2
* Server OS = Windows Server 2003
* HDD = 4 disks in a Raid 5 config

Troubleshooting Steps:
* Attempted most variations of booting to "Last Known Good Config", Safe Mode, Safe  Mode with Networking
  -> hangs each time at this file - acpitabl.dat
* Replaced the CMOS battery
  -> attempted to update ACPI settings in BIOS - not visible/available?
* Removed 1 hdd & rebooted to try to "degrade" setup, then added back to normal hdd setup
* Boot to Windows Server 2003 cd, attempted Repair
   -> it reported that it didn't find any disks?? ($65)

Any help is appreciated, thanks.
pridenetadminAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Jeff PerryWindows AdministratorCommented:
Are there any USB devices plugged into the server?

Microsoft Technet article.

Windows Server 2003 cd does not have the RAID driver so that is why it cannot see the disk array.
0
pridenetadminAuthor Commented:
* No, there are not any USB devices plugged into the server, nor any storage devices (SAN etc)
* Roger that on the RAID driver

Thanks.
0
Onet-ITCommented:
I have the same problem and most answers say to check the RAM.
Take some modules out and see what happens.
My problem seems to be the raid controller though.

And yes, you need the raid controller drivers to get the install going (F6)
0
pridenetadminAuthor Commented:
After slipstreaming the raid controller drivers into a copy of the Windows Server 2003 CD, via nLite (http://nliteos.com/), we were able to run chkdsk.  And after running chkdsk the server booted up and we had access again.

Thanks for all the input, always appreciated.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
pridenetadminAuthor Commented:
I found the utility and was able to resolve the issue.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.