Why the VHD file is always shows error?
This is a 2-host MS HyperV 2012 setup, with 8 VMs within. Both hosts are sharing the same SAN Storage, and 2 volumes were created in paths - c:\clusterstorage\volume1 and volume2, respectively. However, whenever I tried to move some of the the VHD (or VHDX) files to different volume or host, the error occurs as attached.
I just took over the administration of the above virtualization setup. I not sure whether this is because both volumes are not CSV, but, does it mean that both volumes have to be converted to be CSV (Clustered Storage Volume)? I check the host resources are enough, what else?
Thanks first, hope you guys could be any help.
EE---MS-HyperV-27000.jpg
I just took over the administration of the above virtualization setup. I not sure whether this is because both volumes are not CSV, but, does it mean that both volumes have to be converted to be CSV (Clustered Storage Volume)? I check the host resources are enough, what else?
Thanks first, hope you guys could be any help.
EE---MS-HyperV-27000.jpg
ASKER
Hi Philip Elder,
On my second visit, found that all 3 volumes are already CSV. However, I found out 2 new things:
1st, the VHD file is "somehow" attached to the different host in Disk Manager. After "detach" the VHD, and I can rename/move the it.
2nd, attempt to "live migration" any of the VM still failed. Found the cluster network could be the culprit. There are 2 cluster networks, cluster network 1 have both nic1 of host1 and host2 for private traffic. However, cluster network 2 only have host2 component for vSwitch.
Both host1 and hosts are configured with same vswitch name, but, only host2's one is listed. I'll scheduled to re-create vswitch on host1. Since this needs downtime, so, I have scheduled to get it done tomorrow. Please see my update.
On my second visit, found that all 3 volumes are already CSV. However, I found out 2 new things:
1st, the VHD file is "somehow" attached to the different host in Disk Manager. After "detach" the VHD, and I can rename/move the it.
2nd, attempt to "live migration" any of the VM still failed. Found the cluster network could be the culprit. There are 2 cluster networks, cluster network 1 have both nic1 of host1 and host2 for private traffic. However, cluster network 2 only have host2 component for vSwitch.
Both host1 and hosts are configured with same vswitch name, but, only host2's one is listed. I'll scheduled to re-create vswitch on host1. Since this needs downtime, so, I have scheduled to get it done tomorrow. Please see my update.
In Failover Cluster Manager under the Storage node you should see OWNER for each CSV. That's why the disk shows up on one node and not the other. The cluster service takes care of arbitrating calls to the storage via the OWNER.
Before doing anything please post the following via elevated PowerShell in a TXT file from each node:
Get-NetAdapter
Get-NetLbfoTeam
Get-VMSwitch
Get-VMhost | FL Name,VirtualHardDiskPath
Get-VMHardDiskDrive * | FL
Before doing anything please post the following via elevated PowerShell in a TXT file from each node:
Get-NetAdapter
Get-NetLbfoTeam
Get-VMSwitch
Get-VMhost | FL Name,VirtualHardDiskPath
Get-VMHardDiskDrive * | FL
ASKER
Hi Philip Elder,
I will go onsite tomorrow. Will update you the status.
I will go onsite tomorrow. Will update you the status.
10-4
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
Elevated PowerShell and post to TXT:
Get-NetAdapter
Get-NetLbfoTeam
Get-VMSwitch
Get-VMhost | FL Name,VirtualHardDiskPath
Get-VMhost | FL Name,VirtualMachinePath
Get-VMHardDiskDrive * | FL
Get-NetAdapter
Get-NetLbfoTeam
Get-VMSwitch
Get-VMhost | FL Name,VirtualHardDiskPath
Get-VMhost | FL Name,VirtualMachinePath
Get-VMHardDiskDrive * | FL
ASKER
Problem resolved by following the given actions.
Any additional LUNs that are hooked into the two nodes must have the Add Cluster Storage step run then Add to Cluster Shared Volumes.
Once they are in CSV, you'll see Volume3 and Volume4 ETC.
In Failover Cluster Manager use the Storage Live Migration process to move the VHDX files from their current CSV to a new one. This can be done so the VM does not have to be taken offline.