@JJ-Fullmer It looks like one of my problems was that I was runnning two network interfaces. One was going to our production network, the other to the fog network. I deleted the production interface and that eliminated the random errors I was getting. I was getting one consistent error during capture “Could not mount images folder (/bin/fog.upload) Args passed: Reason: mount: 192.168.7.184:/images/dev/ on /images failed: No such file or directory”

I had a 125 TB raid for internal storage (images) and a separate system drive for the OS and fog. So I installed the OS and fog on my raid. I can now consistently capture images with no problem. Deploying is the problem now. I’ve attached a pic. If anybody sees anything in the error please feel free to chime in.

BTW I have been using the compatibility feature to ensure the hardware passes muster.

Thanks!

@JJ-Fullmer That is helpful. I’ll run those.

@JJ-Fullmer “boot the host to the pxe menu, and use the check compatibility option”

Hey JJ. what are the steps to do this?

@JJ-Fullmer Sorry JJ. I’ve been checking for replies but today is the first I’m seeing this. It was working on an old z840 with 1 TB of storage. I’ve not moved to a Dell Server with 120 TB and I posted an image of the error I’m seeing in my latest update dated 9/16/2024.

Moved to a new Alma install. Used the git install. I could not register an Ubuntu 20.04 host. I then diid a clean install of Alma and used the latest tar for FOG. Was able to register a host but could not capture single disk resizable. Posting this pic of the error. Curious if anyone sees anything obvious. Thanks for any input.

@Tom-Elliott Hey thanks for getting back. This is the filesystem on the drive. But, oddly, with a new Alma Linux and FOG install I was able to do Single Disk - Resizable. I posted to JJ about my next steps. I’ve got to hit this with a hammer. It’s all I have .

@JJ-Fullmer My inexperience with Fog is showing. I’ve been pretty careful but obviously in this particular case not careful enough. Since I last posted I did a clean install of FOG (tar version) on a clean install of Alma Linux. It seemed to work pretty well. Moving to a big (for me) machine using Alma and a clean FOG install. I’ll take a look at the doing the Git install.

@JJ-Fullmer

Sorry getting back so late. I backed out of debian and went with a clean install of Alma Linux. Downloaded the tar file for 1.5.10.1593 and installed that. Still seeing same issue. Here’s a screen capture of the version that I’m on. And it does say that I’m not up to date. Any advice would be appreciated. Thanks for your help!

@JJ-Fullmer Not really knowing what I’m doing, I went to FOG Confguration, Kernel Update, downloaded, saved my old kernel and installed the new kernel. Doing that downgraded my kernel, oddly enough. But as instructed (thank you FOG) I saved my old kernel and was able to go back to it.

Still getting the same issue where when I create an image Single Disk - Resizable, it will not capture. However when I set the image to Multiple Partition - Single Disk (Not Resizable) it will capture. The problem then is that the image is huge (the entire disk) and it will not deploy.

I think I’m just gonna build a new server from scratch using Ubuntu Server. I’ve had odd little bugs in the past with Rocky. I doubt that that is the problem but who knows?

@JJ-Fullmer Hey, thanks for responding. I’m on FOG Version 1.5.10. I’ve attached a screen shot of the image settings. Meanwhile I’ll take a look at updating fog and the kernels.