Windows Datacenter 2008 R2 Failover Cluster Manager will not start

Posted on 2009-12-23
Last Modified: 2013-11-11
We are running a 5 node Windows Datacenter 2008 R2 Failover Cluster that we are using for Hyper-V with a Cluster Storage Volume that will not start because our physical domain controller (another DC is sitting on the CSV that we can't access) and now we get the following error when trying to bring the Cluster Service online within the Failover Cluster Manager.  

Node 'BLADE01' failed to establish a communication session while joining the cluster. This was due to an authentication failure. Please verify that the nodes are running compatible versions of the cluster service software.

What are our options.  Has anyone used the Force Cluster Service online option successfully and will it work for our scenario.

Thank you in advance for any and all assistance.
Question by:Patrick Nunez
    LVL 7

    Expert Comment

    Is it an option to stand up another DC (physical or otherwise) that may allow the clustering service to start? I'm afraid in this situation you still need authentication and I'm not sure that forcing the cluster service (which I have not done myself) would work in this situation because it's a communication issue between you and a DC (that isn't available) thus the authentication errors.
    LVL 1

    Author Comment

    by:Patrick Nunez
    We have engaged Microsoft for assistance.  1st step was to reassign the LUN from the cluster to a single box.  We did this and can see the drive but it is listed as RAW.  Waiting for next option.  Will keep you posted on the outcome.
    LVL 1

    Accepted Solution

    Microsoft was not able to assist on the recovery.  Reassigning the LUN to one of the servers not in the cluster only presented the drive as RAW format.  Microsoft had us run chkdsk against the drive and it would continually stall at 66%.  The recommended solutiona at that point was data recovery such as Ontrack.....thank you very much but we will keep digging on our own.

    We ran Power Data Recovery against the 2tb "RAW" drive and after countless hours we were able to see the content of the drive.  We extracted out the VHD containing the DC and mounted to a blade not in the cluster.  The domain controller fired up without a hitch.  Once the domain was up we reassigned the LUN back to the cluster and fired up the nodes.  The cluster started perfectly.

    If anyone has further questions, let me know.

    Featured Post

    Want to promote your upcoming event?

    Is your company attending an event or exhibiting at a trade show soon? Are you speaking at a conference? Spread the word by using a promotional banner in your email signature. This will ensure your organization’s most important contacts are in the know.

    Join & Write a Comment

    Scenario:  You do full backups to a internal hard drive in either product (SBS or Server 2008).  All goes well for a very long time.  One day, backups begin to fail with a message that the disk is full.  Your disk contains many, many more backups th…
    Know what services you can and cannot, should and should not combine on your server.
    This tutorial will walk an individual through the steps necessary to configure their installation of BackupExec 2012 to use network shared disk space. Verify that the path to the shared storage is valid and that data can be written to that location:…
    This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles to another domain controller. Log onto the new domain controller with a user account t…

    733 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    17 Experts available now in Live!

    Get 1:1 Help Now