@hvaransky I am assuming something is wrong with our kernel. I received this error when trying to run debug capture:
Posts made by hvaransky
-
RE: Capture stuck after 1st partition
-
RE: Capture stuck after 1st partition
@tom-elliott We are running 1.4.4 with what looks like Kernel version 4.11.0. We will try again with a debug capture task and see if it gets any further.
-
RE: Centos Help
@george1421 We were trying an HP 8200 Elite, however, we also tried a 4300 and got the same result.
-
Capture stuck after 1st partition
We are currently trying to capture a new windows 10 image and it keeps getting stuck after successfully capturing the first partition. It finishes 100% and then cloned successfully shows up at the bottom and it never goes on to the next partition. I double checked the image management and have windows 10 selected, image type is set to multiple partition image- single disk, and tried using both Partclone ZSTD on compression 11 or Partclone GZip on compression 9, and both stop at the same place. We also tried another computer and it still the same thing. Any help is appreciated!
-
RE: Centos Help
We have gotten further than you have, with using the undionly file, however, our image has 3 partitions, and only the 1st one will write. After it finished, it says cloned successfully and stops. We are also using CentOS with Fog version 1.4.4
-
RE: Rate is at a slow crawl when trying to deploy/capture image
@george1421 I couldn’t get the 2nd part of the command line to work as I kept getting permission denied. I was able to use the built in benchmarking on the disks menu to come up with the screenshot below:
We also double-checked all of the switches last night and all seem to be set properly and rebooted the FOG server. I am going to try to capture a new image with the ZSTD compression instead of Gzip. On the downside, after changing compressions on the image and it starting out super high transfer rate yesterday, it still took over 8 hours to complete and the rate almost bottomed out by the time it was an hour in.
-
RE: Rate is at a slow crawl when trying to deploy/capture image
@junkhacker We’re not really worried about compression size per say. We would rather it take less time for an image to deploy. (It was running at about 35 minutes per machine last summer and is now taking more than 7 hours to complete.) On the plus size, once changing compression size on the current image I’m deploying, it is predicted to only take about 3 1/2 hours to finish!
-
RE: Rate is at a slow crawl when trying to deploy/capture image
@tom-elliott I changed the rate down to 6 and deployed the image again. It started out at 10GB/Min, but within 10 minutes it is down to 247MB/Min. I’m at 44% completed with it running for an hour and 22 minutes, which is definitely MUCH better, but is there something else I need to adjust to get it even quicker? The rate is still dropping (it is going down at about 2MB every 3 minutes or so). Sorry for all the questions, I really am a newbie with FOG.
-
RE: Rate is at a slow crawl when trying to deploy/capture image
@tom-elliott I understand about the compression rates, but I’m not sure about the Gzip/ZSTD stuff. All of our images are set to partclone Gzip as per screenshot. Am I safe to assume that I have something set up wrong in the image management?
-
RE: Rate is at a slow crawl when trying to deploy/capture image
@wayne-workman I took 2 because I’m not exactly sure what we’re looking for. The compression is set at 22 and the image size is 465GB.
-
RE: Rate is at a slow crawl when trying to deploy/capture image
@wayne-workman The computer that I imaged last night is in the same building, but is through a different switch. I tried an image last week that took 7 hours and 44 minutes and was connected to the same switch. They are two different images, but both were made around the same time for HP desktops.
-
RE: Rate is at a slow crawl when trying to deploy/capture image
@wayne-workman I did run the ethtool utility and the speed is set at 1Gbps. I also did an ifconfig and am getting RX at 419.0MB and TX at 20.6GB. I restarted the server and reset the services yesterday as well. I thought maybe it was because I was trying to image during the day when the network is being hit hard, so I waited until most everyone left, but it still took over 7 hours to complete. Connection between server and host computer looks to be okay as well. I did look back at the imaging reports, and the same image only took 1 hour and 7 minutes last July.
-
RE: Rate is at a slow crawl when trying to deploy/capture image
@wayne-workman Thank you!! Will definitely try those options!
-
Rate is at a slow crawl when trying to deploy/capture image
Very much a newbie FOG user here, so if this question sounds stupid, I apologize!
I am trying to both deploy and capture an image and everything starts out great until I get to the actual deploy/capture. The rate starts out High, but within 30 minutes, goes so low (20-60MB/Min) that I end up canceling the task because it’s taking over 24 hours to actually complete. I did let a deployed image go and it did actually complete the deployment and image seems to be running okay on the computer that I put it in. The image that I deployed was made last July and it worked great (rate ran at about 1.5GB/Min) the whole summer while re-imaging. I’ve only noticed it be this slow since about December. I have tried rebooting FOG server and restarting the services but nothing helps. We have not ran any updates on the FOG server or updated it. Currently running FOG 1.4.4 or Ubuntu 14.04.
-
Exit Code 1 Error when deploying image
Server
- FOG Version: 1.4.4
- OS: 14.04
Client
- Service Version:
- OS: Windows 7
Description
Trying to deploy images and they keep failing, even though I have used the same images to deploy about 45 other computers… I am using an image that successfully deployed just 1 hour before unicasting this one. The computers are both Dell Optiplex 380s with the same hardware inside.
The error comes up: Image failed to restore and exited with exit code 1 (writeImage).
I also get a read error towards the bottom when i tries to continue.
I’ve restarted both FOG service and the FOG server in hopes that something was just off, but nothing helped.
Any advice or insight? -
RE: Can't WOL & Deploy across subnets
@Wayne-Workman We tried to use the location plugin and am getting the same error as the WOL plugin.
-
RE: Can't WOL & Deploy across subnets
@Wayne-Workman Here’s the screenshot that we are getting when trying to create the new WOLbroadcast.
We are working on getting a storage node setup on another VLAN now.
-
RE: Can't WOL & Deploy across subnets
@Quazz there isn’t any error, it just never starts. It shows the image name that it’s supposed to be deploying, but it won’t load the partitions. This isn’t working with multicast, however, we did try to unicast and it worked. I’m assuming it has something to do with multicast settings…
-
RE: Can't WOL & Deploy across subnets
@Tom-Elliott When we try to configure WOL broadcast management we get “ID must be set to edit” error.
-
Can't WOL & Deploy across subnets
Server
- FOG Version: 1.4.4
- OS: Ubuntu 14.4
Client
- Service Version:
- OS: Windows 7
Description
We are able to use all features on the machines that are on the same subnet as our fog server, but once going to our other subnets, WOL and deploying images won’t work. We have registered and all machines and can PXE boot but they get stuck after loading partclone. We’ve tried to enable UDP broadcast forward but the command keeps coming up invalid in our HP switches.