[quote=“Simon33, post: 39122, member: 27154”]I’m using FOG 1.2.0 and the DHCP is supplied by the primary router.[/quote]
Does your router have somewhere to specify the options needed to PXE boot? For Windows Server I know this is DHCP option 66/67, where you tell it the IP of the FOG server and point it to the undionly.kpxe file. I’ve never done it without a DHCP server so I probably won’t be much help there. It sounds like it’s not receiving the bootfile via tftp that it needs to boot from FOG
[quote=“Simon33, post: 39120, member: 27154”]Probably a stupid question, but I’m having real difficulty figuring out what is going wrong.
I’ve tried installing fog on a Ubuntu 14.10 64 bit installation and everything seems fine. I can create the images, define the hosts, I’ve gotten the hostnames to resolve by adding them to /etc/hosts (otherwise I get “can’t resolve hostname” errors). I’ve got upload image tasks set up. The problem is that when I boot the respective clients they just sit there in the PXE screen with DHCP. <more dots added as time goes on>. There seems to be something really obvious I’m missing.
Reading that Ubuntu 14.04 isn’t recommended, I’ve tried the same thing on Ubuntu 12.04.5 32 bit and get the same outcome.
I’ve tried giving the clients static IP in the router’s DHCP table. I’ve tried taking the secondary router out of the equation (I have two routers in my house). Nothing seems to work.
One more thing. All I really want is to be able to PXE boot from ISO files I’ve downloaded from the internet rather than image a machine. Particularly because I’m trying to load an OS onto a netbook and for some reason imaging the ISO onto a USB is proving problematic (Rufus doesn’t recognise the ISO for example.) Perhaps FOG isn’t for me?[/quote]
Which version of FOG are you using and are you using FOG for DHCP, or something else?
[quote=“Pedro Valente, post: 39015, member: 25154”]In fog configuration -> kernel update.
the 64 or 32 bits is refeing to the server or to the clients.
sorry I’m a noob.
thanks[/quote]
It’s referencing the clients you’re booting from FOG, not the FOG server itself. It doesn’t depend on the version of the OS on the client either, it’s based on whether the CPU has 64 bit support or not. If not, it’ll use the 32 bit kernel - when possible it uses 64 bit
[quote=“SouperGrover, post: 38925, member: 27066”]Why do you use undionly.kpxe instead of pxelinux.0 for the bootimage? When I used the value you gave, the PXE boot could never find the file. Is this a file that got generated someplace else?
Thanks![/quote]
Starting with 0.33B(?) FOG moved to iPXE from PXE. iPXE is using undionly.kpxe whereas PXE uses pxelinux.0 from /tftpboot. Assuming you’re running 0.33B or later, your DHCP option 67 should be undionly.kpxe, not pxelinux.0 as FOG used to use - option 66 should still be the FOG server IP. Sounds like your DHCP server isn’t set to the correct bootfile (undionly.kpxe)
[quote=“shadowfax, post: 38870, member: 26386”]We’re running FOG 1.2.0 on Ubuntu 14.10 and have had no problems whatsoever. We get in shipments of 10-20 PC’s at a time. Our imaging process is to set up the BIOS on the new PC’s to allow us to PXE boot into the FOG server, Perform Full Host Registration and Inventory and power down. Then we image them using multicast. I usually wait until the Host Registration is done and turn off the PC while it’s restarting and before it runs Windows. I didn’t know if there was a simple code modification I could make to have the PC shutdown instead of restart after the Host Registration is done.[/quote]
So you’re shutting down because there’s no way to multicast directly from the Full Registration? I could see that being a helpful feature, especially when new devices are added in bulk. Tom, after it asks if you want to image now, maybe there could be a way to choose unicast or multicast? Just a thought
[quote=“Gilou, post: 38849, member: 3221”]Question would be, what is the git repository you are talking about?
And SharpDevelop, might be good if it doesn’t make it impossible for non-windows users to contribute :)[/quote]
I believe he’s referring to this one: [url]https://github.com/mastacontrola/fogproject/tree/fogservice-rewrite[/url]
I don’t know much about 0.32, but trying another kernel is simple enough.
To download the 32 bit kernel:
[CODE]
wget --no-check-certificate http://mastacontrola.com/fogboot/kernel/bzImage32
[/CODE]
then backup the original 32 bit kernel and replace it with the new kernel - I think this is the correct path for 0.32 and earlier
[CODE]
mv /tftpboot/fog/kernel/bzImage{,.ORIG}
cp bzImage32 /tftpboot/fog/kernel/bzImage
[/CODE]
Then see if you can successfully inventory and image
What version of FOG? And are you using a USB NIC or have some kind of USB device attached to the machine that’s being booted from FOG?
[quote=“Jamie Rozek, post: 38807, member: 24394”]I’m also going to throw in there (while I’m trying to configure a kernel) that the DL380 G3 is strictly an x86 unit.[/quote]
From how I understood what Tom said and looking at even the x86 kernel, the drivers you need are there, so it doesn’t sound like a kernel issue. I would think it’s related to the fact that “FOG Only checks for /dev/sd{[a-z]} and /dev/hd{[a-z]}” per Tom. That’s my take anyway, as a non-developer. I’m sure Tom will explain and correct me 
According to Tom’s 64-bit kernel config:
[CODE]
CONFIG_SCSI_HPSA=y
[/CODE]
According to some Googling, the cciss driver was deprecated and replaced with the hpsa driver, which is present in Tom’s kernel. It also appears, however that the 5i controller is compatible with the cciss driver only though, and I don’t see it in the .config. I don’t see any mention of a 5i+, only a 5i.
Source: [url]http://cciss.sourceforge.net/[/url]
Verify:
DHCP options 66 and 67 are set to correct ip and filename
filename should be undionly.kpxe
ip should be the ip of the FOG server
Make sure the firewall is disabled
[CODE]
sudo ufw disable
[/CODE]
Can you download the file from the FOG server to a client using TFTP?
I think you’re on the right track with trying a newer kernel
[url]https://mastacontrola.com/downloads.html[/url]
[quote=“dvaldez, post: 38658, member: 26961”]I got debian to boot using these options in the menu:
:debianlive2
kernel [url]http://${fog-ip}/fog/debian/7.6.0/live/vmlinuz1[/url]
initrd [url]http://${fog-ip}/fog/debian/7.6.0/live/initrd1.img[/url]
imgargs vmlinuz1 root=/dev/nfs boot=live netboot=nfs fetch=[url]http://${fog-ip}/fog/debian/7.6.0/live/filesystem.squashfs[/url]
boot
but it is now asking for some uname/password which i dont have and giving some strange firmware error once in a while…[/quote]
This is happening within Debian or FOG?
[quote=“David Herrington, post: 38651, member: 3549”]I just went from 1.2 to build 2556 and none of my images show up under image management now
If I run the 1.2 installer again, they show up like nothing has changed
Have any idea why that would be?[/quote]
Where are your images stored, /images?
I haven’t done it with Debian, but I have with Hiren’s and the principle is the same. Make sure you place the ISO in the location you reference within the Advanced Configuration box. You can also require login to access the advanced menu
From the FOG Web Interface:
‘FOG Configuration’ -> ‘PXE Settings’ or ‘iPXE Boot Menu’ -> ‘Advanced Configuration Options’
Example entry:
:MENU
menu
item --gap – ---------------- iPXE boot menu ----------------
item LIVEDEBIAN7 Boot Debian 7 Live Version
item return Return To Previous Menu
choose --default LIVEDEBIAN7 --timeout 5000 target && goto ${target}
:LIVEDEBIAN7
initrd [url]http://${fog-ip}/ISO/DEBIAN7.ISO[/url]
chain memdisk iso raw ||
goto MENU
:return
chain [url]http://${fog-ip}/${fog-webroot}/service/ipxe/boot.php?mac=${net0/mac}[/url] ||
prompt
goto MENU
autoboot
Source: [url]http://www.fogproject.org/wiki/index.php/Advanced_Boot_Menu_Configuration_options[/url]
[quote=“sudburr, post: 38643, member: 4706”]No love for 2554 either. Still failing at php5-json.[/quote]
Ditto
[quote=“Tom Elliott, post: 38637, member: 7271”]SVN 2553 maybe?[/quote]
No joy, Houston. Now it’s apache2
[url=“/_imported_xf_attachments/1/1478_apacheerr.png?:”]apacheerr.png[/url]
Well…just created a new 14.04.01 VM and downloaded rev 2551 via svn. Everything was going perfectly other than still getting dpkg-query output (not really a big deal), and now when checking package php5-json it says ‘failed’. If it’s checking to see if it’s installed, it seems to be incorrect, because dpkg seems to indicate that it is. Some type of issue with how it’s checking to verify packages are installed?
[url=“/_imported_xf_attachments/1/1477_PhpErr.png?:”]PhpErr.png[/url]
2550 worked, although I had previously installed mysql manually to troubleshoot so I uninstalled and then successfully ran the FOG installer. I’m creating a new VM just to verify the results and will update
[quote=“Tom Elliott, post: 38629, member: 7271”]Sorry to ask, but can you try reinstalling with 2548?
I don’t know where it went wrong, but hopefully I’ve fixed the issue.[/quote]
For some reason it’s just hanging at the mysql-server install now - no ‘failed’ message. Htop shows that it’s attempting to install, and just typing the same command in manually works, but it’s not working in the script. I wasn’t sure if the dpkg-query line was just meant for added verbosity or if that was unintentional. Its been sitting at the mysql-server install for 10 minutes while I had another VM I manually installed mysql-server on in that time. Same result on 14.04.01 and 13.10 - I didn’t create a new VM but didn’t think it would be necessary given that it didn’t actually install packages last time
[url=“/_imported_xf_attachments/1/1475_Processes.png?:”]Processes.png[/url][url=“/_imported_xf_attachments/1/1476_RetryAttempt.png?:”]RetryAttempt.png[/url]