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

[kratkale]

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

[kratkale]

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 GB

[Tom Elliott]

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