• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login

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

    Scheduled Pinned Locked Moved
    Hardware Compatibility
    5
    54
    6.9k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • R
      rocksteve69
      last edited by

      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.

      1 Reply Last reply Reply Quote 0
      • george1421G
        george1421 Moderator
        last edited by

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

        unable

        Well first of all you have already done most of the initial steps we would have suggested so now we are to the hard bits.

        First of all what version of FOG are you using? Version 1.5.7.2 addressed some imaging issues that were discovered after 1.5.7 was release.

        What kernel version when you say the latest, that is a relative number.

        I understand this is a HP, but on the dells we have to switch the disk controller mode from raid-on to ahci mode, is there something similar in the hp firmware?

        If you are on FOG version 1.5.7, there are some beta kernels and inits we might like to try. They have an updated version of partclone on them. These are not released for general availability just yet. It would be interesting to see if the updated beta code does anything different from the current version of FOS Linux.

        My intuition is telling me the issue is either with the network adapter or the disk controller. At this time I don’t have any basis to know which one just yet.

        Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

        1 Reply Last reply Reply Quote 0
        • R
          rocksteve69
          last edited by

          Hi George,

          Thank you for replying. Here is the answers to your questions:

          First of all what version of FOG are you using? Version 1.5.7.2 addressed some imaging issues that were discovered after 1.5.7 was release.

          Currently using FOG - 1.5.7

          What kernel version when you say the latest, that is a relative number.

          Kernel - 5.1.16

          I understand this is a HP, but on the dells we have to switch the disk controller mode from raid-on to ahci mode, is there something similar in the hp firmware?

          I have looked through the BIOS and unable to see any settings with regards to the disk controller, but I know from the specs sheet you can have raid setup. I have asked the question to HP as I have a technical support incident raised with them. I will update once I have a reply.

          Kind regards,

          Steven

          george1421G 1 Reply Last reply Reply Quote 0
          • george1421G
            george1421 Moderator @rocksteve69
            last edited by

            @rocksteve69 Well, lets start by collecting some details on this target hardware. Lets do the following.

            1. Manually register a target computer into FOG (you may have already done this because you are having issues deploying).
            2. Schedule a capture/deploy to this target system, but before you schedule the task, tick the debug checkbox.
            3. PXE boot the target computer
            4. After several screens of text that you need to clear by pressing enter, you will be dropped to the FOS Linux command prompt.
            5. Key in ip addr show and collect the IP address of the FOS LInux client
            6. Set root’s password to something simple like *hello with passwd Don’t worry this password will be reset the next time FOS boots.
            7. Now with the information you set in steps 5 and 6, use putty or a remote window shell from a second computer by connecting to ssh on the FOS LInux system using info you previously collected. This remote connection will help you copy and paste commands into the FOS Linux shell.
            8. Key in lspci -nn -k and post the results here. If you get an error drop the -k from the command. This command will print out the hardware ID and the kernel driver being used for that device.

            Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

            R 1 Reply Last reply Reply Quote 0
            • R
              rocksteve69 @george1421
              last edited by Sebastian Roth

              @george1421

              Hi sorry for the late update.

              Please see output from hardware and kernel driver command.

              [Fri Sep 20 root@fogclient ~]# lspci -nn -k
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]: Sandisk Corp Device [15b7:5003] (                                                                                                                                                             rev 01)
        Subsystem: Sandisk Corp Device [15b7:5003]
        Kernel driver in use: nvme
              Q 1 Reply Last reply Reply Quote 0
              • Q
                Quazz Moderator @rocksteve69
                last edited by

                @rocksteve69

                Can you give it a try with kernel parameter nvme_core.default_ps_max_latency_us=5500 ?

                R 1 Reply Last reply Reply Quote 1
                • george1421G
                  george1421 Moderator
                  last edited by

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

                  3b:00.0 Non-Volatile memory controller [0108]: Sandisk Corp Device [15b7:5003] ( rev 01)
                  Subsystem: Sandisk Corp Device [15b7:5003]
                  Kernel driver in use: nvme

                  I also wanted to look into this disk controller in the kernel build. This is not the typical intel nvme disk controller, its something new. I’m wondering if there is some kernel settings missing for this new hardware.

                  But I would surely try the kernel parameter that Quazz posted because that has fixed other strange nvme performance issues.

                  Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

                  1 Reply Last reply Reply Quote 0
                  • R
                    rocksteve69 @Quazz
                    last edited by

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

                    nvme_core.default_ps_max_latency_us=5500

                    Hi Quazz,

                    I have successfully been able to capture and deploy images fully without any issues setting the Host Kernel Arguments value to nvme_core.default_ps_max_latency_us=5500. Thank you greatly for this information.

                    Now is there way we can we set this argument permanently for all captures and deployments and not have to create host entries for all future image deployments?

                    Thanks all.

                    Q 1 Reply Last reply Reply Quote 0
                    • Q
                      Quazz Moderator @rocksteve69
                      last edited by

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

                      R 1 Reply Last reply Reply Quote 0
                      • R
                        rocksteve69 @Quazz
                        last edited by

                        @Quazz

                        Excellent, thank you. Will test and report back.

                        1 Reply Last reply Reply Quote 0
                        • R
                          robbit
                          last edited by

                          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

                          1 Reply Last reply Reply Quote 0
                          • ?
                            A Former User
                            last edited by

                            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?

                            george1421G 1 Reply Last reply Reply Quote 0
                            • george1421G
                              george1421 Moderator @A Former User
                              last edited by

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

                              Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

                              1 Reply Last reply Reply Quote 0
                              • R
                                rocksteve69
                                last edited by

                                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

                                george1421G 1 Reply Last reply Reply Quote 0
                                • george1421G
                                  george1421 Moderator @rocksteve69
                                  last edited by

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

                                  Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

                                  R 1 Reply Last reply Reply Quote 1
                                  • R
                                    rocksteve69 @george1421
                                    last edited by

                                    @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

                                    Q 1 Reply Last reply Reply Quote 0
                                    • Q
                                      Quazz Moderator @rocksteve69
                                      last edited by Quazz

                                      @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

                                      R 1 Reply Last reply Reply Quote 0
                                      • R
                                        rocksteve69 @Quazz
                                        last edited by

                                        @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

                                        Q 1 Reply Last reply Reply Quote 0
                                        • Q
                                          Quazz Moderator @rocksteve69
                                          last edited by

                                          @rocksteve69 Can I ask which model it is specifically?

                                          R 1 Reply Last reply Reply Quote 0
                                          • R
                                            rocksteve69 @Quazz
                                            last edited by

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

                                            george1421G 1 Reply Last reply Reply Quote 0
                                            • 1
                                            • 2
                                            • 3
                                            • 1 / 3
                                            • First post
                                              Last post

                                            178

                                            Online

                                            11.6k

                                            Users

                                            17.1k

                                            Topics

                                            154.6k

                                            Posts
                                            Copyright © 2012-2024 FOG Project