@george1421 , obrigado! Agora entendo como o fog funciona!

@george1421

Looked through the guide and everything matched, it was just the tftp server password that was wrong.

@george1421 I received my fixed IP from the sysadmin and I redid the installation. Everything is working perfectly now. I really thought the error was coming from mysql

I really appreciate the help you have given me. Thanks!

@george1421

From the chat session as well as the pcap here is what we found. The bootp information in the dhcp offer packet is set correctly but the dhcp options values were incorrectly set. The OP is using a route to supply the dhcp and pxe boot information for his network. The red outlined text is the problem with the dhcp offer packet.

pxe_boot.png

@Pikmin Understand it only needs to be in ahci mode for imaging, once the image is laid down just switch it back to raid-on mode before the first boot of windows. Or if you are not using any raid function, just leave it in ahci mode. There isn’t much of a performance penalty for leaving it in ahci mode.

@Sckendall With pfsense make sure both the bios and uefi fields are filled out to support dynamic booting between bios and uefi clients. Then pfsense will work fine for network booting.

@Sckendall Yes start a new topic, they are free and keep problems and solutions together with the subject of the thread.

@Sebastian-Roth , @george1421

Thanx for your help.
I set up a new virtual host with ubuntu 18.04.03 LTS server with fog and dnsmasq and everything went fine for the installation part now.
The ubuntu 18.04.03 provides apparmor by default, so I assume, that apparmor was not the reason for the install-issues I had before.
Maybe the fact, that I have had mysql installed manually, tried installation of fog and removed mysql after noticing, that fog wants to install mariadb, gave us the troubles we had.

Now another problem arose, but I opened another thread for that: https://forums.fogproject.org/topic/14197/1-5-7-does-not-capture-correctly

@Sebastian-Roth - I will try these things when I get into the office on Monday morning. I believe that I have the 1903 image that was working prior to this last batch of windows/software updates that I can get the data from.

@Fog_Newb Send me your email address in a direct message (it’s the talk bubble in the top right), and I’ll get a wiki user created for you.

@dclark I ended up just redoing my image for my Latitude 3500s with a clean install of latest W10 from USB. I gave up trying to fix the partitions/issue.

No issue with new image and deployed a bunch so far (single disk resizable)

@Robotic said in Where is the .mbr file?:

As you can see in the screenshot i added that one arg pertaining to nvme latency. That wouldnt affect the image capture process would it?

No, shouldn’t cause this issue.

What jumps at me in the file listing is this:

/images/HP-9480: total 15882304 drwxrwxrwx 2 root root 4096 Feb 6 10:11 . drwxrwxrwx 7 fogproject root 4096 Feb 6 09:36 … -rwxrwxrwx 1 root root 2 Feb 6 09:24 d1.fixed_size_partitions -rw-r–r-- 1 administrator administrator 1048576 Feb 3 08:58 d1.mbr ...

Two things:

The name in the listing is different than in the picture: HP-9480 vs. HP9480 The file is owned by a user called administrator. Seems like someone messed with this image.

No idea why d1.mbr is missing in /images/HP-9470 directory!?!

@astrugatch Ah good one. I see that @Sebastian-Roth has already updated the article. Thank you Sebastian for your speediness and pro-activeness, as always.

@ty900000 Sorry, forgot to update this topic as well. We have added a fix. Please update to the latest dev-branch and it should be all good to go again,

@lkisser Would you post more information?

@stu Any news on this? Did you get to test Linux live distros?

@Corrco Sorry this topic has been kind of lost probably when we had some issues with the forums not long ago.

The only thing I can imagine is the partition cannot be detected and captured as NTFS. In this case FOG uses RAW mode which will result in a much larger image file. This could happen if the drive is encrypted with Bitlocker or some other forms of disk encryption. Though we added a check for Bitlocker a fair while ago and it should print a message and bail out.

Please post your FOG version and let us know if you need further help.

@george1421 said in [dev-branch] multicast: for some hosts DB not updated after restore:

@shruggy How many systems do you typically image at the same time with multicast? How much memory do you have on the fog server?

Usually, it’s 36 systems at once. The setup is similar to @tec618’s: FOG on a VM with 4GB RAM, but both the VM and the hosting server run CentOS 7, and it’s Xen, not KVM. PHP 7.3 from Remi’s repo.

@Kiweegie said in Could not mount images folder (bin/fog.download) ... failed: Operation not supported:

Thoughts welcome

Do you have firewall restrictions in your MPLS or the VPN tunnel?