HP Elitebook 830 Gen 6: Issues Capturing Images and Deploying Images



  • HP Elitebook 830 Gen 6: Issues Capturing Images and Deploying Images

    Currently we us FOG to capture and deploy images of our Windows machines. With each new laptop revision we install a fresh windows 10 installation with latest approved updates and our core applications installed. We then capture an image and then use this image to build all our new laptops going forward (every month we update this image with the latest approved updates to windows and applications and then capture a new image).

    The process has been used for capturing and imaging laptops across different models and generations for example

    HP 430 G2
    HP 820 G3
    HP 250 G6
    HP 830 G5

    The only issue we have come across is with the new HP 830 G6 laptops were we are unable to capture an image and also deploy an image. The one time we were able to capture an image (never again) we were then unable to deploy it to the same generation of laptops or back to the same laptop or even capture an image again. We have also attempted to deploy an image using the image we currently use for the HP 830 G5 and this had the same results.

    The issue appears to be FOG Software reading and writing to the SSD. The laptop will pxi boot fine to the fog menu, select Deploy Image (enter creds) and then start the Partclone process and hang for 25 minutes at the starting to restore image screen doing the first partition of 100MB (EFI system). Then it will start the writing of process of the 2nd partition and then slow down even more at the The process will take ages to start and then slow down to a halt stating it is writing at speeds of 450kb/min which would mean it would take 100hr + to deploy the image which we have never complete also the software does not error due to the fact it is running but at a very slow rate. We have never left the process running longer than a full day.

    Steps Attempted:

    1. Updated the kernel on the Fog Server to the latest. No effect.
    2. Swapped SSDs from and to a G5 to a G6. No effect – SDD imaged fine within the G5.
    3. Attempted to deploy using a HP docking station. No effect.
    4. Updated the bios to the latest version of R70 Ver 01.02.01. No effect.
    5. As part of our process we disabled Secure boot. We have attempted via legacy boot as well. No effect.
    6. Performed Bios factory reset along with the security reset within the BIOS. No effect.
    7. Also disabled TPM.
    8. We have also change the capture settings using no compression and no resizing of partitions.

    There seems to be an issue with the new chip 9th Gen. I was wondering if there a function to turn on verbose logging to see what is actually happening.


  • Moderator

    @george1421 This one is auto-built by Jenkins using the github repository, the other one was the one I made for testing, but wasn’t fully complete (missing progress update patch)

    Other than that they’re identical

    @rocksteve69

    Once you have the init.xz you can rename it to init_partclone.xz or something and then copy it to /var/www/fog/service/ipxe

    Then you can change the host init in the WebGUI at host settings to init_partclone.xz or whatever you named it.


  • Moderator

    @rocksteve69 The updated version of partclone should be in the link I provided below. Partclone is in the init.xz file. You would just download the init.xz and rename it and and move it to /var/www/html/fog/service/ipxe directory. Then for that specific host go into the host definition and under the init field.

    Byt @Quazz looking at the link you provided earlier, I though you named this beta init something else than init.xz?? Is that link still correct?



  • @rocksteve69

    I have also just tried the Samsung G6 SSD in a G5 and it worked fine with no issues, imaged in record time.

    Starting to get very confused.



  • @Quazz

    I can try. How does one install the update version of partclone?



  • @george1421

    I have done just that. If I swap the drives works fine with WD. Samsung doesn’t work within either laptop. I could attempt to put one of the drives within a known working G5 as this will completely rule out anything else.


  • Moderator

    @george1421 To be honest, I never expected the partclone update to really change anything in that regard. I just figured there was a possibility that it could improve somewhat.

    I’ve been confusing this thread with another one I think. I assumed he was already on those inits.

    It’s worth a shot!

    Can be downloaded from: https://dev.fogproject.org/blue/organizations/jenkins/fos/detail/master/95/artifacts


  • Moderator

    @rocksteve69 This may be too much to ask, but if you swapped the WD drive for the Samsung drive in the same model laptop, does the problem move with the drive? That would then point directly to the Samsung drive.

    @Quazz do you think the updated version of partclone would solve this issue ?



  • @Quazz The SSD model is Samsung MZVLB256HAHQ-000H1-S425NE0M726296.


  • Moderator

    @rocksteve69 Can I ask which model it is specifically?



  • @Quazz said in HP Elitebook 830 Gen 6: Issues Capturing Images and Deploying Images:

    nvme_core.default_ps_max_latency_us=0

    Hi, I have tested with the command nvme_core.default_ps_max_latency_us=0 and it made no difference to the G6 with the Samsung SSDs

    We see about the firmware update for the SSD and report back


  • Moderator

    @rocksteve69 Try nvme_core.default_ps_max_latency_us=0

    For the purposes of FOS, we don’t require a threshold where the drive assumes a lower power state, so we may as well try and eliminate lower power states altogether.

    There may also be firmware updates for the SSDs in question



  • @george1421 Thanks for the reply.

    Basically there is no other errors and the original issue is present again, slowness like the disk is back in low power mode.

    I have done some investigations to find the difference between the two G6s and have re-imaged a working one fine and failed on the newer G6s. The difference appears to be with regards to SSDs.

    Working G6s have West Digital and non-working have Samsung.

    I can confirmed this on 10 of each and it appears the nvme_core.default_ps_max_latency_us=5500 command has no effect on the Samsung SSDs.

    Here is a putty extra of a non working G6 with a Samsung SSD.

    00:00.0 Host bridge [0600]: Intel Corporation Device [8086:3e34] (rev 0c)
    Subsystem: Hewlett-Packard Company Device [103c:854a]
    lspci: Unable to load libkmod resources: error -12
    00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:3ea0] ( rev 02)
    Subsystem: Hewlett-Packard Company Device [103c:854a]
    00:04.0 Signal processing controller [1180]: Intel Corporation Skylake Processor Thermal Subsystem [8086:1903] (rev 0c)
    Subsystem: Hewlett-Packard Company Device [103c:854a]
    00:12.0 Signal processing controller [1180]: Intel Corporation Device [8086:9df9 ] (rev 11)
    Subsystem: Hewlett-Packard Company Device [103c:854a]
    00:14.0 USB controller [0c03]: Intel Corporation Device [8086:9ded] (rev 11)
    Subsystem: Hewlett-Packard Company Device [103c:854a]
    Kernel driver in use: xhci_hcd
    00:14.2 RAM memory [0500]: Intel Corporation Device [8086:9def] (rev 11)
    Subsystem: Hewlett-Packard Company Device [103c:854a]
    00:15.0 Serial bus controller [0c80]: Intel Corporation Device [8086:9de8] (rev 11)
    Subsystem: Hewlett-Packard Company Device [103c:854a]
    00:15.1 Serial bus controller [0c80]: Intel Corporation Device [8086:9de9] (rev 11)
    Subsystem: Hewlett-Packard Company Device [103c:854a]
    00:16.0 Communication controller [0780]: Intel Corporation Device [8086:9de0] (r ev 11)
    Subsystem: Hewlett-Packard Company Device [103c:854a]
    00:1c.0 PCI bridge [0604]: Intel Corporation Device [8086:9dbc] (rev f1)
    Kernel driver in use: pcieport
    00:1c.7 PCI bridge [0604]: Intel Corporation Device [8086:9dbf] (rev f1)
    Kernel driver in use: pcieport
    00:1d.0 PCI bridge [0604]: Intel Corporation Device [8086:9db4] (rev f1)
    Kernel driver in use: pcieport
    00:1f.0 ISA bridge [0601]: Intel Corporation Device [8086:9d84] (rev 11)
    Subsystem: Hewlett-Packard Company Device [103c:854a]
    00:1f.3 Multimedia audio controller [0401]: Intel Corporation Device [8086:9dc8] (rev 11)
    Subsystem: Hewlett-Packard Company Device [103c:854a]
    00:1f.4 SMBus [0c05]: Intel Corporation Device [8086:9da3] (rev 11)
    Subsystem: Hewlett-Packard Company Device [103c:854a]
    Kernel driver in use: i801_smbus
    00:1f.5 Serial bus controller [0c80]: Intel Corporation Device [8086:9da4] (rev 11)
    Subsystem: Hewlett-Packard Company Device [103c:854a]
    00:1f.6 Ethernet controller [0200]: Intel Corporation Ethernet Connection (6) I2 19-V [8086:15be] (rev 11)
    Subsystem: Hewlett-Packard Company Device [103c:854a]
    Kernel driver in use: e1000e
    01:00.0 PCI bridge [0604]: Intel Corporation Device [8086:15e7] (rev 06)
    Kernel driver in use: pcieport
    02:00.0 PCI bridge [0604]: Intel Corporation Device [8086:15e7] (rev 06)
    Kernel driver in use: pcieport
    02:01.0 PCI bridge [0604]: Intel Corporation Device [8086:15e7] (rev 06)
    Kernel driver in use: pcieport
    02:02.0 PCI bridge [0604]: Intel Corporation Device [8086:15e7] (rev 06)
    Kernel driver in use: pcieport
    03:00.0 System peripheral [0880]: Intel Corporation Device [8086:15e8] (rev 06)
    Subsystem: Hewlett-Packard Company Device [103c:854a]
    39:00.0 USB controller [0c03]: Intel Corporation Device [8086:15e9] (rev 06)
    Subsystem: Hewlett-Packard Company Device [103c:854a]
    Kernel driver in use: xhci_hcd
    3a:00.0 Network controller [0280]: Intel Corporation Device [8086:2723] (rev 1a)
    Subsystem: Intel Corporation Device [8086:0084]
    3b:00.0 Non-Volatile memory controller [0108]: Samsung Electronics Co Ltd Device [144d:a808]
    Subsystem: Samsung Electronics Co Ltd Device [144d:a801]
    Kernel driver in use: nvme

    Steven


  • Moderator

    @rocksteve69 other than the export errors are you experiencing any issue? The export errors are understandable because of the dot in the parameter name.



  • Hi,

    Apologies for the late feedback. We have been successfully imaged 10 G6 laptops but now we new are getting the same error message as ‘Shad0wguy’.

    I have attached a screen cap.

    Error6.jpg

    Could be the bios has been updated so will check and report back.!

    Kind regards,

    Steven


  • Moderator

    @Shad0wguy Please provide a clear screen shot of the error taken with a mobile phone. The context of the error is important here.



  • I’m trying this for our G6’s. I’ve updated to 1.5.7.4 and added the nvme_core kernel argument, but when I PXE boot it shows an error about that parameter being invalid. Anyone else see this issue?



  • 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



  • @Quazz

    Excellent, thank you. Will test and report back.


  • Moderator

    @rocksteve69 You can set it for all under FOG Configuration -> FOG Settings -> General -> Kernel args


Log in to reply
 

457
Online

6.2k
Users

13.6k
Topics

128.2k
Posts