Basic Image Capture Stuck in Loop

[bnorwood]

Here is my setting on the image.

[Sebastian Roth]

@bnorwood What? 7 hours for not even 35 GB? There Muster be something wrong with virtualization or disk controller or network drivers.

[bnorwood]

@Sebastian-Roth I am running a Windows 2016 Server with 32 GB RAM and Xeon CPU E5-2640 @ 2.50 GHz. I have Hyper V loaded using manager 10.0.14393.0. I have two VMs set up. One is the FOG Server and the other VM is the machine I use to update/capture mages from. There is nothing else running on this server. I have the virtual switch manager running an external fog switch with a 1GB connection. Both the Fog server and client VM are running at 1 GB. I have them both set to 16GB Memory and 8 virtual processors. I only have the compression set to 4 in the Fog GUI. Not sure why it takes so long.

[bnorwood]

Here is a screenshot of my Hyper V

[Sebastian Roth]

@george1421 Would you have an idea why it’s that slow?? You have more experience with HyperV than I have!

@bnorwood I remember we had a performance issue some time ago but this was fixed. As I see you are running version 1.5.5 I don’t think this is the same problem. Here are the details just for reference: https://forums.fogproject.org/topic/6695/performance-decrease-using-hyper-v-win10-clients and maybe https://forums.fogproject.org/topic/6966/uploading-an-image-from-hyper-v-is-extremely-slow

[bnorwood]

Here are some screen shots at the end of the capture and errors.

[george1421]

@Sebastian-Roth said in Basic Image Capture Stuck in Loop:

You have more experience with HyperV than I have!

Sorry I have zero experience with hyper-V. We are a vSphere shop.

But I remember something like this in the forums from a while ago. I think it had something to do with the disk controller that was used, but it is a vague memory.

[bnorwood]

[bnorwood]

[george1421]

@Sebastian-Roth said in Basic Image Capture Stuck in Loop:

As I see you are running version 1.5.5

I would also ask what version of FOS Linux is installed. From quick search of the forum it looks like a rsched issue was resolved in 4.19.6 and later.

[bnorwood]

@Sebastian-Roth From what I am reading it is an issue with the virtual switch manager using the Legacy Network Adapter only running at 100MB. That would account for the long capture time. The forum link didn’t address if there is a fix for this. I am using the Legacy Network Adapter as per the setup instructions. I have “real” NICs available but not sure how to use them instead of the Virtual Switch Manager. Thoughts?

I also reset all the username and passwords to match after seeing the error code. I think the storage one may have been bad.

[Sebastian Roth]

@bnorwood said in Basic Image Capture Stuck in Loop:

I also reset all the username and passwords to match after seeing the error code. I think the storage one may have been bad.

We try to tell people to not mess with the FOG service account (called fog up to 1.5.5 and fogproject since 1.5.6). If you change the password of that account you run into trouble. Make sure you read and understand this: https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_FTP

Probably best if you open a new topic for the HyperV performance issue so we keep things sorted and other users will find the answers to their questions more easily.

[bnorwood]

@Sebastian-Roth The password error solved the capture issue. I have successfully captured the image. Thanks for the help! I will start another thread on the Hyper-V slowness issue.