Fog wont load past kernal_thread_helper+0x6/0x10
-
Are you sure you’re using the correct bzImage and init.xz pair? A 32 bit bzImage needs the 32 bit init_32.xz file. A 64 bit bzImage needs the 64 bit kernel.
As you say you’ve upgraded the fog system (I would typically recommend a fresh install) you likely need to adjust the values in FOG Configuration ( ? ) icon -> FOG Settings -> TFTP Server
Make the following changes to the relevant lines:
FOG_TFTP_PXE_KERNEL = bzImage (Exactly, NOT fog/kernel/bzImage)
FOG_TFTP_PXE_KERNEL_32 = bzImage32 (Should already be set)
If using Debian variant (e.g. Ubuntu, Debian, mint):
FOG_TFTP_PXE_KERNEL_DIR = /var/www/fog/service/ipxe/
If using Redhat Variant (e.g. Redhat, Fedora, CentOS, Scientific Linux)
FOG_TFTP_PXE_KERNEL_DIR = /var/www/html/fog/service/ipxe/
FOG_PXE_BOOT_IMAGE = init.xz (Exactly, NOT fog/images/init.gz)
FOG_PXE_BOOT_IMAGE_32 = init_32.xz -
Ok made the setting changes to the tftp but i am still running into the issue. The G1 is a gen4 i5 processor the first one where we started having issues. Should i make the change to a 64bit kernel instead of a 32? if so how do i go about making this change if necessary
-
When you changed over, are you booting to undionly.kpxe or pxelinux.0?
You need to update (from 0.32 to 0.33 upgrade) the option 67 to point to undionly.kpxe rather than pxelinux.0.
-
Ok i managed to botch something up i was attempting to make sure i had the correct kernel but doing the kernel update from the fog config. Afterwards when i try to create a image on a client i get bad kernel. So i went back to the kernel updater but i noticed that the unpublished is no longer loading on the page. I going to attempt to re-run the last good kernel and then once i’m back up check the dhcp server./
-
My server is down at the moment, due to a kernel panic on my storage server, so I expect it to be down until around 5 pm EDT.
-
ok is that why it gets stuck at moving file to tftp server
-
Ok so i downloaded the kernel earlier from the site is there anyway to copy it to the folder and replace the other kernel? i’ve tried doing it with a click and drag which give me a permission denied.
-
Open a terminal and type in sudo nautilus
That will give you a GUI with copy permissions after entering your password.
otherwise use the copy command
cd /var/www/fog/service/ipxe
mv bzImage bzImage.orig.4-15-2014cp /location/of/your/downloaded/file / /var/www/fog/service/ipxe
-
ok the one i downloaded was named tom.elliot i need to change the name to bzImage first correct?
-
Yes, it needs to be named bzImage
-
Ok used nautilus to change the downloaded tom.elliot.32 to bzImage and copied that file to var/www/fog/service/ipxe renamed the original to bzImage<date> and thats that. however when i attempt an image i am still getting bad kernel image. Do i need to reboot? sorry def noob at this
-
Do you have a specific kernel set under the FOG UI for that host??
Also a recheck of what Tom posted above:
[QUOTE]Are you sure you’re using the correct bzImage and init.xz pair? A 32 bit bzImage needs the 32 bit init_32.xz file. A 64 bit bzImage needs the 64 bit kernel.
As you say you’ve upgraded the fog system (I would typically recommend a fresh install) you likely need to adjust the values in FOG Configuration ( ? ) icon -> FOG Settings -> TFTP Server
Make the following changes to the relevant lines:
FOG_TFTP_PXE_KERNEL = bzImage (Exactly, NOT fog/kernel/bzImage)
FOG_TFTP_PXE_KERNEL_32 = bzImage32 (Should already be set)
If using Debian variant (e.g. Ubuntu, Debian, mint):
FOG_TFTP_PXE_KERNEL_DIR = /var/www/fog/service/ipxe/
If using Redhat Variant (e.g. Redhat, Fedora, CentOS, Scientific Linux)
FOG_TFTP_PXE_KERNEL_DIR = /var/www/html/fog/service/ipxe/
FOG_PXE_BOOT_IMAGE = init.xz (Exactly, NOT fog/images/init.gz)
FOG_PXE_BOOT_IMAGE_32 = init_32.xz [/QUOTE] -
I have the init_32.xzfile and i made the changes specified above. I errored by trying to update the kernel from the updater page. the part im at now is should i name the kernel bzImage or bzImage32? this is with the copy and paste method and if i’m not mistaking it has to go to the ipxe folder correct?
-
That depends on which kernel that tom.elliot is.
If it’s 32 bit then it needs to be bzImage32.
-
Just download both kernels from here, keep them named as they show and copy them to the ipxe directory.
[SIZE=13px][FONT=arial][COLOR=#262626]svn.code.sf.net/p/freeghost/code/trunk/packages/web/service/ipxe/bzImage[/COLOR][/FONT][/SIZE]
[SIZE=13px][FONT=arial][COLOR=#262626]svn.code.sf.net/p/freeghost/code/trunk/packages/web/service/ipxe/bzImage32[/COLOR][/FONT][/SIZE]
[SIZE=13px][FONT=arial][COLOR=#262626][/COLOR][/FONT][/SIZE]
-
ok so i am now able to register it and inventory… the last thing i will need assistance with is this. I set a task to upload an image but when the client pxe boots it doesn’t see it and goes to the fog load page. What am i missing?
-
Can you include a screen shot of the task you created?
Are you sure you created a task for the correct host?
Did you get any errors when creating the task?
-
Screenshot after task
[url=“/_imported_xf_attachments/0/666_Screenshot from 2014-04-15 14:57:17.png?:”]Screenshot from 2014-04-15 14:57:17.png[/url]
-
no errors popped up and yes its the only one like it listed in my inventory. I was able to get it there using the quick inventory function
-
Viper, check your DHCP server and make sure it points to undionly.kpxe not pxelinux.0.
If that does not work open a mysql terminal and type [SIZE=13px][FONT=arial][COLOR=#262626]“truncate table tasks” this will clear up any tasks from .32.[/COLOR][/FONT][/SIZE]
If none of that works [SIZE=13px][FONT=arial][COLOR=#262626]what is the output of “[/COLOR][/FONT][/SIZE][SIZE=13px][FONT=arial][COLOR=#262626][url]http://{fogserverip}/fog/service/ipxe/boot.php?mac=XX:XX:XX:XX:XX:XX[/url] spits out (where the x’s are the systems MAC ADDRESS)”[/COLOR][/FONT][/SIZE]
You can type it into any machine on the network.[SIZE=13px][FONT=arial][COLOR=#262626][/COLOR][/FONT][/SIZE]
For the record this is why we recommend a fresh install vs a update when going from .32 to .33b. If you can, back up your images and hosts and do a clean install of .33b and you will not have to hunt down all of these little changes.
