Thank you very much. It works like a charm 🙂

Thank you all.
I will update in case resolved.
Take care!

@Wayne-Workman Yeah, that’s why I’m trying to work out my issues now - this is a fresh upgrade on a new server (installed FOG on new hardware, then moved my snapins and database over). Only place I have the new client installed is on a new image I’m working on, so this is the time to get this worked out. Next I have to try and figure out why the old FOG clients aren’t auto-upgrading like I would have thought they would.

Some how I feel a bit unsatisfied, but solving thread.

@max.maeuschen

Does your notebook currently have an operating system installed?

Did you replace the hard drive in this unit, or is the hard drive blank by chance?

@Barry-Tabrah I don’t understand the issue.

Bandwidth graph isn’t working? This should not be impacting functionality in any regard.

Just a guess, does the disk space show? What about active tasks, does it refresh every 5 seconds properly?

Can you upgrade? FOG 1.2.0 and earlier did not have any controls in place to tell the dashboard page what interface to use. However, as you stated, you pushed through to enforce the settings was for ens32, but where did you make that change?

@Tom-Elliott
I have to correct - sometimes it works and sometimes not. So it’s stilll not working. Will wait and test.

@Wayne-Workman

Also, in the file “dnsmasq.conf” at the end of the file uncomment the conf-dir.

It should look like this:

# Include another lot of configuration options. #conf-file=/etc/dnsmasq.more.conf conf-dir=/etc/dnsmasq.d

If you wanted to try the esxi route
I found this info on unRaid NFS
http://lime-technology.com/wiki/index.php/FAQ#How_do_I_configure_NFS_mounts.3F

Then in vcenter for esxi add a datastore with the network file system option
give esxi the unraid servers nfs address
tell it where to mount it on esxi
and give the datastore a name, like images

Then on your fog vm, shutdown, edit settings, and then add a new virtual disk from that data store.
Then mount that as /images in your /etc/fstab. You might have to format it before you can mount it with mkfs ext4 or something of that sort.

If that overview isn’t helpful and you want to try this method, I’ll test it out a little and document the process more thoroughly when I get a chance.

1.3.0 is really the trunk/“beta” version currently. It isn’t quite yet to release. Granted if every stable trunk was released as a final version, we would be at FOG 5782.2.0 by now.
@Tom-Elliott has been working on gpt partitions recently trying to get it perfect. Give the trunk a go

https://wiki.fogproject.org/wiki/index.php/Upgrade_to_trunk

I know what you’re saying.

This is because of the way the cycle loops. The loop is sleeping using a preset value, and never rechecks the sleep time value. I’ll work on that.

@Tom-Elliott Well I’m officially a twat. Sorry for wasting your time… I shall be booking myself into an Alzheimers clinic immediately!

@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.