@Sebastian-Roth

Thank you for that. Our HP laptops were equipped with Western Digital PC SN520 NVMe SSD, but also tested with Toshiba NVMe THNSSN5256GPUK with same results. After the update, it still went to a crawl HOWEVER

When I went to change the Kernal parameter under FOG Configuration -> FOG Settings -> General -> Kernel args -> nvme_core.default_ps_max_latency_us=5500 -> it’s working now. I was able to deploy the image to a NVMe drive via unicast.

Test#1 w/ Fog Server 1.5.7.3

• Same results with the NVMe drives where the rate goes to a crawl of about 10MB/min

Test#2 w/ nvme_core.default_ps_max_latency_us=5500 + Fog 1.5.7.3

• Deploying at a solid speed ~5GB/min on isolated networrk

Whatever it is, the combination of both of those have fixed the issue.

I want to thank both you @george1421 and @Sebastian-Roth for chiming in! It’s good to know there’s a very active community for this.

@Sebastian-Roth said in Stuck at bzImage after selecting image to deploy:

Please check BIOS/UEFI firmware version. Are those exactly the same as well?

I will check once we’re back in the office. As you may have guessed, we’re all WFH now and our fog server is back in the office so might be some time before I have a chance to test again. I will try updating to latest BIOS and try again.

Do you really mean init.xz here? Above you say stuck on bzImage. Not sure if that makes a difference but I just want to make sure we talk about the same things here. So is it all stuck at the same spot that we see in the picture with bzImage ........ but not showing init.xz .....?

Wopos, I do mean init.xz. I didn’t take a screenshot of it but after booting into PXE, when I try to do the “quick register” option, then it gets stuck at init.xz

But for now, I guess we’re sort of stuck until I find a chance to visit the office to test.

Hi,

We got the new HP Elitebook 840 G6 with m2 drives, they were working just fine before. But I recently received a new batch (same exact model as others), and they get stuck at bzImage. I went ahead and updated Fog server to 1.5.8.24 but the issue still persists.

See screenshot here

What is odd, if I try to register it, it gets stuck at int.xz

There was a fix I read in previous threads where to try different bzImage/int.xz files. Was wondering if there was maybe an updated one. See screenshot of what I used in the past for laptops that caused me issues.

@DeRo93

I’m curious, what drives are inside your HP 840 G6s? We currently have the same laptop at my company, but our drives included in our G6 are Western Digital PC SN520 NVMe SSD. I know there is a configuration with OPAL drives (so they are already encrypted by default)

@Sebastian-Roth

Thank you for that. Our HP laptops were equipped with Western Digital PC SN520 NVMe SSD, but also tested with Toshiba NVMe THNSSN5256GPUK with same results. After the update, it still went to a crawl HOWEVER

When I went to change the Kernal parameter under FOG Configuration -> FOG Settings -> General -> Kernel args -> nvme_core.default_ps_max_latency_us=5500 -> it’s working now. I was able to deploy the image to a NVMe drive via unicast.

Test#1 w/ Fog Server 1.5.7.3

• Same results with the NVMe drives where the rate goes to a crawl of about 10MB/min

Test#2 w/ nvme_core.default_ps_max_latency_us=5500 + Fog 1.5.7.3

• Deploying at a solid speed ~5GB/min on isolated networrk

Whatever it is, the combination of both of those have fixed the issue.

I want to thank both you @george1421 and @Sebastian-Roth for chiming in! It’s good to know there’s a very active community for this.

@george1421
updating now, I ran ./installfog.sh and it’s taking some time to backup database. I will report back tomorrow

Thank you for all the help so far! I’ve also just found this thread just now. We pretty much have the same exact laptop
https://forums.fogproject.org/topic/13733/hp-elitebook-830-gen-6-issues-capturing-images-and-deploying-images/5

so I may try the kernal parameters as well (unless you suggest otherwise)

It seems like we may have similar issues except I can capture image fine but deploying images is extremely slow (10MB/min).
I’m updating to latest version of Fog 1.5.7.0 to 1.5.7.2 and going to try Kernal parameter as well if the update doesn’t resolve the issue
nvme_core.default_ps_max_latency_us=5500

I too am using the HP Elitebook G6, except 840 not 830

@george1421

Thanks for the screenshot. Looks like I don’t have apt-get on CentOS 7. Is there another alternative? It seems like I just need to get Git, right? Tried running yum install git but got a bunch of errors about mirror sites not available.

@george1421 said in Extremely Slow Deploy to NVME drives:

tarball

Tarbell. I went https://fogproject.org/download to download it. Installed it as Normal Server.

I forgot to mention, Fog is installed on a standard 3TB 3.5" HDD. The images are being stored under /images.

@george1421

I do, I have a 10port 1Gb managed switch (Cisco SG300-10SFP). I tried it out with the same results. It started out strong for few seconds but rate quickly drops. Elapsed time is about 5 minutes and the rate is at 90MB/min and still dropping. The progress percentage has also froze at 1.21% right now.

I’m not sure if it’s a red herring, but I suspect it’s something with the NVMe vs M.2 SSD. It deploys just fine with the M.2 SSD with the exact same laptop, switch, cables. But as soon as I put back the NVMe, this issue comes up. I got a 52port 1Gb managed switch as well if we want to get into medium size business switches as well

@george1421

Hi,

Thanks for getting back to me so quickly. Maybe it’s more like 5GB/min? I forgot the exact number but it would only take no more than 10-15 minutes to deploy (at least to my m2 ssd).

I have a small unmanaged switch, both the target device and the fog server are plugged into it and nothing else. I’ve tried the basic troubleshooting of using different cables and switches as well.