So you can test SP2 before applying it to the production system. If you had done this way, you would had notice that the server hangs, and now your production one would be still working in RTM SP0. You got the picture for the next SP ; Why do you involve restoring update. By far the best method to restore your server is to perform a restoration from a tested backup. If you failed to make a backup prior to ther upgrade, you're stuck.
To create moderately useable backup, use ntbackup. To create a more useable backup, use an imaging product. Alternatively, if your disks are mirrored, split the mirror prior to the upgrade in order to retain your existing installation on one of the disks. If you believe that a restoration of update will solve your problem, give it a try but make sure to back up the original version first. When I did my most recent service pack installation, I did not burn my wings. Instead I followed the stern warnings I had received from my local user group about creating and testing a full backup first.
This was for a humble one-server business with just 12 staff. The idea about "restoring" update. If I undrstand you both Mr. Pegasus and Mr. Chateau , I get the message that the only way out of this pickle is to find some way to restore from backups which we do have. However, to restore, I need to re- install the opsys, install the backup program, re-catog or locate and reuse the catalogs of the backup media, and then restore the system folders from the backups.
You already had the means with your mirrored disks. The downtime to test this method would have been minimal. Yes, that's the drawback of ntbackup. This is why I use different backup methods. They let me restore a system onto a blank disk without first loading an auxiliary version of Windows. Not gonna provide instructions here. If you need them at this point you should probably call in qualified help www.
In the event this happened after a hardware change, remove the offending hardware and try to boot. If no luck perform the first option. Hope this helps someone For all others, chastising a person in need when they post a request for help in a forum is non-productive and uncalled for. It helps not the original person requesting help nor anyone else, and it clutters the post making searching for an answer harder.
My two cents.. The situation is that the server was rock solid until a weekend that a possible power outage occured. Yes there is a UPS that is out of date and the replacement is in a box on the server floor. No new software was installed and no new hardware was installed. I have upgraded the driver for the controller card to no avail. After installing win2k3 sp2 on win2k3 server which had no prior sp1, update to dot. In normal boot, it hangs at spash screen; in safe mode, it hangs at acpitabl.
Thanks a ton for this, saved me an all night rebuild! This was a very nice find, you saved a lot of us. I changed bios power management to user defined, still blue screened, I removed 3rd disk, raid yelled no boot volume, shutoff, put disk 3 back in, booted up fine. And rebooted fine! Just want to thank you for the importance of this tip. If you could only imagine! If you are down this side of the country will definitely treat you to some frosty cold ones.
I had this problem and tried every solution above mentioned and noting worked. So i disconnected all devices one by one and tried to start windows. When i took off the network card it started correctly.
I put a new network card and everything worked right. Seems like this problem could be caused by any faulty hardware. Thanks for the great post. One of the great things about the Internet.
We had a server come in, based on an old P4 mb yeah, that old. Had to copy ntldr to one of the two mirrored drives. After that, we could get it to boot just to the Windows Splash screen whereupon it would promptly reboot.
Ok thanks for the input Chris. I find it hard to believe the only hard drives that will work are refurbished Dell drives. The controller is able to see the drives, create an array with the drives, and shows them as optimal status both during startup and in the controllers bios. If the controller isn't compatible with the firmware of the drives then how come the controller can see them and create an array? Everything seems normal until Windows tries to boot.
It doesn't appear to be the driver. The drive doesn't have to be a Dell refurb, I was just giving some examples of listed 1TB drives, sorry about that. The issue appears to be the drives themselves though. If you have another system, you could confirm this to see if the issue follows those drives. Browse Community. PowerEdge OS Forum. Turn on suggestions.
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. Showing results for. Search instead for. Did you mean:.
0コメント