Windows 2008 R2 power surge, now stuck booting on "Microsoft Corporation"
Hi, we suffered a massive building power surge last night. Three of our four servers booted fine. They all have UPS power.
The one that WON'T boot is our domain controller. It's stuck on the black "Microsoft Corporation" screen. Safe modes didn't work, neither did "last known good".
We're desperate. Please help.
Microsoft Legacy OSWindows OSWindows Server 2008
Last Comment
DrGangles
8/22/2022 - Mon
PaulD77
Do you have the media for server 08? I would try booting with the disk and run a repair....or can you get into BIOS or any diagnostics from bootup?
DrGangles
ASKER
Thanks. Yes, I've tried to run a repair, but unlike instructions I've seen, no operating system shows up. It appears to have crashed in the middle of last night's backup, so we'd need to go back a day, and we DO NOT want to do that.
jramsier
Resead the hard drives? Does the hard drives show in bios? If it is a RAID 1 (or no RAID) you can try to remove one drive. If it is a SATA drive try booting it on a desk top or USB and run checkdisk on it.
So when you boot off the disk...
Select next after making sure the language options are correct.
Select Repair option
Select CMD
CD into recovery
Type Dir
Run the StartRep.exe command in the list.
DrGangles
ASKER
@jramsier HAH! No kicking yet.
It's a RAID 5 Promise array. So far, we've gotten to the loading drivers part for the Promise controller, but now it's taking FOREVER to load the drivers.
Everywhere I turn, brick wall.
@PaulD77 There's no CMD option.
DrGangles
ASKER
Driver install failed. Of course. They're the EXACT drivers we used in setting up the server last year. Same disk.
When you run the repair, is it finding any current installation of server 08? If it does, but does not have the cmd options available, start the repair and the dialog box should have a cancel button, if you cancel it, does the cmd option become available?
DrGangles
ASKER
It's not finding an installation, so I'm guessing that's why it's asking for drivers. When we try to install the Promise drivers, we select the proper controller, see MS's non-progress progress bar for several minutes, and then the driver install fails.
Thanks again for the ongoing help.
PaulD77
hmmm. Well I thinkl you can access the cmd by hitting Shift F10 at the select language screen..if you get a cmd, run a dir on the c: to see if windows files are there...if ther are, try run the StartRep.exe from the CD
The array is 100% functional, and it's RAID 5, not 1 (which I would be happy to try). I really don't want to mess with that. While it does have a hot spare, a rebuild takes about 6 hours.
Thanks, the command prompt DID come up. I found startrep.exe, ran it, and it says I have no hard disk. That would explain why it has no operating system.
The Promise interface says the array is functional, but this is obviously a Windows driver issue now. And since I can't seem to load the drivers in the LOAD DRIVERS part of the recovery, I'm stuck again.
Promise has no diagnostics. It's an SX-4300 controller on a Tyan S3950G2NR board. These boards have been rock-solid for us for three years, but the other three servers use Adaptec 1420SA RAID1 controllers.
I'm almost to the point where I may clone the contents of the Promise array to our spare-parts 1420SA and one of several new spare drives. I wish I could do this outside Windows, though. The partition is small enough that it would fit on one new drive, then I could put that drive on the Adaptec and make a RAID 1 array from it.
Any idea how I can clone the Promise SX-4300 RAID 5 array to a blank drive, but outside of Windows? Gparted won't recognize the Promise array (didn't think it would).
DrGangles
ASKER
Thanks again for the replies. I don't know exactly what the problem was, but we finally fixed it by moving the entire RAID 5 array (card and drives) to spare computer. We copied the array to a single bare drive using Acronis True Image (a lifesaver of a program), moved the bare drive back to the server along with a new 1420SA, booted it, installed the 1420SA drivers, shut down, installed the new drive on the 1420SA with an identical blank drive, rebuilt into a RAID1, rebooted, and we're up and running again.
My guess is that the surge did something to the Promise controller, which is why we couldn't install its drivers to do a system file repair.
Out of every crisis, there's something better, and now we don't see some of the performance warnings we saw with the Promise controller.
Sorry for the babbling. We're pretty happy it's fixed, and it seems to be an improvement. Happy holidays!
DrGangles
ASKER
While no reply was an exact answer to our problem, they all helped to point us in the right direction. Thanks again to both of you and happy holidays!