Home > Hyper-V, SCVMM, Windows 2008 R2 > Add possible Owner to a Cluster Shared Volume

Add possible Owner to a Cluster Shared Volume

Another interesting issue this evening, today I added a Hyper-v host server to an existing cluster using System Centre Virtual Machine Manager 2012 (which rocks BTW). As part of the process to add the node you click a button to say add this node to this cluster and provide some credentials and off it goes and performs some validation tests before actually adding it to the cluster, this is great I hear you say….. In this case the node was added to the cluster and I start to check to make sure everything was OK before loadng the dad boy/girl up with VM’s when I happen to notice the the CSV’s LUNS were not attached it puzzled me how VMM 2012 thought this was OK……

Anyway I connected the LUNs and proceeded to load him/her up and moved onto the next node to take out of the cluster for maintenance, as part of this process I wanted to move the owner of a CSV disk first. so I go into Failover Manager find the CSV resource and select migrate to other node…. Only to be presented with


Operation has failed.

The action ‘Move to node <nodename>’ did not complete

Error code: 0×80071398. The operation failed because either the specified cluster node is not the owner of the group, or the node is not a possible owner of the group


Uh OH.. I have had enough problems with this cluster/SAN/CSV’s (that’s anther story put is this way one of the CSV’s ‘lost’ it’s partition information). I surmised that because the CSV’s were not presented to the server when it joined the cluster it may not had updated the “Possible Owners list” and sure enough this server was missing a few command laster and were are back in business.

note command needs to run from a Admin commpand prmpt


To tell who are the possible owners run:

Cluster res <resource name> /listowners


To to add a server to the list

Cluster res <resource name> /addowner :<servername>


Hope this helps

Categories: Hyper-V, SCVMM, Windows 2008 R2 Tags:
  1. DRGilroy
    October 9, 2012 at 11:56 pm

    Thanks for this, it was exactly what I needed!

  2. Gabe3000
    March 23, 2013 at 4:55 am

    That was amazing.. we ran into this when we joined some new hosts to a hyper-v cluster, but didn’t have the CSVs visible yet on the new hosts.. so, storage went into redirected mode, and then we made the volumes visible via the SAN, and redirected mode went away. But apparently, the CSVs couldn’t be owned by the new hosts, so this little shortcut provided the perfect remedy in a late-night maintenance. You rock. 🙂

  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: