@Tom-Elliott
fyi:
again no interaction with the web interface - today another PC lost the hostDevice.
root@fog:~/NVME_Problem/hostDevice# ./anzeigen
±---------+
| hostName |
±---------+
| PC102CAD |
±---------+
f48d8e63-b439-411c-8caa-e64d1764887a-grafik.png
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

@GregorS I have 3 Dell Models that are also doing this, but I will try the change to DHCP Boot file.

I will post back when I have an update.

Thanks!

So I am alone ?

@Chandlerbing Can you do a look for all files that contain:

grep -r 'display_errors' /etc | grep -v '#'

This should only display things where display_errors is defined directly.

I suspect there’s one that is doing this for you natively.

We can mark this closed. Turns out it was a old/bad snapin package on the old server. I set up Fog with a new DB and everything worked fine. Once I removed the snapins and exported and imported the DB again it all worked as expected.

Thanks for the help.

@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
This is resolved in latest dev-branch version: 1.5.10.1853
Thanks.

@Mr_K
Thanks for the help Tom. You got me pointed in the right direction. Everything is working now.

I did a complete Ubnutu and fog fresh install to make sure I wasn’t missing anything and noticed during the installation it was grabbing my WAN IP as the fog server IP and then somehow changing the fog server IP to my LAN IP. So when I clicked on the link from the terminal after it had finished it was 192.168.1.148 however everything was setup “certs, storage Ipxe” ect as my WAN IP 20.21.X.X.

All I had to do was just change the fog settings so the IP’s matched re ran the installer to grab the new files and everything is running perfect now.

Fresh install using ver1.5.10.1826

Works perfectly. Can register hosts as normal

Maybe a bug with 1.6.0… hopefully if anyone else experiences this issue this might help

@gabriel-pissoto

I often record this with a phone then you can pick out the error in that micro flash of text.
I think most of the time picking a different X.pxe file resolves this for me.

I have the same HP Z2 G1i – it works for me with
sanboot.PNG
“SANBOOT”
The BIOS also seems very finicky to me—I even disabled all NVMe devices and Windows and enabled only network boot—but Windows resets the setting. Setting a BIOS password didn’t change anything.

@bond007fink A new version of ntfs-3g, which is the parent package for ntfsresize, has finally been released last week. That’s after 4 years of no updates. If all goes well, I will be doing an experimental release this weekend with the newer package.

As @Tom-Elliott stated, this is not an issue with FOG itself, instead FOG relies on tools like ntfs-3g and partclone to handle all the NTFS filesystem changes. Hopefully this updated version fixes your issue.
I will update the thread once the experimental release is available.

@Tom-Elliott

This is fixed, too, and can be marked as solved. The reason was stale WOL power action. I deleted those manually from the DB, and the CPU went back to normal.

I’m not sure about the SSH and replication issues, but I deleted my physical storage node, and I’m not seeing those anymore.

@mashina
I’m still having huge problems. Updated Fog. Rebuilt the Windows 11 image. … Windows 11 changes the boot order.
The image works for a few days—then it stops working.
Multicast only works sometimes—just now the image worked with one computer, but not with three in multicast—it just stops at 94% for no reason. What surprises me the most is that with this computer, only BOOT EXIT TYPE: SANBOOT works. I don’t understand much about this, but it seems wrong to me.

@pillbox1234567 Thanks for the suggestion. I turned Viridian off on the cloned VM, and it did not make a difference.

Interesting note that you’ve seen it cause boot issues on certain Linux VMs. I have not experienced that behavior yet but will keep an eye out for it.