• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 319
  • Last Modified:

2k3 server won't shutdown/restart

Hello,

I'm stumped on this one:  I have a 2k3 server that when I initiate a reboot, it logs off, exits out of explorer, and hangs at the blue background screen (not a BSOD or a BIOS black screen, just the regular wallpaper).  crtl+alt+del doesn't do anything at all, but the mouse still moves and the server isn't hung.  The drives appear to flash in synch with eachother at a pretty slow pace, so I'm guessing most of the operations have stopped but for a few.

I can only get it to go all the way down by holding the power button, which scares me.  Has anyone had this before that can shed some light?  Again, it logs off -> kills all windows processes and then just sits and never shuts off or reboots.
0
Maniac_47
Asked:
Maniac_47
  • 2
  • 2
2 Solutions
 
Mike_CarrollCommented:
This I have seen before a number of times. It always turned out to be a BIOS issue. Update your firmware and try it again.
0
 
beesterCommented:
Usually when this happens, it's because some process can't shut down. Did it start happening after you installed a specific software? Could you try upgrading all the drivers on the servers, and/or run all windows updates?
0
 
Maniac_47Author Commented:
The server has been fine for 4 years, its just started doing this.  I don't have much time to test it as it is a production server, but I'll try bringing it down a bit later today after running windows updates (I don't think thats what it is though).  

It looks like all the processes are killed and the only goofy event viewer messages I have from that time is a VOLSNAP error  8, would that be contributing?  MS says its related to breaking a software RAID1 mirror, but I don't have a software mirror, this server is running with a physical RAID controller
0
 
beesterCommented:
Could this be the problem you're experiencing?

http://support.microsoft.com/kb/930045
0
 
Mike_CarrollCommented:
As I've mentioned, I've seen this problem before.

In my experience, it seems to be caused by Windows updates - not sure whether it involves intended functionality with some sort of incompatibility or something goes wrong with the updates. The only other common factor that I've seen is older hardware with out of date drivers loaded.

On each occasion, I've been able to resolve the problem with a BIOS flash and I generally also update drivers at the same time.

I cannot say for definite that this is the problem you are seeing but I know where I'd be approaching from.
0

Featured Post

Configuration Guide and Best Practices

Read the guide to learn how to orchestrate Data ONTAP, create application-consistent backups and enable fast recovery from NetApp storage snapshots. Version 9.5 also contains performance and scalability enhancements to meet the needs of the largest enterprise environments.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now