Windows 11 | 65x HP Z2 Tower G1i | UPDATE -
-
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 directoryI’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.1826When I upload the image, I don’t get any errors
-
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
-
@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.
-
@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
-
=== 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 ===
-
Please check memory of computer with memtest86+ 8.0
-
@sgennadi
I don’t have any hardware issues anymore—now I just need to make sure the cloning process is happening on the right NVMe drive. One NVMe drive contains the students’ data, and the other contains the operating system. If I can’t get this to work, I’ll have to swap out the Fog for some Microsoft stuff -
@kratkale Like I said, if you know which nvme drive has the student data, and which is expected to be the OS:
On a registered host you can explicitly call out which drive using “serial, wwn” or otherwise.
You type in the wwn or serial number:
lsblk -pdno PATH,SERIAL,WWN,SIZE --nvmerespective of your device. (I lowercase them for simplicity.)Find your “primary” drive, and put in either one of those details in the form field and give it a shot. It should work and will leave the other drive completely alone so long as the type of image you’re using is “single disk” style.
-
is this now correct?
-
@kratkale That seems correct to me, yes. If this is a drive you’re testing proof of, I’d first just replace the actual second disk with something you don’t care to lose to test.
What I don’t want is you to just trust me at my word for the sake of things and lose actual data.
Another method you can use in case this isn’t sufficient, it’s a little more involved I suppose is to simply unplug the disk you don’t want being written, but that’s a part of the problem. At a glance you of the hardware you have no idea what drive is which. That’s the basic problem you’re running into now:
nvme0n1 this time might be the right disk, but next boot nvme0n1 might be the student disk. It’s all dependent on who starts up and responds first.
