@Sebastian-Roth

It works now !!! Thank you very much. thanks to you, I understand “Fog Server” better than before this issue 👍

@Tom-Elliott
they all went through with partclone after the latest update.

Thanks!!

Remoted in and found that the issue was the resizing of the partitions was shrinking the first partition. The first partition is ALWAYS, for now, supposed to be a “fixed_size”.

The problem was the image was reuploaded a couple days ago when that part was, unknowingly, broken and wasn’t saving the partition numbers to the fixed size list.

Fixed by editing the d1.fixed_size_partitions file and simply adding the number 1, saving, and restarting the image process.

Upgrading to trunk actually worked. I was able to get the machine to register the host. This issue is resolved.

@Wayne-Workman

I did. Created a backup user to avoid this in the future. Thanks everyone for your help! I am up and running again.

@Ph3noM said:

No it’s ok now, i just made a mistake.
I am very happy!
Thanks all for the help!

What was the mistake?

I seem to have solved my own issue. The printers were not adding to my account but they were added to the local admin setup account. When I removed them from the admin account and did a reboot the printers were then added to my account. Thanks for the help tho.

Trying to find out what exactly goes on there in the ipxe code as well as asking google. But this UEFI iPXE stuff is such a vast and complicated world. From the errors I see (“cannot read PCI configuration: No such device” and “is not supported by driver ‘PCI’”) it sounds like the NIC is not designed according to the standard UEFI implementation. Maybe it’s just a UEFI GUID not matching or what. I don’t know for sure.

By the way, which NIC was this? Can you please let us know which NIC exactly you are trying to boot from?

The iPXE dev team is great and might be able to help you with this. Try getting in contact with them on their forum or via IRC.

@Tom-Elliott @george1421 These things are listed here, in the credentials section:
https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_FTP#Credentials_.2F_Passwords

This will not remove current hosts it adds the new hosts. If there are duplicates it will skip those hosts and keep the current one in the database.

WOOT, Sorry to have caused the problem in the first place, but I am glad it is now working properly.

@jxke I recommend assigning a 500GB hard drive. That’s more than enough for about 40 different base images.

Tom,

Yes pb mean problem 🙂 no misunderstanding for me with your answer 😛

You can solve this post, all is ok now, thanks to Sebastian who told me how update / change my boot pxe

@Tom-Elliott Thanks
Updated the file as instructed.

If anyone else is having this issue the fix was:

symbolically link /var/www/fog to /var/www/html/fog

ln -s /var/www/fog /var/www/html

Mod edited to include command.

[‎1/‎26/‎2016 2:20 PM]
Ok
getmac didn’t work
I did that already
[‎1/‎26/‎2016 2:21 PM]
and netsh interface show interface gave me null response

Is what i get from my colleague at the computer. Good to know that this can cause the issue though and that it’s not the server itself. Going to suggest a hardware upgrade and get that going. Thank you.

@ITSolutions
Installed .net4 and client installed fine.
Thanks again for your guidance

@Arrowhead-IT
I followed your advice RE: using diskpart and managed to get both my Dell 5450 latptop and HP 800-G1 desktops to boot legacy/MBR, install Windows 10 and can now successfully capture/deploy using single-disk resizable FOG image.

I’m pretty sure I had default GPT/UEFI Windows 10 multi-partition image capturing and deploying previously but maybe I imagined it?

Thanks for your help.

so I went ahead and tried sudo service tftpd-hpa restart and waited a few minutes. then tried to PXE boot and it worked. However, instead of registering the host, I inputted the MAC address thru the WEB GUI.

Well its seems were both right (sort of) I reverted the server via snapshot back to 1.2.0 and it deploys fine to the 80.3% errors then it performs the after imaging tasks, such as change host name/resize FS/clear task. So its probably been corrupt for awhile but have never noticed it, since it works fine.
It appears the trunk fog just errors out and then stops everything and reboots.

EDIT: I did try pushing a different image to the same PC and that worked fine.

Thanks for the help and sorry about wasting everyone’s time.

On an off topic, how well is the legacy client going to work with the trunk fog? Is best to just plan to upgrade the client at the same time as the server?