I tried this and still nothing. I did find that I had an incorrect path list on the the image path under Storage management. I created a directory here: /home/fog/Images, applied the appropriate permissions and corrected the path under the storage management.
Still have the same message appearing.
Could not mount images folder (/bin/fog.upload)
@Tom-Elliott said:
Teamveiwer
That would be awesome! Thanks! I could do a teamviewer session. Are you just wanting to see the management console or are you wanting to actually get on the linux box?
@Tom-Elliott
I run that from the machine connecting to the FOG server?
I am unable to get an image to upload. I’ve tried this from two machines and I get the same results.
I’m running on CentOS 7
Version: 6132
bzImage Version: 4.4.0
bzImage32 Version: 4.4.0
All it says is:
An error has been detected!
Could not mount images folder (/bin/fog.upload)
Computer will reboot in 1 minute.
The host register just fine. I’ve attached a screenshot of the error and the task that is running
 
Upgrading to trunk actually worked. I was able to get the machine to register the host. This issue is resolved.
Thank you for both for the replies.
The machine only has one NIC.
" or you can try downloading just the new kernel/init files"
Is this just updating the kernal from within FOG? Or is this another method?
I suppose I could upgrade to trunk. I will give that a try and let you know if that resolves the issue.
Sorry for the late reply. I am booting in LEGACY mode, UEFI is not selected.
I am extremely new to the Linux realm and imaging department but I was able to get FOG installed and running.
Here is what I have running.
FOG 1.2.0 on CentOS 7
Kernal Version: 3.19.3
I was able to get an Optiplex580 to register and pull and image. It’s actually in process right now, so I’m pretty sure it’s going to work!
However, I have an Optiplex 7040 that I cannot get to register.
It says:
Cannot register host for the following reason.
Then it just lists all the system information and when it says “Attempting to send inventory” it just goes into an endless loop.
Here is the network card and partition information.
Intel
Ethernet Connection (2) I219-LM
Multiple Partition - Single Disk (Not Resizable)
The thing is, I had this same issue on CrucibleWDS. This particular model would not register but all others would just fine. I was thinking it was just a lack of functionality, but that does not seem to be the case. I don’t know if it is a network driver or a hard drive problem.
I am not sure if it matters, but this unit is using an SSD drive that is on SATA port 3. All others have been on 0. I would expect if it was a hard drive problem, I would see that once it tried to capture the image.