Posts made by Jaymes Driver

@coop90 Not likely. Typically when the SSD is present and there are issues, the issues are with the recognition/initialization of the disk.

FOG finds the disk, or the image wouldn’t be pushed.

@george1421 said in Dell XPS 8700 PXE boot error:

FWIW: In my environment we use MDT to create our golden/master/reference image and FOG to capture and deploy it across our campus of 12 different models of devices. You can’t beat FOG for time to deploy with almost any other platform.

Boy do I second that notion! FOG beats the pants off of WDS in my corporation. I also particularly enjoy the fact that after I deploy my image… it works. I don’t have to spend any time troubleshooting why something wasn’t “installed” on my image due to the windows imaging process <.<

Sure sometimes I have an issue, but I just push the image again and do my happy dance (3 minutes later the image is done and I spent very little time troubleshooting it).

They keep trying to shove SCCM down my throat. I will use the SCCM, I just won’t use it for imaging. (If it’s not broke don’t fix it!!!)

@cfsalyer Hey, that’s good news!

Please let us know if you have other issues.

I am glad to hear that removing option 60 solved your issues. Was option 60 something that was required by WDS?

Sometimes using an IP Helper address at the switch can help to resolve these issues too, but it appears like your clients are now getting the proper boot file.

@cfsalyer Yes, that was precisely what I was asking. and thank you for providing the full file. It appears that the menu file is being displayed… so its a matter of determining why the client is not completing it’s tasks.

Can you please provide a screen shot like George has asked?

Usually the pictures can provide us with a bit more information so that we can determine the cause of the issue.

I appreciate you taking the time to provide the information we have requested, it greatly helps in finding the resolution.

You should see more than just those few lines.

Can you test for me with a different machine an let me know if it sees the fog menu?

What provides your DHCP/Where did you make the changes to provide your pxeboot file information?

Do any of your clients see your FOG boot menu?

What happens if you open a browser and navigate to http://ip.of.fog.server/fog/service/ipxe/boot.php

Change the ip.of.fog.server to the ip address of your fog server please.

When do you see this error?

As soon as the client connects to the FOG server to upload the image, or do you see this error after the capture has completed?

I am curious, as you are able to get the file from the command line, so everything appears to be in order, and your client is attempting to pull the pxe files. I am curious if you see the menu or when the error occurs, it may help to find a resolution for you.

I couldn’t agree more!

And being opensource, it has the ability to do more than just DHCP and routing.

I use my pfsense router as a webfilter and also use it for NAT/internet rules (I shut my internet off at night except for certain devices).

I love the control that pfsense gives you, and I also enjoy the easy set up with fog

@fredlwal

Do you have a webfilter appliance?

You may have to add launchpad.net to the whitelist, or the bypass list so that the traffic is not monitored?

We filter all traffic anything ssl gets decrypted and sent down to the client (basically a man in the middle) and I had to add the url to the bypass list so the traffic is not decrypted.

I could get to the website fine, but I saw issues with adding the repository. (I even added the repo to the sources.list which helped some but not completely.)

I can confirm personally as I own these devices and use Ubuntu 16.04 on them, they will in fact work with this version of linux installed.

I used a single hard drive in my instances and did not use any of the on board raid configurations or NAS/SAN options.

@Tony-Ayre

Thank you very much, This may help someone in the future with a similar issue

I appreciate you taking the time to explain your issue and your resolution!

@Blsmith I just used clonezilla to clone a FOG installation yesterday! You shouldn’t have any issues.

LVM should be supported by clonezilla, even if it is multipathd.

Let us know how it goes.

I find this funny

We changed the name of the icon from “upload” to “capture” to help alleviate the issues we see with this.
I don’t see any reason why changing the color would hurt anything!

@Developers Anyone disagree?

Can you test the Mysql connection please?

mysql -u fog -pPasswordHere -D fog
exit

This will let us know if the service is running and if a connection can be made.

You may want to restart the service as well

service mysql restart

I usually leave the mysql password blank though…

If all else fails check out this section of the Wiki:
https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_MySQL#Ubuntu_13.04_14.04_15.04_and_higher_with_FOG_1.2.0

It may give some insight, not certain if we still have these issues or not, but it wouldn’t hurt to check the settings and verify the passwords are correct, it definitely seems like a password setting.

@Tony-Ayre Would you mind elaborating on the issue, so if others have this issue, they will have a resolution?

@craigcoulson said in Debian + svn = error:

nevermind all - i rebuilt the server with only minimal packages and re-ran the svn install of Fog and it worked fine - go figure.

Glad to hear you got it working

@Tom-Elliott This, this is why we love you.

Did you try again?

I had a minor issue with this as well, creating a new image and uploading solved the issue in the one particular instance that I was seeing this error.

It appeared to be an issue with transferring the image from the /images/dev/(macaddress) to /images/(nameofimage) folder.

Can you try once more and report back? Hopefully we don’t have to do this for EVERY image (upload twice).

@RobTitian16 Thank you for your reply.

Did you build your Windows 10 image from scratch or are you using a modified version of the pre-installed os?

You could try wiping the drive of all partitions, adding a blank one and imaging again. We have had trouble with partitions on the disk that were put there as a factory recovery point. (I know Dell, HP, etc are known for having a recovery partition).

Is this by chance a new drive? Or did it have data on it prior to imaging?

I’ve been away a minute, so please excuse this message if this is no longer an issue.

In the past we have had issues pushing an image to a “blank” hard drive. We would resolve this issue by writing a partition to the volume then imaging.