Deployment freezing
-
I am running FOG .32 on Ubuntu Server 11.10. Attempting to Image/Deploy HP 6200 Pro MiniTower with Win XP SP3.
These systems came with Win 7 (and 3 partitions on HD). Reinstalled with XP and all updates. Uploaded image. Attempt to Deploy resulted in clients freezing at “random” points in the deployment - 0%; 38%; 56%, etc.
Removed all partitions, Created single partition, installed Win XP. Uploaded. Deployed successfully to systems that had had all partitions removed and single partition created… Continued with XP installation, updates, Office 2010, Adobe Creative Suite 5.5, a couple other programs and all updates… Uploaded. Deployment freezes at random points.
I have not Sysprepped, but I don’t see how that would make a difference here.
The HP 6200 Pro [I]desktop[/I] (not minitower, necessarily) is on the list of Working systems, with FOG version .32.
Please help. -
have you tried an updated kernel maybe?
-
[quote=“falko, post: 1503, member: 48”]have you tried an updated kernel maybe?[/quote]
I’m fairly new to FOG. How would I know if I have the latest kernel?
Would that be under “Other Information / Version Info”? -
you are most likely using 2.6.39.1 that was the default kernel.
Hope the below article helps,
-
[quote=“falko, post: 1506, member: 48”]you are most likely using 2.6.39.1 that was the default kernel.
Hope the below article helps,
[url]http://community.spiceworks.com/how_to/show/2338[/url][/quote]
Thank you. I AM using the 2.6.39.1 kernel… I went to the link you gave me and following those instructions to get the latest kernel results in an error “… filesize = 0”, which I looked up… Others had downloaded the newer kernel directly from SourceForge, which I did.
I then renamed the downloaded file (Kernel-3.2.4.core) to hp6200 and copied the file from Downloads into /tftpboot/fog/kernel.
I went into the properties for one of the hosts I’m trying to deploy to and changed the “Host Kernel” setting to hp6200.
I set up a new task to deploy to that host which then said “Could not find kernel image: hp6200”Not sure what to try next… Is there an issue with permissions on the hp6200 file? Does the file need to have an extension?
-
This post is deleted! -
[Addendum] I also tried to use the Kernel Update that WAS available through the FOG console method (Other Information/FOG Kernel Updates), which was listed as, “Kernel - 3.1-rc8 Core (Use with caution!!!)”. I figured, “what have I got to lose?”, right?
Same message from the host - “… Could not find kernel image: hp6200pro” (hp6200pro is what I instructed the software to name the kernel during the download).
Just thought that info might help. -
hosts settings needs to be along the lines of the below (basically the full file path, i cant remember of the top of my head)
/fog/kernel/hp6200
edit: see the last picture in the link i sent
-
[INDENT]I am having the same problem. As a workaround I deploy images manually as described here: [url]http://fogproject.org/wiki/index.php?title=Troubleshooting_an_image_push_to_a_client[/url][/INDENT]
-
[quote=“falko, post: 1688, member: 48”]hosts settings needs to be along the lines of the below (basically the full file path, i cant remember of the top of my head)
/fog/kernel/hp6200
edit: see the last picture in the link i sent[/quote]
Okay… just wanted to update… I (temporarily) gave up on renaming the kernel file just to see if simplifying would help. It did.
I just followed the directions for downloading a newer kernel (the newest one still doesn’t dl properly - says size=0) and LEFT THE DEFAULT FILENAME. I then left the kernel designation blank for the new workstation and the deployment (at least to just that single machine) went through - 100%. This is about a 22GB image in about 6 and a half minutes!
Thank you, Falko! You’re awesome! Hope I can return the favor some time.
-
[quote=“falko, post: 1688, member: 48”]hosts settings needs to be along the lines of the below (basically the full file path, i cant remember of the top of my head)
/fog/kernel/hp6200
edit: see the last picture in the link i sent[/quote]
Okay… just wanted to update… I (temporarily) gave up on renaming the kernel file just to see if simplifying would help. It did.
I just followed the directions for downloading a newer kernel (the newest one still doesn’t dl properly - says size=0) and LEFT THE DEFAULT FILENAME. I then left the kernel designation blank for the new workstation and the deployment (at least to just that single machine) went through - 100%. This is about a 22GB image in about 6 and a half minutes!
Thank you, Falko! You’re awesome! Hope I can return the favor some time.