SOLVED
I was on 18.04 and ran “sudo do-release-upgrade -d”, It finished, I rebooted and was able to access the FOG web interface and deploy an image. I am running the latest stable version: 1.5.8
UPDATE: I had some issues when I upgraded to 20.04 on a different FOG box. It has been resolved.
Thanks
@sebastian-roth The error during the FOG install on 21.10 is related to installing php 8.0 mysql
If I try to manually install php8.0-mysql it appears to be installed already
The GUI works fine and capturing an image goes smoothly until the end where the database needs to be updated
Wow, so I ran the FOG installer again, this time there wasn’t an error when it came to the mysql install.
Going to try capturing an image now.
Hmm. It still fails to update the database.
Yes.
I just want to add real quick, the DC 7800’s can boot to the menu with any kernel and without and kernel parameters. They fail when deploying.
I installed the leaked dev version 21996/21996.1 on bare metal and in a VM. Secure Boot didn’t have to be enabled . UEFI and TPM (which requires CSM to be disabled) had to be. Secure Boot - the option only had to be present.
After more testing. I found I could install it in a VM as Legacy. I guess MS laxed on the VM requirements?
I also found on metal, I could disable TPM and enable CSM which should make secure boot completely unavailable. Then I deploy a sysprep-ed Win 11OOBE UEFI image on it without any problems.
I will try pure legacy on metal next…
This was with that leaked dev build so who knows if it was modified or what not and how close it is to the actual dev build release or the final release.
3.13 that comes on the latest dev-branch as of today has issues with APFS on my laptop.
3.20 x64 does not
Hell yeah dude, that cleared it right up.
Not sure if this has been resolved or if this helps -
I’ve created a Win 10 UEFI VM using the 2004 ISO. VMware
Workstation 15 Pro 15.5.6 build-16341506. All the settings were default except I went up tp 8GB of RAM. I installed it, ran all the updates, activated it while waiting for updates, rebooted twice then captured the image with FOG dev-branch version: 1.5.9-RC2.11 running on Ubuntu 20.04 LTS
It deployed fine to a similar VM.
@sebastian-roth Thanks. I just updated to the latest. So far it is capturing an APFS drive on a hackintosh no problem.
So yes, this is a perfect solution since Primary host disk can now be set by size. I have one image for the OS disk, and one for the “D” drive. I just switch the Primary Host disk setting depending on which image I want to capture or deploy.
@george1421 I boot from a FOS usb stick that pxe boots to the FOG server. So I am thinking put the T2 Kernel on the server and specify that kernel under the “host kernel” setting for the macs, then on the the FOS stick put the t2 kernel as well?
Hi all,
Not sure if this is a bug but…
I recently upgraded my FOG server (running in a VM on Ubuntu 24.04) from 1.5.x to 1.6. The upgrade process went smoothly with no errors, but afterwards I ran into a problem: the Default Storage Node could not connect. In the Web UI, “Test Connection” kept failing with an error about username/password not matching.
Here’s what I’ve done so far to troubleshoot:
Checked the .fogsettings file – confirmed the management username (fogproject) and password were correct.
Verified FTP manually – I was able to ftp localhost as fogproject using the same password, and it worked fine.
Checked the database – logged into MariaDB and confirmed that the nfsGroupMembers table had the correct ngmUser and ngmPass matching .fogsettings.
Looked at the hostname – saw that ngmHostname for DefaultMember was set to the server’s LAN IP (10.1.1.100). I tried updating it to 127.0.0.1 instead, restarted the FOG services (FOGImageReplicator and FOGSnapinReplicator), but the connection still fails.
Restarted services and re-tested multiple times, no change.
Here’s the output of systemctl status | grep FOG showing all services running:
FOGFileDeleter.service
├─1048 php /opt/fog/service/FOGFileDeleter/FOGFileDeleter
└─1115 php /opt/fog/service/FOGFileDeleter/FOGFileDeleter
FOGImageReplicator.service
├─1054 php /opt/fog/service/FOGImageReplicator/FOGImageReplicator
└─1116 php /opt/fog/service/FOGImageReplicator/FOGImageReplicator
FOGImageSize.service
├─1059 php /opt/fog/service/FOGImageSize/FOGImageSize
└─1117 php /opt/fog/service/FOGImageSize/FOGImageSize
FOGMulticastManager.service
└─1062 php /opt/fog/service/FOGMulticastManager/FOGMulticastManager
FOGPingHosts.service
├─1071 php /opt/fog/service/FOGPingHosts/FOGPingHosts
└─1131 php /opt/fog/service/FOGPingHosts/FOGPingHosts
FOGScheduler.service
├─1074 php /opt/fog/service/FOGTaskScheduler/FOGTaskScheduler
└─1133 php /opt/fog/service/FOGTaskScheduler/FOGTaskScheduler
FOGSnapinHash.service
├─1076 php /opt/fog/service/FOGSnapinHash/FOGSnapinHash
└─1135 php /opt/fog/service/FOGSnapinHash/FOGSnapinHash
FOGSnapinReplicator.service
├─1082 php /opt/fog/service/FOGSnapinReplicator/FOGSnapinReplicator
└─1137 php /opt/fog/service/FOGSnapinReplicator/FOGSnapinReplicator
So far, I’ve confirmed:
Credentials are correct (FTP works).
Database values match .fogsettings.
Tried both LAN IP and 127.0.0.1 as hostname.
All FOG services are running.
Still unable to get the storage node to pass the connection test in the Web UI.
Has anyone else run into storage node connection issues after moving to the 1.6 branch? Did something change in how the node authenticates compared to 1.5.x?
Thanks for any advice!
Hi, turns out, I had some funk on my network. It was happening on just one machine. I wiped everything, and I mean everything, router, wifi access point, phone, NAS, tablets, PC’s macs, TV’s then rebuilt from scratch, changed all passwords, authenticator everything, new keys… ugh. Rough weekend but all better now. Happy to report the latest FOG dev version is running great, although FOGMulticastManager is leaving zombie processes. I’m about to update to working 1.6 just to check it out.
Fog 1.5.10.1716 Ubuntu Server 24.04.3 LTS
I am experiencing an issue after updating to the latest dev version (see pic). Over the last few releases, FOG has been having problems resizing NVMe drives or producing unusual errors. These errors appear during capture or after deployment, ranging from “Could not adjust bad sector list” to “1 cluster outside the volume.” Usually, a complete drive wipe and Windows reinstall resolves the issue, even though the drive and volume are clean. chkdsk /x/f/r
I previously solved the “1 cluster outside the volume” error by restoring the previous image, shrinking and expanding the Windows partition, and trying again. Unfortunately, that method does not work in this case. I am now stuck at this point:
@Tom-Elliott Hi Tom, Thanks… I updated to 1.5.10.1692 and was able to deploy a 2 day old image to the PC. I updated some things on the PC, mostly with Steam and display settings then went to capture an image from it again and ran into the same problem mention in the OP. Only this time, I was able to take a pic.
I ran chkdsk prior to capturing and it came up clean
UPDATE: So I tried everything for the ntfsresize error … turns out, I had to shrink the partition in windows a bit then expand it. After that, I could capture.
Some additional info. I believe I was able to successfully capture an image of this PC right after updating to 1.5.10.1688. on Aug 26th. I am restoring a back up FOG from that time to a new VM to see.
UPDATE: So I restored the FOG server back up from a couple of days ago to a new VM and yes, I was able to back up the PC once after updating to 1688.
I updated to 1.5.10.1688 and attempted to capture an image. Win 10 resizable whole disk. It captured the main partition then failed at some point. I couldn’t see the error on the screen. The drive is now too borked to boot into Windows. So I tried to deploy an image I took before the update to the PC but was unable to check in
An idea on how to fix?
@Tom-Elliott Fog now tells me the latest dev version and the one I have is 1.5.10.1671
Was 1.5.10.1771 all a bad dream or were we both mistakenly calling 1.5.10.1671 1.5.10.1771?
