@Sebastian-Roth
25 an 36 PC in Multicast

@Tom-Elliott
Here’s something else funny—the serial numbers aren’t unique! I have a duplicate…
Two differnt PC’s CAD009 and CAD023

@Tom-Elliott
Tom Thank you for your great support.

@Tom-Elliott
I can confirm, that it works to insert the serial number in Host Management | Host gernal | Host Primary Disk. You can take the value you get from booting with a clonzilla stick (Switch to the second console) and use lsblk -pdno SERIAL,SIZE


I did a test and used the wrong number in Host Primary Disk and start to clone:

So it seems to work.

@kratkale
as a feature request I would suggest to have the possibility to fix the host primary disk like the “protected” in Image General - just to be fail safe.

@Tom-Elliott
Of course, if I change the image, for example, I have to use groups as well. Otherwise, I’d have to change the image on every PC by hand.
In that case, I think it would be helpful if you could protect the “Host Primary Disk” entry on the host so that this information isn’t lost.

@kratkale OK—I’ll try to explain it more clearly:
FOG

FOG clones (as you can see in the image) to nvme1. No host device was specified here. So FOG correctly identified the NVMe order and didn’t clone to nvme0, but to the wrong nvme1.
I noticed that this happens with all devices where the NVMe serial number starts with a number. For those where the NVMe serial number starts with a letter, it clones correctly to nvme0. The NVMe on the data drive is a different brand and only has numbers as serial numbers.

Clonzilla

Clonzilla always gave me a choice between nvme0 and nvme1 when cloning. Here, the NVMe installed in the first slot in the PC was always nvme0, and the one installed in the second slot was always nvme1—so Clonzilla always correctly identifies which is the data drive and which is the system drive. The system drive is always installed in the first slot, and the data drive is always in the second.

@kratkale
Okay—I have another theory about the problem: after analyzing the NVMe serial numbers, I found the following number ranges: 0525476001xxx and BMEAN00061090Axxx—where x can be a hexadecimal number and varies. The PC’s with NVMe drives from the 05… range have trouble recognizing the first NVMe drive. Those with BM… did not have this problem. The serial numbers of the data disks are all 260227800xxx and are all one digit shorter than the numbers of the system disks.

When cloning with Clonzilla, I didn’t have a problem with any system (65 PCs); all hard drives were correctly recognized in the order they are installed in the PC.

Could it be that cloning with FOG always clones to the smaller serial number? … and when cloning, it also says that it’s cloning to nvme1, which is correct.

@kratkale Here’s a big problem: updating a group overrode the “Host Primary Disk” entry on all the PCs in the group—I had already entered the information for all 65 PCs. But I had backed up the host table beforehand—can I just restore it?
It would be necessary to be able to block host entries!

@kratkale

is this now correct?

@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