[quote=“Tom Elliott, post: 39325, member: 7271”]1. ) Will take some time, as we’re still recoding the new client.

2. ) See 1

3. ) Done

4. ) GRRRRRR[/quote]

I can’t help but laugh

You can check with the manufacturer and see if they have a BIOS update you can apply. I have several machines that do this and a BIOS flash will solve it in my environment.

Something else I noticed, some older managed switches don’t like FOG, they disable ports and cause all kinds of trouble with receiving the boot files. Can you try a different switch or hub?

try [code]
sudo chmod -R 0777 /tftpboot
[/code]

Your user may not have the required privileges to chmod that folder without sudo.

I only ask so I can download a version and try to replicate your issues.

which version of 12.04 did you install, 12.04.1LTS? 12.04.4 LTS? 12.04.5LTS?

[quote=“Barbara Howard, post: 39252, member: 27181”]
[INDENT=1]The firewall is disabled and I can successfully transfer the file via TFTP on my windows machine. Rights to tftpboot folder show: Owner=1002 (a user created as part of the installation?), Group=root and Others=Access Files. Not sure how to adjust that, but I made sure the rights to the images folder look OK (owner is root). Even tried a subfolder in images with ‘create and delete’ rights for all users even though I’m not getting that far in the process. Thank you for the help, Tom![/INDENT]
[/quote]

Did you set up DNSMasq again?

[CENTER][B]As always, By using this guide you agree that you as the user have taken full responsibility for lost data, corrupted partition tables, or the like. I can not, and will not be held responsible for your actions or any damage that comes to you or your equipment by use of this guide.[/B][/CENTER]
[CENTER] [/CENTER]
[CENTER][B]You also agree not to replicate or reproduce this information without giving proper credit to the FOG project and it’s forums.[/B][/CENTER]
[CENTER] [/CENTER]
[CENTER][B]This information is subject to change without notice.[/B][/CENTER]
[CENTER] [/CENTER]
[CENTER] [/CENTER]
[CENTER][U][B]Preface[/B][/U][/CENTER]

Do you have an Advanced Format drive? Are you unable to image it with FOG? Does your installation not boot after completion of the deploy task? Does your cursor indicator blink but never boot? Then have I got a treat for you!

As always you should verify that your drive is in fact Advanced Format, if not, try my guide to format the drive using the FOG debug menu option and see if your image works. If that doesn’t work, come back and I will show you another trick!

[CENTER][U][B]Quick NTFS guide[/B][/U] -[/CENTER]
[CENTER][url]http://fogproject.org/forum/threads/quick-format-to-ntfs-with-fog-for-noobs.10349/[/url][/CENTER]

So all of the options I listed above about the blinky cursor and the failing to boot, they are not direct indicators of Advanced format, and the issue may lie with the image, but trying the steps below will not injure your image or any of your machines, so long as the drive does not have any important data on it.

[CENTER][U][B]Background[/B][/U][/CENTER]

Through some diligent troubleshoot/serious face bashing against the proverbial wall, I have managed to get an Advanced Format drive to work with older versions of FOG that may not exactly support them.

I even have trouble with the recent versions of FOG and my crappy old images being pushed to these new format drives, and I had to find a way to use them so I didn’t have to rebuild all my images (we move to active directory soon and I plan to build new images for them, but I’ll be d@mned if I’m going to build new Novell images!!! Grumble).

[CENTER][U][B]The Procedure[/B][/U][/CENTER]

The quickest, easiest way I have found to deal with Advanced Format drives is to put the hard drive in a External USB HDD caddy/case.

Now attach the usb hard drive to a currently working Windows installation (sorry I haven’t fool proofed the plan yet and I’m not sure how many passes the configuration will stay through, but I will be testing further).

You can plug the drive in to the SATA ports on the mother board too, but The USB case is quicker to access and to get the drive back. Using a USB caddy also prevents damage to internal working equipment for any reason, but to each his own.)

I right mouse click “[B]My Computer[/B]” and select [B]Manage[/B], and then under [B]Storage[/B] select the [B]Disk Manager[/B] on the left hand pane. Your ultimate goal is to get to the [B]Disk Manager[/B] so you can modify the partitions and the allocation.

Next you will find your hard drives listed in the disk manager pane on the right. In my case I have two drives, my windows drive (partitioned and working) and my new drive (which may or may not have partitions, if it does, we will Delete them and remove them all). My hard drive for windows is Disk 0, and my Advanced Format drive that I want to use with FOG is Disk 1. Select your Advanced Format drive in question, and make sure to delete any partitions, they will have a blue bar across the top. Select the partitions one at a time and Press the [B]Delete[/B] button. You may right mouse click the partition and remove it if you’d like. If the bar is black, the space is unallocated and does not need to be touched… yet.

Now that the Advanced Format drive is blank, right mouse click the unallocated space and select “[B]New Simple Volume[/B]”, this will start the wizard. The first screen is the welcome page, Click Next at the bottom right. Decide how big the partition should be, FOG will handle the reset for us so creating 1 partition is enough, I use the entire disk space. Click next. Assign a drive letter to the drive and click Next. Finally, make sure that the “format” button is selected and change the “[B]Allocation Unit Size[/B]” to 512 and click [B]Format[/B].

Depending on the size of your disk, Formatting could take some time to complete. After the disk is formatted, you may disconnect the drive from the machine and put it back into the FOG host. You may now image your Advanced Format drives through FOG

Please keep in mind my production servers are still FOG 0.32, this process may not be required in future iterations of FOG.

Thanks for letting us know what fixed it for you, we may be able to suggest this to other users now!

I doubt that the 10/100 would cause you any connectivity issues. It may slow your imaging down, but it should NOT be preventing you from receiving your files. I use some old Cisco switches that are 10/100 and they work fine with FOG. But I also use DNSMASQ in my environments.

I have similar issues though with managed switches. My Cisco switches are Catalyst 2960-S and they tend to take quite some time for my machines to boot, unless I enable port fast, then they boot within a few seconds. If I use an unmanaged switch things are usually much smoother and faster, though I am not sure why.

The only other thing that I have enabled on my switches is the IGMP Snooping.

I set my switches up with the following guide: [url]http://fogproject.org/forum/threads/cisco-programming-guide.10856/[/url]

I feel it should be stated, the experience I have with Cisco switches are all self taught/playing with settings. I am not a Cisco engineer and I never claim to be!

Hey wolfsbane, I don’t have any of those machines, but I do have some laptops I want to have added to the list

Fog 0.32 + undionly.kpxe stock bzImage

Toshiba Tecra A8-EZ8512
Toshiba Tecra RA950

[quote=“Wolfbane8653, post: 38373, member: 3362”]Can anyone else give me models that work but not on this page?
[url]http://fogproject.org/wiki/index.php/WorkingDevices[/url][/quote]

All working with FOG 0.32 + undionly.kpxe and default bzImage

Tangent Pendant 5181LPB
Tangent Pendant 5161LPB
Tangent Pendant 5141LPB
Tangent Pendant 5131LPB
Tangent Pendant 5131LP
Tangent Pendant 2465LPB

You don’t have to log in as root to install. You should at least include the sudo in front of the installation command.

Generally it is bad practice to use the root user for ANYTHING especially logging in to complete tasks, however it is acceptable to sudo su and run your commands or use sudo in front of each command you wish to elevate.

The reason you edit the lightdm.conf is so you can log in as the root user, but my recommendation is to leave lightdm.conf alone and use a regular user and call sudo when you need it.

DNSMasq takes less than 5 minutes to configure and can save you a mountain of time troubleshooting. There could be a number of reasons you are experiencing this error. Do you have access to manage/edit the DHCP scope?

DNSMasq alleviates the need to make changes to the entire scope of the DHCP, I would recommend trying DNSMasq as it has helped many others in the past. DNSMasq involves the installation from apt-get, and a single configuration file, and we already created the template for you in the wiki, you copy and paste and change the ip address information to match that of your location.

Continuing any further without permission of your Network engineer/manager is NOT recommended. You MUST edit the settings at the DHCP server in order for your server to be seen by your network properly.

Have you thought about using DNSMasq?

I use this in my locations so that I don’t have to worry about the DNS/DHCP settings being changed, or worry about messing up someone else’s settings. I actually HAVE to use this in my Novell environment to help to resolve to my bootfile and server.

You can look here and give this a shot to see if it helps to alleviate your issue.

[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 use fstab as Tom has described above to use my external hard drive to write my images to.

Could be the switch gear, I have a managed and unmanaged switch that do this from time to time. To fix the managed switch I reboot, or try a different port.

For the unmanaged switch, I find the cable that feeds my unmanaged switch and I move the cable to another port on my managed gear. This may not be the entire cause of your issue, but be aware that the switch gear could be the problem and not your FOG set up.

its not subnet, its netmask

[quote=“Mark Achel Gagalac, post: 37658, member: 26550”]thanks Jaymes! i quoted what you said in my blog at the first part. mebbe ill try to create a step by step installation in Centos 7 too.[/quote]

That would be awesome! I look forward to your guide!

We appreciate your time and effort to make this guide, but You should put in BOLD someplace that

[B]Ubuntu 14.04.1 Is not officially supported by the FOG development team[/B], we really advise users to use a pure Debian or CentOS revision.

Awesome write up, and I liked your blog, with all the images it should really help! Fog does seem to run rather beautifully on the 14.04.1 set up

Separate those VLans and everything should be golden.