Make a node a possible owner on a Cluster Shared Volume

I have a hyper V setup with 2 hosts and 1 san. Recently host 2 crashed and i had to rebuild it, most things seem ok and i can send VM's between hosts etc.
However if host 1 goes offline Host 2 can no longer use the cluster shared volume because it is not set as a possible owner.
Using Failover Cluster Manager I was able to set host 2 as a possible owner on all the other resources but that option is not there on the Cluster shared Volume.
So my question is how do I make host 2 a possible owner of the Cluster Shared Volume?
GWbjonesAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

kevinhsiehCommented:
What is the connection method from host to SAN? It sounds like host 2 isn't configured to directly access the SAN. If using iSCSI for example, go to the iSCSI control panel and connect to the CSV.
GWbjonesAuthor Commented:
Yes it is iscsi.
Host 2 can see all the drives from the SAN and host 2 also has c:\clusterstorage\volume1 where I can see all the vhd files for the VM's. The VM's do run on host 2 but only if host 1 is up!
GWbjonesAuthor Commented:
In my Failover Cluster Validation Report i get this

Validating cluster resource Cluster Disk 7 - (P:) Array6_CSV_OS.
This resource does not have all the nodes of the cluster listed as 'Possible Owners'. The group that this resource is a member of will not be able to come online on any node that is not listed as a 'Possible Owner'.
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

kevinhsiehCommented:
I would check out these two links.

http://support.microsoft.com/kb/313882
"From the command prompt, run the following command to add the other node to the Possible Owners list, where missing node is the node that is down:
cluster res name of resource /addowner:missing node  "


http://support.microsoft.com/kb/263317

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
kevinhsiehCommented:
You can also move everything to mode 1, evict node 2 from the cluster and then add it back.
GWbjonesAuthor Commented:
Thanks! I did try this yesterday but couldnt seem to make it work. going back with fresh eyes and all appears to be ok now.thanks again
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Virtualization

From novice to tech pro — start learning today.