HP Compaq Elite 8300 don´t boot
-
@BASURILLABAS2 as @Sebastian-Roth asked, what do the ipxe files look like. Specifically the init and bzImage files?
ls -l /var/www/fog/service/ipxe/{init{,_32}.xz,bzImage{,32}}
-
@BASURILLABAS2 As well, can go to FOG Configuration -> FOG Settings -> FOG Boot Settings to enable FOG_KERNEL_DEBUG and crank up the FOG_KERNEL_LOGLEVEL to 7! Hope we will see more messages then!! Keeping my fingers crossed.
-
It could be as simple as the inits and kernel not being fully downloaded. That always causes bizarre errors.
Can you see if another model will still boot and image?
-
@Tom-Elliott said:
@BASURILLABAS2 as @Sebastian-Roth asked, what do the ipxe files look like. Specifically the init and bzImage files?
ls -l /var/www/fog/service/ipxe/{init{,_32}.xz,bzImage{,32}}
-rw-r–r-- 1 fog www-data 6169392 ene 21 12:38 /var/www/fog/service/ipxe/bzImage
-rw-r–r-- 1 fog www-data 6170512 ene 21 12:38 /var/www/fog/service/ipxe/bzImage32
-rw-r–r-- 1 fog www-data 9577456 ene 21 12:38 /var/www/fog/service/ipxe/init_32.xz
-rw-r–r-- 1 fog www-data 10914208 ene 21 12:38 /var/www/fog/service/ipxe/init.xz -
@BASURILLABAS2 The init’s are not the proper size.
Please rerun the installer.
-
This post is deleted! -
There you go, see the problem? bzImage32 and init.xz don’t go together! Should be bzImage+init.xz OR bzImage32+init_32.xz. Please check your FOG settings in the web GUI.
-
@Sebastian-Roth
With bzImage I have the same problem: -
@BASURILLABAS2 said:
I have update to FOG 6060, I update kernels:
And I still have error (with kernel bzImage and bzImage32):
-
@BASURILLABAS2 In your picture below, it’s still trying to use bzimage32 with init.xz. One is 32 bit, the other is 64 bit. They can’t work together. Did you re-run the installer? What version of FOG are you using? Have you specified anything in the kernel parameters for this particular host?
-
@Wayne-Workman
Is the same error with bximage and init.xz.
I have FOG 6094, I reinstaled today
I dont have parameters in the multiple host that I try to capture a image -
@BASURILLABAS2 So let’s take it one step back and hopefully we can see what’s missing for you here.
- Is this only an issue with HP Compaq Elite 8300?? Other client machines boot fine?!
- Do you see this kernel panic only on one particular machine or on several machines (all HP Compaq Elite 8300)?
- Have you tried booting any kind of live linux on this machine? Try Ubuntu DVD for example or any other you have at hand
PS: Trying to find out about the HP Elite 8300 hardware details I remembered that we used to have some of those machines at work. FOG worked great! Maybe it’s a hardware defect in this particular machine. RAM? NIC?
-
Hello @Sebastian-Roth
- Is this only an issue with HP Compaq Elite 8300?? Other client machines boot fine?! --> Now I have this machines only. PXE boot fine, the error is when I tried to capture an image
- Do you see this kernel panic only on one particular machine or on several machines (all HP Compaq Elite 8300)? --> Error is in several machines
- Have you tried booting any kind of live linux on this machine? Try Ubuntu DVD for example or any other you have at hand --> I have FOG installed in a HP 8300 and I instaled with Centos and Ubuntu and boot fine in both
PS: Trying to find out about the HP Elite 8300 hardware details I remembered that we used to have some of those machines at work. FOG worked great! Maybe it’s a hardware defect in this particular machine. RAM? NIC?
-
Can you please be a bit more specific? Do you see the same kernel panic on all your clients when trying to capture/deploy? Different machines? Which models?
-
Could this have anything to do with the boot file?
Can you try undionly.kkpxe for your DHCP option 067 ?
-
@Sebastian-Roth said:
Can you please be a bit more specific? Do you see the same kernel panic on all your clients when trying to capture/deploy? Different machines? Which models?
In all models HP Compaq Elite 8300
-
Which iPXE binary do you use at the moment? undionly.kpxe? ipxe.pxe? Am I right that those machines use legacy BIOS and don’t have UEFI yet?
As Wayne suggested you can try using a different iPXE binary, like undionly.kkpxe (note the two k’s!) or ipxe.pxe
PS: I find this really confusing. Those machines are not very new and I am pretty sure others have used FOG with those successfully.
-
@Sebastian-Roth
I found the error.
I have another FOG in production (FOG@ehu 1.33) in production in the same LAN with the same DHCP and had a conflict with the iPXE.
I modified the DHCP an now boot properly
Thanks for the replay that made me find way -
Thanks for letting us know! I am so glad that this has been fixed now.