PXE issues?
-
[QUOTE]You could always try DNSMasq to proxy serve your bootfile and server, sometimes this can alleviate issues with finding the correct files.
[URL=‘http://fogproject.org/wiki/index.php/Using_FOG_with_an_unmodifiable_DHCP_server/_Using_FOG_with_no_DHCP_server#DNSMASQ_settings_for_iPXE’]http://fogproject.org/wiki/index.ph...with_no_DHCP_server#DNSMASQ_settings_for_iPXE[/URL][/QUOTE]
This did it!!! Finally, thank you so much. :):D Now that it boots Fog every time, I can learn how to actually use it instead of installing it. Thank you so much.
-
Hi Phantox,
Can you please guide me to fix this issue. I have same issue. I have Fog 1.2.0 running in Ubuntu 12.04. I am using Windows Server for DHCP service.
Thanks in advance.
-
I really just followed this guide to setting up DNSMasq.
[URL=‘http://fogproject.org/wiki/index.php/Using_FOG_with_an_unmodifiable_DHCP_server/_Using_FOG_with_no_DHCP_server#DNSMASQ_settings_for_iPXE’][I][SIZE=12px]http://fogproject.org/wiki/index.ph...with_no_DHCP_server#DNSMASQ_settings_for_iPXE[/SIZE][/I][/URL]
I didn’t do step 7 or 8 on the guide. Instead, I jumped down to the section “DNSMASQ settings for IPXE” and continued from there.
To be able to edit and create files, I used “sudo gksu nautilus.” I used gedit (text editor) to create the ltsp.conf file and saved it to my desktop. Then using “sudo gksu nautilus” in terminal allowed me to move the ltsp.conf from my Desktop to /etc/dnsmasq.d/ltsp.conf. Make sure to edit ltsp.conf for your setup. For example:
The boot filename, Server name, Server Ip Address
dhcp-boot=undionly.kpxe,[B]x.x.x.x[/B]
Change the [B]x.x.x.x[/B] to your fog server IP address.
I also changed the IP address in this section to point to my fog server.
This range(s) is for the public interface, where dnsmasq functions
as a proxy DHCP server providing boot information but no IP leases.
Any ip in the subnet will do, so you may just put your server NIC ip here.
Since dnsmasq is not providing true DHCP services, you do not want it
handing out IP addresses. Just put your servers IP address for the interface
that is connected to the network on which the FOG clients exist.
If this setting is incorrect, the dnsmasq may not start, rendering
your proxyDHCP ineffective.
dhcp-range=[B]10.0.0.10[/B],proxy
I hope that helps you.
-
Thanks a lot for your help Phantox. I will try tomorrow and let you know.
I have bit doubt in (dhcp-range=[B]10.0.0.10[/B],proxy) part. Can I give DHCP server IP B[/B] in place of [B]10.0.0.10[/B] as our ip range is in 172.17.x.x
Once again thanks for you help.
-
I didn’t put in my DHCP server IP. I put in the actual fog server IP. I do not know if that was the correct thing to do, but everything is running now.
-
[quote=“Phantox Jada, post: 34379, member: 25158”]I didn’t put in my DHCP server IP. I put in the actual fog server IP. I do not know if that was the correct thing to do, but everything is running now.[/quote]
That is the correct thing to do, that is what the documentation tells you to do!
-
EDIT/UPDATE: This article: [url]http://fogproject.org/wiki/index.php/Chainloading_PXE_to_iPXE_using_pxelinux.0[/url]
got things working at long last, at least as far as booting into the FOG Environment, and running the diagnostics mode. I haven’t tried actually imaging or uploading from any of our PC’s yet.I WILL note that FOG now seems touchier than ever about switch equipment; on the other hand, I keep telling the PTB our switches are desperately in need of replacement, so maybe this will give them an extra kick in the butt
ORIGINAL POST:
Hi there,
I have been banging my head against this same problem. I just upgraded today from FOG 0.32 to 1.2.0 in Ubuntu 12.04
The DNSMasq trick worked like a charm…but now whenever we try to PXE boot, it craps out at this error:
/default.ipxe…Connection timed out ([url]http://ipxe.org/4c126035[/url])
We boot mostly Panasonic Toughbooks and HP Compaq Pro Elite workstations. We had NO problem in the past with PXE booting, not until this upgrade.
The chain http statement in that file is pointing to the correct IP address of the FOG server, and when we run the URL through, we get an output that appears as expected.
Any ideas?
-
Hi there,
I updated yesterday from 1.1.2 to 1.2.0, then i get the same error,
after reading the post, i installed & configure dnsmasq.then now i got this error :
PXE-T01: File not found
DASH-E3B: TFTP Error - File not found
DASH-M0F: Exiting Option ROMThe DHCP score options 66 & 67 are good (like for the 1.1.2)
i tried to restore old tftpboot directory, same error.
i check the dnsmasq, don’t see any errors.Fog is installed on a Ubuntu 14.04
ps sorry for my bad english
-
finded the solution :
ln -s undionly.kpxe undionly.0 -
I’m not sure why this fixed my problem, but it did. We were getting timeouts/hanging at kernel download…
I’d love to hear an explanation of what is looking for undionly.0…
-
Hello, I’m the rookie that struggled with TFTP login issues all day yesterday. I reinstalled FOG 1.2.0 today and it seems to have fixed that problem. Today I’ve struggled with the PXE boot. I can turn on a Dell D620, but get the T01, E3B file not found on my three victims (old Dell D620 (32bit), Thinkpad E440 (64) and a 64-bit VM). I tried adding an advanced menu option, but haven’t seen it come up. I’m not using FOG for DHCP and do get an IP address. DHCP entries for 66 and 67 have been made. The undionly.kpxe file does exist in the TFTPBOOT folder. I went with 12.04 LTS desktop version after getting befuddled with the server version which I tried after getting befuddled with the desktop version. I’ve tried using the undionly.kpxe.INTEL file as well, but went back to undionly.kpxe. FOG does turn on the D620 (the bright spot in the day), misses the PXE boot with the file not found errors, gets to the Windows login screen and then shuts down to try it all over again. This is what I get from the boot.php file. Any advice you can give me would be most appreciated.
[COLOR=#000000]#!ipxe
cpuid --ext 29 && set arch x86_64 || set arch i386
colour --rgb 0xff6600 2
cpair --foreground 7 --background 2 2
console --picture [url]http://192.168.1.8/fog/service/ipxe/bg.png[/url] --left 100 --right 80
:MENU
menu
colour --rgb 0xff0000 0
cpair --foreground 0 3
item --gap Host is NOT registered!
item --gap – -------------------------------------
item fog.local Boot from hard disk
item fog.memtest Run Memtest86+
item fog.reginput Perform Full Host Registration and Inventory
item fog.reg Quick Registration and Inventory
item fog.sysinfo Client System Information (Compatibility)
item fog.advanced Advanced Menu
choose --default fog.local --timeout 9000 target && goto ${target}
:fog.local
sanboot --no-describe --drive 0x80 || goto MENU
:fog.memtest
kernel memdisk iso raw
initrd memtest.bin
boot || goto MENU
:fog.reginput
kernel bzImage32 root=/dev/ram0 rw ramdisk_size=127000 ip=dhcp dns=192.168.1.1 keymap= web=192.168.1.8/fog/ consoleblank=0 loglevel=4 mode=manreg
imgfetch init_32.xz
boot || goto MENU
:fog.reg
kernel bzImage32 root=/dev/ram0 rw ramdisk_size=127000 ip=dhcp dns=192.168.1.1 keymap= web=192.168.1.8/fog/ consoleblank=0 loglevel=4 mode=autoreg
imgfetch init_32.xz
boot || goto MENU
:fog.sysinfo
kernel bzImage32 root=/dev/ram0 rw ramdisk_size=127000 ip=dhcp dns=192.168.1.1 keymap= web=192.168.1.8/fog/ consoleblank=0 loglevel=4 mode=sysinfo
imgfetch init_32.xz
boot || goto MENU
:fog.advanced
login
params
param mac0 ${net0/mac}
param arch ${arch}
param username ${username}
param password ${password}
param advLog 1
isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
:bootme
chain -ar [url]http://192.168.1.8/fog/service/ipxe/boot.php##params[/url] ||
goto MENU
autoboot[/COLOR] -
[quote=“Barbara Howard, post: 39245, member: 27181”]Hello, I’m the rookie that struggled with TFTP login issues all day yesterday. I reinstalled FOG 1.2.0 today and it seems to have fixed that problem. Today I’ve struggled with the PXE boot. I can turn on a Dell D620, but get the T01, E3B file not found on my three victims (old Dell D620 (32bit), Thinkpad E440 (64) and a 64-bit VM). I tried adding an advanced menu option, but haven’t seen it come up. I’m not using FOG for DHCP and do get an IP address. DHCP entries for 66 and 67 have been made. The undionly.kpxe file does exist in the TFTPBOOT folder. I went with 12.04 LTS desktop version after getting befuddled with the server version which I tried after getting befuddled with the desktop version. I’ve tried using the undionly.kpxe.INTEL file as well, but went back to undionly.kpxe. FOG does turn on the D620 (the bright spot in the day), misses the PXE boot with the file not found errors, gets to the Windows login screen and then shuts down to try it all over again. This is what I get from the boot.php file. Any advice you can give me would be most appreciated.
[COLOR=#000000]#!ipxe[/COLOR]
[COLOR=#000000]cpuid --ext 29 && set arch x86_64 || set arch i386[/COLOR]
[COLOR=#000000]colour --rgb 0xff6600 2[/COLOR]
[COLOR=#000000]cpair --foreground 7 --background 2 2[/COLOR]
[COLOR=#000000]console --picture [url]http://192.168.1.8/fog/service/ipxe/bg.png[/url] --left 100 --right 80[/COLOR]
[COLOR=#000000]:MENU[/COLOR]
[COLOR=#000000]menu[/COLOR]
[COLOR=#000000]colour --rgb 0xff0000 0[/COLOR]
[COLOR=#000000]cpair --foreground 0 3[/COLOR]
[COLOR=#000000]item --gap Host is NOT registered![/COLOR]
[COLOR=#000000]item --gap – -------------------------------------[/COLOR]
[COLOR=#000000]item fog.local Boot from hard disk[/COLOR]
[COLOR=#000000]item fog.memtest Run Memtest86+[/COLOR]
[COLOR=#000000]item fog.reginput Perform Full Host Registration and Inventory[/COLOR]
[COLOR=#000000]item fog.reg Quick Registration and Inventory[/COLOR]
[COLOR=#000000]item fog.sysinfo Client System Information (Compatibility)[/COLOR]
[COLOR=#000000]item fog.advanced Advanced Menu[/COLOR]
[COLOR=#000000]choose --default fog.local --timeout 9000 target && goto ${target}[/COLOR]
[COLOR=#000000]:fog.local[/COLOR]
[COLOR=#000000]sanboot --no-describe --drive 0x80 || goto MENU[/COLOR]
[COLOR=#000000]:fog.memtest[/COLOR]
[COLOR=#000000]kernel memdisk iso raw[/COLOR]
[COLOR=#000000]initrd memtest.bin[/COLOR]
[COLOR=#000000]boot || goto MENU[/COLOR]
[COLOR=#000000]:fog.reginput[/COLOR]
[COLOR=#000000]kernel bzImage32 root=/dev/ram0 rw ramdisk_size=127000 ip=dhcp dns=192.168.1.1 keymap= web=192.168.1.8/fog/ consoleblank=0 loglevel=4 mode=manreg[/COLOR]
[COLOR=#000000]imgfetch init_32.xz[/COLOR]
[COLOR=#000000]boot || goto MENU[/COLOR]
[COLOR=#000000]:fog.reg[/COLOR]
[COLOR=#000000]kernel bzImage32 root=/dev/ram0 rw ramdisk_size=127000 ip=dhcp dns=192.168.1.1 keymap= web=192.168.1.8/fog/ consoleblank=0 loglevel=4 mode=autoreg[/COLOR]
[COLOR=#000000]imgfetch init_32.xz[/COLOR]
[COLOR=#000000]boot || goto MENU[/COLOR]
[COLOR=#000000]:fog.sysinfo[/COLOR]
[COLOR=#000000]kernel bzImage32 root=/dev/ram0 rw ramdisk_size=127000 ip=dhcp dns=192.168.1.1 keymap= web=192.168.1.8/fog/ consoleblank=0 loglevel=4 mode=sysinfo[/COLOR]
[COLOR=#000000]imgfetch init_32.xz[/COLOR]
[COLOR=#000000]boot || goto MENU[/COLOR]
[COLOR=#000000]:fog.advanced[/COLOR]
[COLOR=#000000]login[/COLOR]
[COLOR=#000000]params[/COLOR]
[COLOR=#000000]param mac0 ${net0/mac}[/COLOR]
[COLOR=#000000]param arch ${arch}[/COLOR]
[COLOR=#000000]param username ${username}[/COLOR]
[COLOR=#000000]param password ${password}[/COLOR]
[COLOR=#000000]param advLog 1[/COLOR]
[COLOR=#000000]isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme[/COLOR]
[COLOR=#000000]isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme[/COLOR]
[COLOR=#000000]:bootme[/COLOR]
[COLOR=#000000]chain -ar [url]http://192.168.1.8/fog/service/ipxe/boot.php##params[/url] ||[/COLOR]
[COLOR=#000000]goto MENU[/COLOR]
[COLOR=#000000]autoboot[/COLOR][/quote]Is your firewall disabled on the server?
Can you follow the tftp troubleshooting guide on the wiki?
[url]http://fogproject.org/wiki/index.php/Tftp_timeout[/url]From what I can tell, your particular issue is that it’s not even getting to the undionly.kpxe file. NO amount of work or changes or additions to the advanced menu, or any menu for that matter, will help you see a menu if you’re not getting the file that’s needed.
-
[INDENT]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]
-
This post is deleted! -
[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?
-
Tried to install dnsmasq and it threw an error about dnsmasq-base being an unmet dependency. This sure is making me nervous though I do appreciate the advice.
-
which version of 12.04 did you install, 12.04.1LTS? 12.04.4 LTS? 12.04.5LTS?
-
It just says 12.04 LTS. I have not done the 81 updates that are available. I did try to do this: chmod -R 777 /tftpboot and got ‘operation not permitted’. This folder is owned by mystery user #1002 which does not show up in my user list. I have not been able to get dnsmasq set up because each roadblock requires study on my part.
-
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.
-
It still surprises me that my user account is an Administrator, but I’m still not Queen of the Ubuntu castle. Mercy, I’ve made no progress today … my new boss must be totally impressed with the new Tech Lady.
