@george1421 Hello, tsc=unstable worked! Thanks. Since some of the computers don’t belong to our campus, and just come here to be reimaged, I tried to apply that parameter in the settings in all clients and it didn’t give us compatibility issues with more modern systems (I tested for example in HP Elite 8200’s and it worked perfectly).

Thank you for your assistance!

I have multiple images on our FOG server, and all of them can be deployed with success.
However, I’m trying to create new images, and every time I capture them, a text file with the name of the supposed directory is created on /images, but the image files are not there.
There’s enough disk space and there’s no error during capture. Using Ubuntu 18.04.5.
Any idea of what could it be? Thank you!

@george1421 Hello, tsc=unstable worked! Thanks. Since some of the computers don’t belong to our campus, and just come here to be reimaged, I tried to apply that parameter in the settings in all clients and it didn’t give us compatibility issues with more modern systems (I tested for example in HP Elite 8200’s and it worked perfectly).

Thank you for your assistance!

@george1421 Hello, I’m running FOG 1.5.9 with Kernel 4.19.145. I’m going to try that and I’ll keep you update. Thank you, once again!

@george1421 Hello George! Thank you for the tip. That’s what I tried to do, but it didn’t work out, it gives me the error in the second image (kernel panic). There’s anything else I could do?

Thanks!

Hi!

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.

This is what appears on the screen:

When I use the acpi=off, I get this error:

Any suggestions? Thanks!!

@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:

@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:

Any suggestions?

@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!

@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.

@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