My server was running a bit slow then I requested a reboot via fdc helpdesk and it failed. Right now im still waiting on support to reply to my ticket to get it back up. 30minutes and going.... Anyways I was wondering if anyone could give me on some ideas why a reboot would fail?
When you request a reboot from most DCs they just hit the reset button on the server. This has the potential of forcing a file system integrity check which can take a considerable amount of time to run. Why didn't you just use the reboot option from within the OS? You should only request a reboot from the DC if the server is fully unavailable.
Enterprise Network Engineer :: Hosting Hobbyist :: Master of Procrastination
"The really cool thing about facts is they remain true regardless of who states them."
You should open a ticket with the help desk have them to log on to your servers and setup your network configuration again. e.g. I discovered this problem after some complaints from customers about rebooted servers not coming back online. When I investigated I discovered that the IP stacks weren't initializing because they were failing due to an IP address in use already issue. It appears that this problem was caused by some misconfigured equipment.
1: Logon to the console of the server. I have console access to my root nodes. (you'll probably have to have them to do this.)
2: #ifconfig eth0 <ip.address> netmask 255.255.255.0 up
3:# route add default gateway <gateway.ip.address>
4: Ping the gateway.ip.address