Can not deploy images after changing init/bzImage
In our school, we have two different models of computers: HP Elite 8100 and some of old Core 2 Duo HP DC 7600’s. I have imaged almost 200 Elite’s with FOG, but we needed to image a couple of the old ones, and I got the “CPU Stall” error.
I saw this (https://forums.fogproject.org/topic/12924/hp-dc7800-network-boot/7) thread (which I already followed in the past, I can’t remember since we did have to rebuild the FOG server), suggesting the change of the inits. When I changed the files, the old computers were able to image, but this error showed up in the newer ones:
What I did try:
- Update the kernel in the FOG CP
- Reinstall FOG in a different server and copy the original files to our server
Any suggestions? I’m kind of scared about rebuilding the server since I have a ton of computers already connected with the FOG Client.
@george1421 Hello, sorry for the late. This is what I get without the Kernel Argument:
And this is what I get with the Kernel Argument:
@davidgoncalves OK great. Now for testing, on the host definition for this 7600 (you may need to register it by hand for this test) Go into the host settings for this computer and in the Host Kernel Arguments field add in
acpi=offand save the setting. Now pxe boot this 7600 to see if you get beyond the cpu stall.
@george1421 Update: the 8100s are now able to deploy images. Already did a backup just to make sure. This is the error I get when I try to deploy in the 7600s:
@george1421 Perfect! I’m going to rerun now remotely and tomorrow when I’m there I’ll try again! Thank you so much for the quick help!
Will the created hosts be affected by that
No reinstalling will only fix the files related to FOG. It will not touch the database or already installed systems or captured images.
Good on the 7600s, get the 8100s working first and we can get teh 7600s working if you know what bits you need.
@george1421 Thank you! Will the created hosts be affected by that? Also, I probably changed accidently the kernel trying to fix the 8100s issue, will that be reseted with the rerun?
Yes, when I changed the inits/bzImage, the 7600s we’re able to boot, I imaged 2-3 just for testing and it worked perfectly.
if there’s any way to go back to that, I think it would fix the problem
Rerun the fog installer it will reset things back in the file system. If you made changes in the WebUI you will need to undo them by hand.
When you get back to the point where the 8100s can image then we can look at the 7600s.
Just as a question did you get the 7600s to image by messing around with the inits? (serious question, I have an idea)
@george1421 Thank you, I just messed up this lol, should’ve ask first (or just be normal and do backups).
I was able to image the 8100s with FOG 1.5.9 stock, no kernel or inits changed - if there’s any way to go back to that, I think it would fix the problem
@davidgoncalves Understand I’m still trying to understand what you have setup.
So you have the kernel for 4.19.1XX and the inits from 1.5.2?
The kernel stall issue is related to the kernel not the inits. Typically with the kernel stall you would add this to the kernel parameters
acpi=off. The top image is from the kernel booting so the inits are not even loaded yet.
Can you image the 8100s with the inits from 1.5.9?
I’m using FOG 1.5.9, Kernel 4.19.143 I think. I usually do a backup when I build a server, but I didn’t do it this time. I used these inits: https://fogproject.org/binaries1.5.2.zip
Yes, never had problems with the 8100s, and I have about 20 of those. To be honest, at this point I just would like to have the ability of image only the 8100s, I can get around with the DC7600s.
First what version of FOG (specifically) are you using and what version of the FOS Linux kernel are you using?
Can you put the system back to the way it was when FOG was installed?
What inits did you install to get the DC7600s to image?
Did the 8100s image correctly without having to modify FOG?
How many 7600s do you have / need to image?