Hyper-V Failover Live Migration failed. Error 21502
-
EDIT: Just to be clear when I first started the troubleshooting I had 1 problem. After the first problem cleared I encountered with the second problem. So if you skim through the thread you may get confused very quickly.
I have been trying to configure a vSAN by StarWind with 2 node for the past weeks. With multiple guides and help from the community, still I cannot test LIVE MIGRATION. Quick Migration does works so I do not quite understand Why?
note: Quick Migration works. Force migration via restarting the server works. Live Migration failed confused
From my initial research I know the cause is probably something to do with setting or naming. Something is not identical and is causing the failure between the node. I configure the server mirroring each other from scratch and still the problem exist.
Here are some screenshots. Hopes it helps to narrow down the cause
-
-
Let's ping @KOOLER @StarWind_Software @original_anvil
-
@Lakshmana
This article pointed out problem with authentication http://www.virtualizationadmin.com/articles-tutorials/microsoft-hyper-v-articles/general/diagnosing-live-migration-failures-part2.htmlThis article resolved the problem http://www.hyper-v.nu/archives/pnoorderijk/2013/03/microsoft-virtual-system-migration-serviceservice-is-missing/
Also, my Active Directory is a bit of a mess so there are multiple security setup that inherited when it should not. Restore to default and unchecked inherited resolve that.
Thank you for the article!
-
So after the whole Live Migration failure, I have managed to bring it online, as screen shot above. Now all the setting should be set correctly, however it still failed on me when I try to create a VM with 2GB memory. I named it Zeus (stole the idea from the naming server idea).
At this point I am dumbfold and confused. Life as a sole admin is hard.
Helo me MangoLassi, you are my only hope.
-
The error seems kinda self evident - not enough disk space. How much freespace in the Hyper-V data store is there?
-
@LAH3385 That error looks like you might have run out of storage at an unexpected place. I know you've probably looked already, but someone has to ask. Do you have 2GB of free space on that C drive?
-
@Dashrender
The cluster storage space is configured with starWind vSAN. I gave it a good 1TB (1,0001GB)
-
@LAH3385 said:
@Dashrender
The cluster storage space is configured with starWind vSAN. I gave it a good 1TB (1,0001GB)
Right, but the error is claiming it's on the system drive.
-
@travisdh1
The VM reside on the cluster drive on C:\clusterstorage\volume1
I might be overlooking this and screwed up somewhere along the way.. but shouldn't C:\clusterstorage\volume1 be a virtual drive? connected by iscsi?
-
Show us the Disk Manager view for your drives, please.
-
-
Am I seeing correctly? the CSVFS (Disk 3) is not mounted anywhere?
Maybe this view doesn't actually show mount points that aren't just a drive letter? -
can we see the output from Mountvol.exe
I found the info at http://thenubbyadmin.com/2012/03/15/listing-all-volume-mount-points-on-a-windows-server/
-
@Dashrender
Now that you mentioned that. somehow the drives on both server (which should be identical) is not.
-
@Dashrender
here is the mountvol.exe result.
-
awww - I think I see the problem.
Your volume on Disk 3 is set to 1 GB, not one TB. You only have 888 Megs free on that volume, and you need 2 GB (2048 MB) free for the RAM disk.
though I'm not sure how you installed Windows into a 1 GB partition.
-
Can you do a details based listing of what is is c:\clusterstorage\volume1?
-
@Dashrender
From your previous message currently I am redoing the whole iscsi and volume clustering. I will report back if the problem resolved. -
@LAH3385 said:
@Dashrender
The cluster storage space is configured with starWind vSAN. I gave it a good 1TB (1,0001GB)
What I can't tell, is this graphic showing 1.001 GB or 1,001 GB?
Assuming it's showing 1,001 GB (nearly 1 TB of space), this is only showing the whole array, not the the partitions that you created in the array.
