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

[Tom Elliott]

@kratkale You don’t need the clonezilla to see this information though admittedly it’s not exactly straight forward.

You can load FOG into debug mode and it will drop you to a shell where you can then run the lsblk command as well.

That said, if booting to clonezilla isn’t that difficult a thing, then it’s all good either way.

[kratkale]

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

[kratkale]

@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

[kratkale]

@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

[kratkale]

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

@kratkale I’m confused what you mean their serial numbers are erased?

FOG isn’t overwriting the serial numbers on these devices.

Furthermore, Serial numbers aren’t stored directly on the host, they’re stored on the inventory table.

That column (hostDevice) is about storing what device a host will be using to image against.

If somebody is updating the group, the empty hostDevice (Group device for groups) would likely be overwriting it.

I’ve pushed a code change to hopefully address this particular issue in the latest dev-branch.