Client won't upload image
-
New user to FOG, I’ve been trying to set it up for the last few days. I have been able to answer most of questions browsing this forum, but I haven’t found a solution to why my client won’t upload an image to fog. I thought the upload was successful, because the image showed up on FOG, but the image file wasn’t actually there, because when I try to PXE boot the image from another machine I get the message “unable to locate image file for <image> sys.img.000”. I tried to manually put an ISO on the server, but when I try to PXE boot my other machine, I get the message "can’t read the following volume file: /images/<image> Can anyone help?
I am running FOG 0.32, and Ubuntu 12.04 LTS on the server
-
When you upload the image, does the Fog client report that it was successful? If it has any issues, you should see messages on the client screen. Fog is good about that. Also, the format of the image is not an ISO. I’m not familiar with the format or type of file it uses, but I know enough that it is not an ISO. What OS are you cloning? When you created the image definition, what type did you pick? When we clone our Windows 7 machines, we choose Multiple Partitions, all disks, not resizeable to insure it grabs that annoying little 100 MB partition Windows 7 likes to create. There are other ways to clone Windows 7, but this has worked well for us…
-
It does not report successful on the client machine. I haven’t seen any messages on it, actually. I am trying to clone a Windows 7 machine, I just tried the multiple platforms all disks option and got a message I haven’t seen before. I am working on the FOG machine, I selected the host I want to upload from, I clicked upload, and it gives me the message: Unable to start task
-
Hmm, if the computer has successfully uploaded shouldn’t the next step be deploy? What happens when you try to deploy this image?
-
When I try to deploy it to my other client I get the “unable to locate image file for <image> sys.img.000” message as if the image is not uploaded to the FOG server. I don’t think it is actually uploading the image, because I would think the wait time would be much longer than it was…This is why I tried to manually put the image on the server, to see if it was the uploading or the deploying that was the problem. I believe it is the upload.
-
Haven’t done any in a while, but I think an upload can take several hours depending on the data. If you look in /images on the fog server, what do you see and how big is it?
-
Is the path for the images folder fog_0.32/packages/tftp/fog/images? Am I checking the right place? The only thing there is “init.gz”
-
On my server it is off of the root folder, or /images
-
Okay I went to that folder and in it is a folder titled “dev” with nothing in it
-
OK, so based on my limited knowledge here is what I think is happening: The imaging of the client completes to the temp area, but the tftp from the temp area to /images is failing. I know there are lots of posts and help in the Wiki on that so I’d suggest searching for tftp failures or errors for some troubleshooting ideas.
-
If I go into the tmp folder under root, it is the same as the images folder. There is a folder titled “images” and within it is an empty folder titled “dev”. I don’t think it is uploading the image at all. Is there a way to verify communication between the server and client? I can ping the server successfully, but is there anything else?
-
I think the temp folder is dev in /images. Try looking in thete. Refer to this for some tftp troubleshooting [url]http://fogproject.org/wiki/index.php?title=Unable_to_connect_to_TFTP[/url]
-
Thank you for all the help. I remember checking this multiple times before I started my own thread, but it turns out I wasn’t editing the root version of the config.php file. I just changed it to match my password, and I will update you on if the image was uploaded successfully tomorrow. Thanks again.
-
I just started the upload, and when the task started, the client I am uploading from immediately restarted, and now it keeps restarting itself about 30 seconds after start up…
-
Let me see if i understand correctly, you started an upload, the client rebooted, now the client just keeps rebooting. Is it still trying to load the PXE boot when it boots or is it trying to boot from the local disk?
-
The machine I am uploading the image from has never been set to PXE boot, it just boots locally. I am trying to upload the image from that machine, and then PXE boot it on a second client computer. Just got in this morning and it is still rebooting, and there is still nothing in /images
-
I guess I am still a bit confused. When I upload an image I create the task in Fog for that host, then PXE boot the computer to load the Fog client and execute the upload task. On our desktops (HP) I just use the F9 key at boot to select PXE as the boot method. At the end of the upload process the desktop shuts down.
Once I have the image uploaded to Fog, I create a deployment task for the destination hosts and set them to PXE boot (using F9) so that the Fog client loads and the image is deployed. After the image is deployed, the computers reboot.
If you don’t PXE boot the computer to Fog, what method are you using to upload the image?
-
Looks like I was the confused one, I never tried to PXE boot to fog with the client I wanted to upload. Image is uploading now. Thanks again for all the help.
-
You are welcome. I’m happy to help. Good luck with Fog. It’s a great solution.
-
I was able to get the image to download to the client, but when it boots and I select boot from hard drive, it boots and opens start-up repair. I tried to have it fix the problem, but every time I boot it goes back to repair. Suggestions?