I’m having the same problem. I think the issue is with permissions.

The image deploys correctly to /images/dev/PCMAC, but when it finishes, it’s unable to create the folder in /images (FOG create a file instead with fogproject:fogproject owner) and therefore can’t move the files. While capturing the image, in my case, the owner for the /images/dev/PCMAC folder is root:root, while it for /images is fogproject:root. If you change the permissions for /images/dev/PCMAC to fogproject:root WHILE capturing the image, everything works as it should.

I tried to set my /images with root:root an 777 and added the user fogproject to sudoers too, but no luck.

Perhaps this can give the developers a clue about the problem.

Thanks.

Edit: FOG 1.5.10 here

your right they do support PXE boot i found the option right at the bottom in the bios you can choose between PXE HTTP and iSCSI
i didn’t do enough scrolling down last time i looked.

So I have deleted the entry with no data

DELETE FROM powerManagement WHERE pmMin = '' OR pmHour = '';

The problem is resolved.
I have backed up the table before 😉

This can sometimes happen after you have sysprepped an machine and missed the boot menu prompt, entering the Out-of-box-experience. Trying to shutdown the device will leave the dirty bit resulting in the unclean error.

To avoid having to sysprep again, allow the device to enter OOBE again and hit shift+F10 and enter “oobe\bypassnro” at the resulting command prompt. Once you hit enter, the system will perform a clean reboot, clearing the dirty bit and allowing Fog to capture the filesystem correctly.

Hopes this helps someone else as some Dell machines are notorious for failing to get an IP from IPV4 PXE boot.

are they all in a clean shutdown state before starting?
do they already have an OS?

Just came across the same issue, did you fix it?

Based on this guide (https://forums.fogproject.org/topic/9673/when-dhcp-pxe-booting-process-goes-bad-and-you-have-no-clue), I tried to monitor the error. One of the faulty machines stops at step seven, while the working machine continues and boots up without error.

fog_pxe_error.png

@robertkwild I’m suspecting there may have been a php module update that FTP was working similarly to a found issue in 1.6 and they finally addressed that. I apologize for not thinking of it sooner and glad it’s working. To my knowledge, we didn’t change anything regarding the Folder/File issue, so much appreciated in letting us know it’s working for you now.

@tian I’ve got exactly the same problem. The initial 10 queue items complete, but the next batch won’t start. I have to click the lightning bolt icon in the task list to force it to start. Am running up to date FOG software on a fully patched Ubuntu server.

Finally , @Tom-Elliott

Reinstallation of fog solved the problem . I think the issue was linked to the fogproject account. This issue can be closed.

@infotech_22 Generally speaking, if you do setupcomplete.com, you should completely disable the FOGService as re-enable it as the final step of the setupcomplete.com script.

The reason:

FOGService will attempt to start up and perform its actions alongside anything else that’s occurring. Generally, when the system is setup and running just fine, things are okay because there’s no interactions, but when you pair it with the OOBE configuration stuff, where it could be changing ini’s and Registry thigns, then the FOG Client is saying “Hey restart to change the name and join the domain” or “Hey restart because I completed installing this Snapin” or whatever else may be going on, it can leave your machine in an unknown and cause issues.

This isn’t something we’re able to fix in a codified manner unfortunately and we have given instructions many times to allow FOG Client while in OOBE state.

https://wiki.fogproject.org/wiki/index.php/FOG_Client#:~:text=If you plan to use,the image deployment is complete.

I don’t know if this is in the more modern Documentation, but it is in the original documentation as well.

@Mr_____T Well, I have discovered a work around. According to our consultant, the legacy wrapper message in the 1st or 2nd image was kinda the key. the X360 has no wired nic port and the usb nic adabter is recognized as a legacy booting device. But the unit only boots efi. I followed this link for starters:

Kernel runtime parameter:

Next I added the MAC addresses from each usb dongle I have available. Then, from the fog web interface:

list all hosts
Select the host
Basic Tasks tab
Deploy tab
Task (I first checked debug and followed the bread crumbs no issues)
Imaging commenced.

This is quite a bit more work than I was hoping to do just to image one machine. I was hoping someone out there could come out of the fog (pun intended) and provide some feedback.

So this is not solved. But a work around that does. If you got this far Tx

Not sure why I did not just start with trying a pre 6.xx.xx kernel…

Downloaded the the last 5.15.xx Linux kernel slapped it in /var/www/fog/service/ipxe/bzimage-5.15.98 updated the host kernel to bzimage-5.15.98 and BOOM 20GB/min.

Still willing to do some testing if there is anything you need from me to see if this can be fixed in 6.xx.xx.