@Tom-Elliott
so I cannot use fog in the development branch - I need the snap in - the old one are not working anymore - I cannot upload new one.

@Tom-Elliott
Problem with upload of a snapin.
First a working snapin stop working:
08.06.2026 15:13:27 Client-Info Client Version: 0.13.0
08.06.2026 15:13:27 Client-Info Client OS: Windows
08.06.2026 15:13:27 Client-Info Server Version: 1.5.10.1858
08.06.2026 15:13:27 Middleware::Response Success
08.06.2026 15:13:27 SnapinClient Running snapin 010_LEHRER_CAD2
08.06.2026 15:13:27 Middleware::Communication Download: http://192.168.0.196/fog/service/snapins.file.php?mac=F8:ED:FC:55:CF:93|0A:00:27:00:00:02&taskid=164
08.06.2026 15:13:31 SnapinClient C:\Program Files (x86)\FOG\tmp\010_LEHRER_CAD2_202404280859.bat
08.06.2026 15:13:31 SnapinClient ERROR: Hash does not match
08.06.2026 15:13:31 SnapinClient ERROR: --> Ideal: 190C52D094C5170B44F32883DEEE59FED0FD5016114B7A64A79EB614BFFBBB39D79B65DB9CE9DE3D0B35FE58AC23B59353D58F190B23CF1F797698055B7D5B44
08.06.2026 15:13:31 SnapinClient ERROR: --> Actual: 6B20738DF050F01FA8E2AAF43235EE959069D2E0ECEA5FE4D7141F802D4F7673E1E51A92F315AE319EC289BA3494047DD006E86371358380FED7A38A9AFB8793
08.06.2026 15:13:31 Middleware::Communication URL: http://192.168.0.196/fog/service/snapins.checkin.php?taskid=164&exitcode=-1&mac=F8:ED:FC:55:CF:93|0A:00:27:00:00:02&newService&json

try to upload a new Version in the fog gui:
named: 010_LEHRER_CAD2_202606081517.bat

@Tom-Elliott
at the moment no lost devices. I did my test at the moment. But no cloning - or other tasks - next week I’ll start to test …

@Tom-Elliott
since yesterday no devices lost

@Tom-Elliott
fyi:
again no interaction with the web interface - today another PC lost the hostDevice.
root@fog:~/NVME_Problem/hostDevice# ./anzeigen
±---------+
| hostName |
±---------+
| PC102CAD |
±---------+

Yesterday it was PC002CAD today PC102CAD.

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

dev-branch

ok
Your version of FOG is up to date.
You’re running the latest dev-branch version: 1.5.10.1858

@Tom-Elliott
Your version of FOG is up to date. You’re running the latest stable version: 1.5.10.1826

@Tom-Elliott
in the inventorry table mostly the other (for me wrong - secondarry Data) nvme is stored
Here are also some without an IHdserial
mysql -u root fog -e “SELECT iCASEserial FROM inventory WHERE iHdserial IS NULL OR iHdserial = ‘’;”
root@fog:~/NVME_Problem/inventory# ./anzeigen
±------------+
| iCASEserial |
±------------+
| CZC5477HVZ |
| CZC5477HT0 |
| CZC5477HTK |
| CZC5477JMZ |
±------------+
The Host now lost the Serial Number is the CZC5477HSX
CZC5477HSX
WDGreenSN350250GB2G0C
236050WD
260227800933
so in the inventory table the Data Disk is stored

@Tom-Elliott
I need the Serial Number of the nvme to clone to the correct device. (2 nvme in every PC)
As I had problems I now use the following command to check if all Serial Numbers are available:
mysql -u root fog -e “SELECT hostName FROM hosts WHERE hostDevice IS NULL OR hostDevice = ‘’;”
Yesterday finally (see previous post) there was no number missing - now one is missing again:
±---------+
| hostName |
±---------+
| PC002CAD |
±---------+
As I can also see it in the host general:

There was no interaction between yesterday and today on the web interface … Fog an the PC’s where on their own … Booting in the morning …
now I replace it again with:
UPDATE hosts SET hostDevice = ‘BNE7N774910207S3G’ WHERE hostID = 61;

So some update

@Tom-Elliott
Again Serial Numbers lost: checking with:

mysql -u root fog -e “SELECT hostName FROM hosts WHERE hostDevice IS NULL OR hostDevice = ‘’;”

root@fog:~/NVME_Problem# ./anzeigen
±---------+
| hostName |
±---------+
| PC116CAD |
| PC118CAD |
| PC121CAD |
| PC110CAD |
| PC112CAD |
| PC034CAD |
| PC026CAD |
| PC015CAD |
| PC016CAD |
| pc101cad |
| pc008cad |
±---------+
root@fog:~/NVME_Problem#

I’ve no idea what happend.

@Tom-Elliott
to make a backup I use now sql in bash

root@fog:~# mysql -u root -N -B -e “USE fog; SELECT CONCAT(‘UPDATE hosts SET hostDevice = ‘’’, hostDevice, ‘’’ WHERE hostID = ', hostID, ‘;’)FROM hosts;” > restore_hostdevice.sql

and restore with
root@fog:~# mysql -u root fog < restore_hostdevice.sql

@Tom-Elliott
Today again the Serial numbers of the nvme are lost in the FOG Database - I don’t know why …
Thats why I again cloned the file system to the wrong nvme

@vanfifty1
I have some simelar Problems maby read the post
https://forums.fogproject.org/topic/18157/windows-11-65x-hp-z2-tower-g1i-update/2
My problem is/was that Fog uses sometimes the wrong nvme …

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