Client Stop at: Starting haveged: OK

[george1421]

@gianni I don’t have a fog console handy, but in fog settings->fog configuration there should be a setting for log level or logging level. By default its set to 4, change it to 7 and lets see if it gives us a bit more detail. Since FOS is hanging at this point, its a bit hard to tell exactly where its going wrong. But i can tell you the iPXE stuff isn’t a problem since the kernel (bzImage) is running and started the system ints.

[gianni]

Ok, I put to level 7 and here the result when I boot the client sto here now

[george1421]

@gianni Well, that’s not much more help but I see the nvme controller is down. What version of the kernels are you using? If you don’t know from a linux console on the FOG server, navigate to /var/www/html/fog/service/ipxe and in that directory execite files bzImage that will tell you what kernel version.

Also make sure the firmware (bios) is up to date on this hardware, since it appears that linux is having an issue communicating with the hardware.

[Sebastian Roth]

@gianni What happens if you randomly hit some keys on your keyboard when you have that message on screen. I am not kidding here. The random number generator in Linux was changed some time ago and we had quite some issues to get around this. One thing that helped in most cases was adding haveged to FOS. But I am not sure this works on each and every hardware. You can add randomness to the pool by typing random keys. Give it a try to see if you have that sort of issue or it it just plain hangs.

[gianni]

@george1421 Hi George, the kernel version is: October 13, 2018
4.18.11 PC 64 Bit. I tried also the newest 4.19.48 and
4.15.2. same problem

[george1421]

@gianni Then another few questions since it appears to be hardware related, is the firmware (bios) up to date on this device?

Is the device in uefi mode? If so, do we get the same issue if bios mode is selected? I’m not suggesting that you switch to bios mode on this system at the moment, I’m only trying to see where the problem isn’t.

In this last picture FOS has proceeded past the point of haveged and actually started running the imaging scripts. What changed to get you past the haveged stop?

[gianni]

@george1421 Yeah, the BIOS is up to date and the device is in UEFI mode.

[gianni]

@george1421 said in Client Stop at: Starting haveged: OK:

In this last picture FOS has proceeded past the point of haveged and actually started running the imaging scripts. What changed to get you past the haveged stop?

I just changed the kernel to 4.18.11. with the last one stops in haveged.

[Sebastian Roth]

@gianni Please try the following. In the web UI edit this host’s settings and add nvme_core.default_ps_max_latency_us=200 as Kernel Parameter. Then try again.

[gianni]

@Sebastian-Roth Yeah, thank you this helps, now is working.

thank you again