@florent
Didn't see your message until now about only applying the fix to only 1 client.
I did do a warm migration on client with ticket #7748053. This completed without issue!
I tried a warm migration on client with ticket #7747444 and this failed again. Sounds expected as the patch was not on this one yet.
Can you push the patch to client with ticket #7747444. Thanks!
Ticket#7747444
and I just opened another ticket for the other client that is having the same issue. Ticket#7748053.
Support tunnels should be open for both clients.
Thanks!
@florent
Thanks for the update on this. I have confirmed the 2 clients that we are having issues with the data drives are not divisible by 2MB.
How do we go about applying this patch?
Is there anything in the logs he provided that stand out?
Thank you for pointing me in the right direction for those logs.
I have attached those here.
Disk that seems to hang at 99% is WE-FS1/WE-FS1_1.vmdk. I see in the logs "Error: task has been destroyed before completion" but this would have been me from restarting the toolstack as the task just hangs there. I don't see much info/errors before.
Tried a couple of times to migrate this machine so might see a couple of attempts.
11/14 @ 2:05 ish
11/14 @ 7:41 ish
Logs.txt
@florent
I'll add some more on this.
I did attach the task log here.
.tasklog.txt
Now I did have to restart the toolstack as I wasn't able to cancel the migration task (after it hung). As stated, it hangs at 99% and says "estimated 3 minutes" to complete. I have left this run for over an hour but still says 99%.
I have tried this multiple times but get the same result. Support did mention to try and kick off the import via CLI which was tried in my last attempt. Unfortunately, same result.
I'm new to XCP, but you mention "xo should say something about " nbdkit logs of ${diskPath} are in /tmp/xo-serverxxxx" do you know where exactly I can pull those? Tried looking under /var/log of XOA but not seeing what you mention.
Side note. After restarting the toolstack and going into storage I could see the drives for that server. For testing I did create a new VM and attached those existing disks. The VM did boot up and the data drive was there and accessible. Though skeptical as technically the migration of that drive didn't get to 100%.