FOG `Kernel panic - not syncing' error after entering quick host registration
-
@Wayne-Workman said in FOG `Kernel panic - not syncing' error after entering quick host registration:
What did you upgrade from?
I went with a clean install on this machine.
We used to run ubuntu 12.04 + fog 0.32 -
We had this issue a while a go and has been resolved for a 1000 or so revisions.
Lets find out a bit more about the target computer.
What is the make and model?
Is it configured for efi or bios mode?
iPXE is not and issue since you are getting the FOS kernel to start (kind of).Since you make references to kernels and you are running the trunk version of fog. I would just run through the ./installfog.sh script again and get the correct kernels and inits installed. Lets not make some bad decisions based on what we think is installed.
What the error is saying is that the kernel can’t find the inits (virtual hard drove) for the FOS client.
-
@george1421 said in FOG `Kernel panic - not syncing' error after entering quick host registration:
We had this issue a while a go and has been resolved for a 1000 or so revisions.
Lets find out a bit more about the target computer.
What is the make and model?
Is it configured for efi or bios mode?
iPXE is not and issue since you are getting the FOS kernel to start (kind of).Since you make references to kernels and you are running the trunk version of fog. I would just run through the ./installfog.sh script again and get the correct kernels and inits installed. Lets not make some bad decisions based on what we think is installed.
Target pc’s/laptops:
I tested with;
Gigabyte Brix 4010
Gigabyte Brix 5010
Lenovo B50-B80
(used 2 of them all, just to be sure)Bios of the clients is configured to use legacy mode.
iPXE works fine untill the execution of a task.
I installed everything as bare as possible (even tried 2 clean installs, Ubuntu+LAMP+FOG via svn checkout)What the error is saying is that the kernel can’t find the inits (virtual hard drove) for the FOS client.
This makes more sense now, thanks in advance!
-
I would start by re-running the trunk installer script. No need to use svn or git since you have a pretty new install, just run the installer again.
Then navigate to /var/www/html/fog/service/ipxe (you may need to adjust the path for Ubuntu) make sure the inits and bzImages are there. There should be two sets one for x64 and one for x86. maybe just do a
ls -laon that folder and post the results here. The installer script should verify they are the right once since the installer is checking image fingerprints now to ensure things are as they should be. -
@george1421 said in FOG `Kernel panic - not syncing' error after entering quick host registration:
I would start by re-running the trunk installer script. No need to use svn or git since you have a pretty new install, just run the installer again.
Then navigate to /var/www/html/fog/service/ipxe (you may need to adjust the path for Ubuntu) make sure the inits and bzImages are there. There should be two sets one for x64 and one for x86. maybe just do a
ls -laon that folder and post the results here. The installer script should verify they are the right once since the installer is checking image fingerprints now to ensure things are as they should be.root@NG-FOGSERVER:/var/www/html/fog/service/ipxe# ls -la total 49128 drwxr-xr-x 2 fog www-data 4096 Apr 6 15:11 . drwxr-xr-x 3 www-data www-data 4096 Apr 6 15:07 .. -rw-r--r-- 1 fog www-data 1156 Apr 6 15:07 advanced.php -rw-r--r-- 1 fog www-data 21280 Apr 6 15:07 bg.png -rw-r--r-- 1 fog www-data 695 Apr 6 15:07 boot.php -rw-r--r-- 1 fog www-data 7023312 Apr 6 15:08 bzImage -rw-r--r-- 1 fog www-data 6916224 Apr 6 15:08 bzImage32 -rw-r--r-- 1 fog www-data 234697 Apr 6 15:07 grub.exe -rw-r--r-- 1 fog www-data 16492316 Apr 6 15:08 init_32.xz -rw-r--r-- 1 fog www-data 17486980 Apr 6 15:08 init.xz -rw-r--r-- 1 fog www-data 25340 Apr 6 15:07 memdisk -rw-r--r-- 1 fog www-data 1839104 Apr 6 15:07 memtest.bin -rw-r--r-- 1 fog www-data 20933 Apr 6 15:07 refind.conf -rw-r--r-- 1 fog www-data 205192 Apr 6 15:07 refind.efi root@NG-FOGSERVER:/var/www/html/fog/service/ipxe# -
@JDoornhof Coming from FOG 0.32 I guess you were using pxelinux(.0) as a boot file. FOG 1.2.0 and FOG trunk use iPXE instead of pxelinux and we have seen the exact same issue that you have chainloading from pxelinux: https://forums.fogproject.org/topic/5642/end-kernel-panic-not-syncing
-
@Sebastian-Roth said in FOG `Kernel panic - not syncing' error after entering quick host registration:
@JDoornhof Coming from FOG 0.32 I guess you were using pxelinux(.0) as a boot file. FOG 1.2.0 and FOG trunk use iPXE instead of pxelinux and we have seen the exact same issue that you have chainloading from pxelinux: https://forums.fogproject.org/topic/5642/end-kernel-panic-not-syncing
Wow! Thank you soo much!
sudo mv /tftpboot/pxelinux.0 /tftpboot/pxelinux.0.OLD1 sudo mv /tftpboot/undionly.kpxe /tftpboot/pxelinux.0That fixed the problem for me, it actually failed to chainload.
Strangelyln -sdid not work, just renaming it did it for me. -
You could have pointed your DHCP server (option 67) to
undionly.kpxeas well instead of renaming…
Would be actually a good idea because we often ask “Which iPXE file you use?” when people have issues. If you tell us pxelinux.0 (although it’s actually undionly.kpxe) that might cause a lot of confusion…
-
@Sebastian-Roth said in FOG `Kernel panic - not syncing' error after entering quick host registration:
You could have pointed your DHCP server (option 67) to
undionly.kpxeas well instead of renaming…Would be actually a good idea because we often ask “Which iPXE file you use?” when people have issues. If you tell us pxelinux.0 (although it’s actually undionly.kpxe) that might cause a lot of confusion…
-
It is recommended that you update your dhcp server to use post undionly.kpxe instead of renaming the file in the fog server. The next time you update FOG the proper file will not be updated properly. Plus when you ask for FOG support it will confuse the person helping you because they are not suspecting this non-standard setup.
You should contact your network support team to have this value updated on the dhcp server. In the dhcp server it is option #67 also called bootfile.
-
@george1421 said in FOG `Kernel panic - not syncing' error after entering quick host registration:
Plus when you ask for FOG support it will confuse the person helping you because they are not suspecting this non-standard setup.
Going to quote you on that
