this one is really doing my head in, I have a three node cluster (2003 R2
Server) which has been running since 2005.
My current problem is this one of my clustered nodes suddenly blue screened
and restarted itself. Which is normally no big deal however this time the
clustered resource failed to move to another node. The resource group tries
to move across but hangs in a "pending state" The virtual server comes
online along with the IP address associated with it. The problem seems to
lie with the physical disk not coming on line so none of the resource shares
come online either.
I can not fail the resource or anything as it come up with the resource is
not in a state to respond!!
I have tried everything to get this back on line to no avail restart all
nodes change all services to manual and start up in every different sequence
possible turned off the entire cluster including the SAN rebooted in order.
Even tried removing the other two nodes and their resources and the group
still hangs. i have changed the fail times the way it fails etc to no avail
:(
Please can somebody help?
really stressed
Paul Kernohan
You need to look through the cluster.log to find out why your resources are
not coming up. You can search the log for "DisksIsVolumeDirty" to get the
line where cluster is checking for the dirty bit. If this says that the disk
is dirty, it's going to perform the chkdsk before bringing the resource
online. If this isn't a chkdsk issue, look for ERR or WARN entries regarding
your disk resource.
Regards,
John
Visit my blog: http://msmvps.com/blogs/jtoner
"Paul Kernohan" <PaulKe...@discussions.microsoft.com> wrote in message
news:A0184692-7CA4-4573...@microsoft.com...