[url]http://fogproject.org/forum/threads/quick-format-to-ntfs-with-fog-for-noobs.10349/[/url]

I would start by looking at the current format on your 60GB SSD and your 1 TB HD to verify that they are both MBR style partitions.

This includes but is not limited to:
Ubuntu 12.04.4, 12.04.5, 14.04, 14.10

If you set a static ip address by editing /etc/network/interfaces and you do not have an internet connection after rebooting, or restarting the service, you need to supply your dns server in your resolv.conf file.

To do so: (wiki article) [url]http://fogproject.org/wiki/index.php/Ubuntu_14.04#Setting_static_IP[/url]

open terminal and issue the following command:
[code]
sudo nano /etc/resolvconf/resolv.conf.d/head[/code]

Ignore the warnings about settings being over written, this is the “Head” of the resolve conf file and anything in this file will be carried down to resolv.conf when it is generated. This warning is meant to be displayed in resolv.conf warning users that changes will be over written. We are supplying the name server manually to the resolve.conf file by letting the head file carry the information for us.

Add the following line where x.x.x.x is the ip address of your DNS. If you need to supply multiple DNS entries, separate entries with a space (i.e. nameserver x.x.x.x y.y.y.y z.z.z.z)
[code]
nameserver x.x.x.x[/code]

If you use Ubnutu 12.04,.4 12.04.5, 14.04, 14.10 then conical has given us another easter egg.

Conical has decided to include dnsmasq-base in the OS and USE it with network-manager.

When you install DNSMASQ or attempt to start/restart the service you will receive the following error:
[code]dnsmasq: failed to create listening socket for port 53: Address already in use failed![/code]

I am not sure why, but I do have a fix for those of use that use DNSMASQ and need to start the service, I have made changes to the wiki to reflect what need to be completed.

[url]http://fogproject.org/wiki/index.php/Using_FOG_with_an_unmodifiable_DHCP_server/_Using_FOG_with_no_DHCP_server#Additional_Steps_for_12.04.4.2C_12.04.5.2C_14.04.2C_14.10[/url]

To solve this issue:

Open terminal and issue the following command:
[code]
sudo nano /etc/NetworkManager/NetworkManager.conf[/code]
Remove the line
[code]
dns=dnsmasq[/code]
Now we need to restart the network service
[code]
sudo service network-manager restart[/code]
This should resolve issues with getting dnsmasq to start.
Issue the following command:
[code]
sudo service dnsmasq restart[/code]

[quote=“Ray Zuchowski, post: 39830, member: 24449”]Will Fog run/install on Ubuntu Server 14.04.1 LTS ?[/quote]

What Wolfbane Said!!!

But, Yes Fog will run on Ubuntu 14.04, 14.10 and Kubuntu 14.04, 14.10

We do not recommend using the latest version, stuff tends to get changed, or broken (such as moving the Apache root dir, and TFTP) If you find issues during installation, please document them and how you solve them so we can help the community.

I set up a 14.10 Kubuntu server this morning. The only issue I ran into is the common issue with ANY Ubuntu revision as of 12.04.4 and requiring users to specify their nameserver in resolv.conf so that you have internet connectivity.

[quote=“Haz, post: 39698, member: 3272”]Well I promised an update so here it is.

Unfortunately after following your precise instructions and steps from the wiki you linked me, it is still giving me the same grief

I think it’s time to give up trying to fix this issue and just do a reinstall.

Many thanks to you both for your time and help, it is much appreciated!

Kind regards
Harrison[/quote]

If you would like help with your DNSMASQ just send me a pm we can work together to solve the issues

Personally I only every use Unicast, it’s faster, it’s more reliable, and it doesn’t bring my DHCP Server down.

Is there a particular reason you want to multicast these?

If it were my environment, I wouldn’t be multicasting on this equipment.

What version of OS?

I’m going to assume Ubuntu, this is a recent development in Ubuntu, although I don’t fully understand it yet.

You most likely need to set your nameservers in /etc/resolvconf/resolv.conf.d/head file

When the machine boots does it pull the pxe menu, or does it error out and continue booting to the OS?

In the past with certain revisions of Ubuntu, we had to doctor some services to start on each reboot. I would not be surprised to find that a service was not started properly on boot.

Start by verifying that the apache and tftp services are running.

[code]sudo service apache2 restart
sudo service tftpd-hpa restart[/code]

Try to navigate to the fog management UI, did the web page display? Pxe boot a machine, does the menu appear? can you register the machine to the fog server?

Good luck, you only need dnsmasq if you need to resolve to your file, if lets say for some reason your offered file is not received completely.

I use dnsmasq because there are IP helpers in my network that over ride my dhcp settings. I also use an out dated netware environment that has limitations on the boot file name length.

This length issue is also present in dnsmasq, that is why you have to symlink undionly.kpxe to undionly.0

Yes it is true that in the ltsp.conf file you have supplied the boot file name in its entirety, but when we began working to provide the undionly.kpxe as a boot file name, dnsmasq still had limitations. I do not know if these limitations are still present.

I hate to see you give up on trying to get dnsmasq to work, I feel it’s a wonderful solution, and with the use of dnsmasq you do not need to even edit the dhcp information to include the fog server or it’s boot file, dnsmasq works as a proxy dhcp server and issues the proper boot information to the client. If you choose to take it up again, dnsmasq that is, I would be happy to help you troubleshoot.

Did you restart dnsmasq after updating your ltsp.conf?

Try removing the server name from the ltsp.conf file and restart the service again.

There is suppose to be a line in the screenshot you provided Directly after DHCP: X.X.X.X there should be a PROXY: and its value should be the same as the FOG server IP address.

I also do not see a proper symlink to undionly.0, you will need to create a symlink to the file you are using, it appears that you are attempting to use undionly.kpx.INTEL

to use this file you need to issue the following command to your terminal\

[code]cd /tftpboot
sudo ln -s undionly.kpxe.INTEL undionly.0[/code]

[url=“/_imported_xf_attachments/1/1534_DNSMASQ.jpg?:”]DNSMASQ.jpg[/url]

That line “but was having difficulty getting the ltsp.conf file in the correct directory due to the permissions on Ubuntu” worries me.

Instead of making a file and moving it… create it and save it in the location that it belongs

[code]sudo gedit /etc/dnsmasq/ltsp.conf[/code]

Then paste in the information from the wiki, be sure to use the DNSMASQ settings for iPXE and then save the file.

This will make the file when you save and exit.

Because you use sudo, the file will be created as if it were done by the root user and issues with having to move the file should go away because the file is already in place where it needs to be. Then you need to restart the dnsmasq service and edit your /etc/exports file as the wiki commands, set up the symbolic link and all should be well.

You can do one of two things at this point. Yes, you can back up your images and install a fresh server, or you can try using DNSMASQ to get your current server working.

[url]http://fogproject.org/wiki/index.php/Using_FOG_with_an_unmodifiable_DHCP_server/_Using_FOG_with_no_DHCP_server#DNSMASQ_settings_for_iPXE[/url]

I recommend DNSMASQ, as this alleviates the need to edit the DHCP/DNS scope to include your fog server. and when removed your network will still run happily. This should take less than 5 minutes to set up and configure, if afterwards you are still unable to get to your boot file, a re-installation would not be a bad idea. I would still use 1.2.0 though.

Tom works quickly and diligently to fix issues with 1.2.0, and upgrading is a piece of cake when an update is available

I would recommend using DNSMASQ to help to resolve to your bootfile and server. You can find the installation instructions

[url]http://fogproject.org/wiki/index.php/Using_FOG_with_an_unmodifiable_DHCP_server/_Using_FOG_with_no_DHCP_server#DNSMASQ_settings_for_iPXE[/url]

[quote=“Sam Wennerlund, post: 39423, member: 20713”]

Also have tried adding the host to FOG first and it still is stuck at “iPXE initialising devices”[/quote]

Have you tried the undionly.kkpxe
Have you tried the ipxe.kpxe
Have you tried the undionly.kpx.INTEL

I would recommend giving one of these a shot.

Did you try to reboot the switches? Did you try a different port ( I pull the culprit from it’s environment and test in my office to be sure). Your fog server seems to be functioning as expected, considering most of your machines are booting correctly.

I have seen this issue in a few of my labs, usually rebooting the switches (managed or unmanaged) will solve this issue. This issue sounds network related.

Could you give us a better understanding of your network and servers?

So your FOG server is not supplying your PXE or your boot menu?

With DNSMASQ you don’t need the DHCP on the server and you don’t need to adjust scopes. You supply all the information in the ltsp.conf file.

Definitely give the DNSMASQ a shot, I have to use this because my Novell network is sorely outdated and won’t support the length of the bootfile name either

Then if you still have issues come back and I would be happy to help you update your kernel.

Use DNSMASQ to serve your bootfile and server information.

[url]http://fogproject.org/wiki/index.php/Using_FOG_with_an_unmodifiable_DHCP_server/_Using_FOG_with_no_DHCP_server#DNSMASQ_settings_for_iPXE[/url]

This should alleviate the TFTP errors you are experiencing.

Is there a specific reason you want to update the kernel? After you set up DNSMASQ if you have issues booting a device to the PXE menu, I would look into updating the kernel.

As for the kernel, have you thought about backing up your current kernel and manually downloading he new one?