• 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.8k
    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.
    • 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
                                • george1421G
                                  george1421 Moderator @rocksteve69
                                  last edited by

                                  @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 ?

                                  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!

                                  Q R 2 Replies Last reply Reply Quote 0
                                  • Q
                                    Quazz Moderator @george1421
                                    last edited by Quazz

                                    @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

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

                                      @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.

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

                                        @Quazz

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

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

                                          @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.

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

                                            @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?

                                            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!

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

                                            184

                                            Online

                                            11.6k

                                            Users

                                            17.1k

                                            Topics

                                            154.6k

                                            Posts
                                            Copyright © 2012-2024 FOG Project