Hi Neil,

>I need to eject it from the pool and designate a new master. 

Did you eject it first from the Ui and then from the xencenter?

> But, I notice that I cannot make any storage changes to instances.  (I assume because the master does not have access to the storage

Please try to fix the storage and then scan it.

What is the current situation is the host master is being seen in XenCenter or not?

Is the SR has any cross mark on XenCenter.

Can you try to fix the SR first if it is showing a cross mark over it.

Hi Neil,

>I need to eject it from the pool and designate a new master. 

Did you eject it first from the Ui and then from the xencenter?

> But, I notice that I cannot make any storage changes to instances.  (I assume because the master does not have access to the storage

Please try to fix the storage and then scan it.

What is the current situation is the host master is being seen in XenCenter or not?

Is the SR has any cross mark on XenCenter.

Can you try to fix the SR first if it is showing a cross mark over it.

There is not a way to "fix the storage" without ejecting the master or changing the master to another host.   The storage NIC on the master needs to be replaced, and (according to Citrix) XenServer may need to be re-installed.    Hence, the master needs to be changed to another member and then ejected from the pool.

I got this resolved.
I didn't realize that CloudPlatform doesn't really care which host is the master.
In CP, I put the master host in maintenance mode and then unmanaged the cluster.
In XenServer, (because the network that the hosts were using for management was still working) I changed the pool master to another host and ejected the bad server from the pool.
Back in CP, I removed the bad host and turned management back on for the cluster.
Upon a clean install of XenServer on the bad host, it was clear that the Storage NIC card was bad and needed to be replaced.