Posts made by Jacob Gallant

@george1421 I ran iperf on a working device and here are the results, 0 retransmits as you mentioned. You’re also correct that that is exactly what I’m seeing on the 640 G8, starts off with reasonable performance but quickly drops down to a crawl:

https://photos.app.goo.gl/oVrtqpnhmYHh39LK9

Here are the results of the hdparm command.

https://photos.app.goo.gl/SfV9bNhBqNeAawkN6

@george1421 said in HP ProBook 640 G8 imaging extremely slowly:

@jacob-gallant said in HP ProBook 640 G8 imaging extremely slowly:

just the ProBook 640 G8

The debugging truth table points to the probook at fault root.

So what is unique about this workstation from previous models? NVMe vs SATA? Specific NVMe disk?

If you want to debug this hardware a bit more we can do that. The issue will be with either the network stack or the disk subsystem.

Here is a link to iperf3 https://drive.google.com/file/d/1fLYGI-roYGongTVRS_4zQ7dWJ7osN4AW/view?usp=sharing

Place it in /images directory

The concept of testing is coming from this post: https://forums.fogproject.org/post/98231

the setup for testing is pretty easy, just setup a debug deployment to this computer. (tick the debug checkbox before submitting the deployment task).

Now pxe boot the target computer after a few screens of text you will be dropped to the FOS linux command prompt.

At the fos linux command prompt key in fog You will need to press enter after each breakpoint in the imaging code. After you see the first partclone copy complete press the Ctrl-C to break out of the deployment script.

The iperf command will be in /images directory on the pxe booting computer. Copy it over to the /tmp directory on the target computer cp /images/iperf3 /tmp Then run the iperf command as outlined in this post. https://forums.fogproject.org/post/98230
You will need to setup the iperf3 receiver on the FOG server and then the client on the target computer. This test will see how fast the network speed is between the target computer and the FOG server.

Once the network bits have been tested then testing the hard drive is next.

This will be a bit more complicated to test, so see if the hdparm command comes back with something in FOS Linux.

Here’s the iperf3 results: https://photos.app.goo.gl/xXFPLZFHAJT7dPEo9

@jacob-gallant said in HP ProBook 640 G8 imaging extremely slowly:

@george1421 @Sebastian-Roth Currently building a completely separate new FOG environment to see if it’s any version/upgrade weirdness from our current environment that may be causing issues, I’ll let you know what I find out.

Same results @george1421 @Sebastian-Roth

@george1421 Sure, give me some time and I’ll run those tests and see what I find. Thanks again!

@george1421 @Sebastian-Roth Currently building a completely separate new FOG environment to see if it’s any version/upgrade weirdness from our current environment that may be causing issues, I’ll let you know what I find out.

@george1421 That’s correct, just the ProBook 640 G8. The firmware is up to date.

@sebastian-roth Thanks for looking into that Sebastian. I can confirm that we’re connected at gigabit, and it is already connected to an unmanaged switch at my desk.

@george1421 I do get the parameter when entering that command, and the storageip is the one I was expecting. The device is not on the same subnet as the storage node or master server, but it’s within the same building and as mentioned other devices are deploying as expected.

Just in case I switched over to the same subnet and switch as one of our storage nodes (a different subnet then the main server) and saw the same results.

@george1421 Kernel parameter didn’t make a difference unfortunately.

@george1421 Thanks george. I’d prefer not to mix kernels and inits, but I couldn’t even get the devices to register until I upgraded to the 5.6.18 kernel and I couldn’t find an init to match. It’s possible I just don’t know where to look.

I’ll give the global kernel parameter a shot.

@george1421 Thanks george, I realize the different versions aren’t a great idea but we just don’t have the cycles to get them upgraded together all the time.

I couldn’t find a “5.6.18” version of the inits, so I copied over the latest from https://fogproject.org/inits but maybe that was the incorrect way to do it…

@sebastian-roth Couldn’t upload properly so hopefully this works: https://photos.google.com/share/AF1QipMf8sITfjDD3zQBcV1mXLrayWD2E6BfHazYGu8XSGWsQidx_KZ4L8em9k-yrTGMtA?key=NTluWlR3VDlWMjhBb2NtdUc5bVk1akRtZWY3Z1Jn

And no, we don’t replicate between storage nodes.

Hi folks,

Apologies if this topic has been covered, but I couldn’t find anything when I searched. We recently got in a few HP ProBook 640 G8s. In order to even get them to register we had to upgrade to the 5.6.18 version of the kernel. Although that finally worked the actual imaging of the systems is terribly slow, around 5-6MB/min.

Imaging other devices with the same image from the same storage node we get the performance we expect (7-8GB/min).

We’ve tried multiple storage nodes with the same results, so it definitely seems to be specific to this one device. Our storage nodes are a mix of versions, but we’ve tried one running 1.5.0 and others running 1.5.9 and it made no difference.

Any help would be greatly appreciated!

Thanks.
Jacob

@Wayne-Workman Will do. It’s been going relatively smoothly so far though so hopefully I won’t have to bug anyone. Thanks again!

Hi folks, I’m not going to waste anymore of your time. I’ve decided to build a new FOG environment and import the database into it. Lots of extra work for me but probably good to go fresh, newer OSs, etc. anyway. Thanks all for your help!

@Sebastian-Roth Hi Sebastien, there were no results for that grep. apt-get -f install ran through but didn’t seem to fix anything. I can still access the FOG web interface and login.

@Sebastian-Roth Here is the results of that command: 0_1484059650717_grep2.txt

@Wayne-Workman No problems with 1.2.0, I upgraded for 2 reasons: Windows 10 support and we had a hardware model that we couldn’t register with the kernel that had been installed with that version of FOG. I tried to manually update the kernel but I was getting “Failed to initialize disk” errors with the kernel I compiled. Rather than fight with that I thought I might as well perform the upgrade of the whole system.

@Quazz Just getting an “Unknown instance” when I try to stop the service.

@Sebastian-Roth Hi Sebastien,

Here are the results of that command, hopefully this helps! 0_1484051401816_grep.txt