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

    Windows 11 | 65x HP Z2 Tower G1i | UPDATE -

    Scheduled Pinned Locked Moved Unsolved FOG Problems
    5 Posts 2 Posters 207 Views
    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.
    • K
      kratkale
      last edited by

      Update to the post Windows 11 | 65x HP Z2 Tower G1i:
      Now errors have appeared during cloning:
      Images that were previously working suddenly stopped working.
      pigz: skipping: <stdin>: cooupted – invalid deflate da (invalid literal/length set)
      or then:
      Partclone fail, …
      read ERROR: No such file or directory

      I’ve now tried to completely rebuild the image. This time, a Win 11 24 LTSC.
      No success with FOG—problems again. The issues occur at the end of the third partition.

      Clonzilla 3.1.2-9, on the other hand, can clone the Sysprep image from a USB drive.

      The NVMe issue isn’t resolved for me yet either—it just happens that the second drive is selected instead of the first. Which is terrible, of course, because it’s the students’ data drive… 😞

      I have no idea how to proceed from here.
      Is it the HP computer? Is it the NVMe drives? Is it the FOG server…

      The FOG server isn’t virtual; it’s a Debian machine running FOG:
      You’re running the latest stable version: 1.5.10.1826

      When I upload the image, I don’t get any errors
      WhatsApp Image 2026-04-29 at 18.42.38.jpeg WhatsApp Image 2026-04-29 at 18.43.10.jpeg WhatsApp Image 2026-04-29 at 18.43.29.jpeg WhatsApp Image 2026-04-29 at 18.44.31.jpeg WhatsApp Image 2026-04-29 at 18.45.08.jpeg WhatsApp Image 2026-04-29 at 18.45.46.jpeg

      1 Reply Last reply Reply Quote 0
      • K
        kratkale
        last edited by

        Update:

        I uploaded the golden image to the FOG server via the NFS share using Clonezilla and then downloaded it again on the client using Clonezilla. Errors occurred here as well.

        What’s interesting is, that I couldn’t detect any errors on the hard drive using SMART. Maybe Network Card, … ?

        So I installed FOG from scratch on different hardware (latest Debian, latest FOG version — typical mix of new/old hardware).

        Unfortunately, I still can’t clone reliably with FOG. The nvme0 and nvme1 drives get swapped, and I can’t figure out why. BIOS settings seem to be changed by Windows — overall it’s quite a mess.

        Cloning with Clonezilla (one device at a time) is of course much less convenient, but there I can explicitly distinguish (see the picture) between the drives: one is 1 TB, the other 256 GB. The different brand names can also be used as a criterion.

        Interestingly, with 25 computers, the order was not swapped even once. It was always exactly as installed in the device:

        nvme0 = 1 TB
        nvme1 = 256 GBWhatsApp Image 2026-05-03 at 23.53.52.jpeg

        Tom ElliottT 1 Reply Last reply Reply Quote 0
        • Tom ElliottT
          Tom Elliott @kratkale
          last edited by

          @kratkale You can do the same thing with “Hard Drive” paramater of the Host in question.

          If you know the wwn, serial, or block size of the disk you intend, it should figure out which drive you intend. Of course this is specific to the machine you’re attempting ot image, but this same functionality is possible in FOG.

          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! Get in contact with me (chat bubble in the top right corner) if you want to join in.

          Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

          Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

          K 1 Reply Last reply Reply Quote 0
          • K
            kratkale @Tom Elliott
            last edited by

            @Tom-Elliott said in Windows 11 | 65x HP Z2 Tower G1i | UPDATE -:

            @kratkale You can do the same thing with “Hard Drive” paramater of the Host in question.

            If you know the wwn, serial, or block size of the disk you intend, it should figure out which drive you intend. Of course this is specific to the machine you’re attempting ot image, but this same functionality is possible in FOG.

            Hi,

            Thank you for you answer. I did now the job with Clonzilla - it worked fine. All PC’s are running.
            One stumbling block was the FOG client. I didn’t realize I had to click the “Reset Encryption Data” button (the yellow bar at the very top of the FOG Host Management website ) - maybe this information will help someone else.
            Now that the PCs are up and running, I have the energy to focus on getting FOG to take over all the tasks again. What I’ve noticed is that in Host | Inventory, only one hard drive is listed—and that’s the nvme2.
            For configuration It would be nice if you could select the correct hard drive from a drop-down menu in Host | Host Primary Disk.

            Unfortunately, I haven’t quite figured out what to enter where: Here’s the data I could easily retrieve under Windows using a snap-in

            K 1 Reply Last reply Reply Quote 0
            • K
              kratkale @kratkale
              last edited by

              === Festplatten-Report fuer PC117CAD ===

              — Festplatte —
              Modell : PSEMN01TA87NC0
              Seriennummer : 0000_0000_0000_0000_6479_A7B4_1F00_1204.
              Groesse (GB) : 931,51
              Medientyp : Fixed hard disk media
              Interface : SCSI
              Partitions : 2
              — Partition —
              Name : Datenträgernr. 0, Partitionsnr. 0
              Typ : GPT: System
              Bootable : True
              Groesse (GB) : 0,10
              — Partition —
              Name : Datenträgernr. 0, Partitionsnr. 1
              Typ : GPT: Basic Data
              Bootable : False
              Groesse (GB) : 931,40
              — Logisches Laufwerk —
              Laufwerksbuchstabe : 😄
              Volumename :
              Dateisystem : NTFS
              Groesse (GB) : 931,40
              Frei (GB) : 844,18

              — Festplatte —
              Modell : WD Green SN350 250GB 2G0C
              Seriennummer : E823_8FA6_BF53_0001_001B_448B_4FDE_90F3.
              Groesse (GB) : 232,88
              Medientyp : Fixed hard disk media
              Interface : SCSI
              Partitions : 1
              — Partition —
              Name : Datenträgernr. 1, Partitionsnr. 0
              Typ : GPT: Basic Data
              Bootable : False
              Groesse (GB) : 232,87
              – Logisches Laufwerk –
              Laufwerksbuchstabe : 😧
              Volumename : Daten
              Dateisystem : NTFS
              Groesse (GB) : 232,87
              Frei (GB) : 232,77

              === Ende des Reports ===

              1 Reply Last reply Reply Quote 0
              • 1 / 1
              • First post
                Last post

              125

              Online

              12.6k

              Users

              17.6k

              Topics

              156.5k

              Posts
              Copyright © 2012-2026 FOG Project