Link to home
Start Free TrialLog in
Avatar of jadasam
jadasamFlag for United States of America

asked on

Windows Server 2008 R2 server hung in repair loop

Hi Experts,
I have a Dell R310 server running Windows Server 2008 R2 (housing SQL Server DB's).  This server is stuck in a "repair loop" and I need assistance.
Original Error:
""Alert! iDrac6 not responding. Power required may exceed PSU wattage. Alert! Continuing system boot accepts risk that system may power down without warning."

Trouble shooting steps done so far:
1. Contact Dell Support
     a. They suggested I remove AC Power and reset (didn't clear error).
     b. They then suggested BIOS reset and clear NVRAM (this cleared the error however server still will not boot into the OS).
     c. Ran windows repair, windows was unable to fix the issue.
     d. Checked the RAID BIOS and all drives have a status of "Online".
     e. Ran a CHKDSK and found no issues.
     f. Dell agent sent me a bootable ISO with all the latest and greatest firmware, ran the disk and after updates the server is still stuck in the same repair loop.

I was able to get my data off the server using Ubunto Live Disk and copy files to an external drive..  However, I'd like to know if anyone has any suggestions on getting this server back without reloading the entire OS and loosing the installed SQL Application/Data.
Thanks in Advance.
Avatar of Gareth Gudger
Gareth Gudger
Flag of United States of America image

Prior to the BIOS reset and NVRAM clear, was it booting? Sounds like the original error was just causing unexpected shutdowns.
Avatar of jadasam

ASKER

It was booting into the OS just fine after the crashes.. just not anymore since the BIOS reset and NVRAM were cleared.  The iDrac Alert error is no longer showing up but now cannot boot into the OS.
Avatar of jadasam

ASKER

It was booting into the OS just fine after the crashes.. just not anymore since the BIOS reset and NVRAM were cleared.  The iDrac Alert error is no longer showing up but now cannot boot into the OS.
I would say the problem lies within the BIOS. That fix may have changed a setting that Windows is looking for to successfully boot into the OS. You may need to run through all BIOS settings and see if there is anything that doesn't look right.
ASKER CERTIFIED SOLUTION
Avatar of Gareth Gudger
Gareth Gudger
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of jadasam

ASKER

Thanks for trying to help.