@utpalgiri143 You can tell FOG to just deploy a single partition. But FOG only knows about the partitions but not the drive letters assigned by Windows. So you need to figure out the correct partition number first.

The second thing you need to keep in mind is that the partition layout is not being deployed if you select a single partition. So a deploy task will fail if the partition layout is not correct. If you deploy the full disk once you can deploy a single partition afterwards as often as you want and as long as the partition layout is not changed.

So for deploying a single partition I suggest you create a new image definition in the FOG web UI. Set the right partition in the image configuration and capture that image. Then set this image to the host you want to deploy and let it do it’s task.

@lee-rowlett said in Secureboot issues:

LockDown.efi

a lot of thanks, that help me a lot…

@dmcadams said in Multicast session is not starting:

These client machines also have NVMe drives, so on the receiver side, instead of “/dev/sda1” should we use “/dev/nvme0”?

Yes, for the first partition use /dev/nvme0n1p1

@bacelo-0 Well there is more details we need about your isolated network.

What device is your dhcp server for this network? (the error you provided is not complete)

But guessing either the dhcp server did not send the IP address of the FOG server or there is no dhcp server on your isolated network.

@dashwell said in FOG bzImage not downloading:

use a Microtik router as our DHCP server and router and it only supports one image file call routine

Once you get past your current issue, If you need dynamic pxe booting (bios/uefi) we have a solution for that even if your dhcp server doesn’t support it. But for now one issue at a time.

@sebastian-roth Fog server is 1.5.9

I try to reproducing error and i put here picture.

@jmeyer said in Fresh install debian 11:

Yes. I’m an running Debian on a Qnap with Container Station.

Have you ever had FOG running on that before? NFS can be an issue in container virtualization. It definitely is on Proxmox when you use the default settings. I don’t know about Qnap.

@sebastian-roth OK thanks, we’re on Latest from 25.07.2021, so we’ll update and try. Thank you for your time. Fog really is amazing software and saved us big time!!

@robertkwild scrap this it works and when it runs the setup eventually its quick like a normal install

@george1421🤝 🤝 Thank you very much !

This is the great solution ever.

reg
utpal

Ha . I see that this was just recently addressed 18 days ago. Please delete. I’ll comment there.

@sebastian-roth Thank you. That fixed it.

@linshiyouxiang-net You need to extract the ZIP file before running the installer. Files bzImage, bzImage32, init.xz, init_32.xz, FOGService.exe and SmartInstaller.exe need to be in /root/fogproject/tmp.

By the way: That binary1.5.9.zip is still available on our server but the installer was changed to pull the mentioned files from github (URL for 1.5.9) some about a year ago. See the change we made in September 2020. No matter where you download the files from, they need to be in the mentioned tmp directory extracted (not as ZIP archive).

The installer will always ignore existing sha256 checksum files and re-download those but it does use bzImage/init files if they exist already and match the freshly downloaded sha256 checksums.

@robertkwild said in add boot from media in menu:

when you say chainloading to the local disk, you mean the menu option where it says boot to hard drive

Yes.

@plegrand Well done. Good to see you got it done using the instructions from the wiki.

@george1421 im following your guide here

https://forums.fogproject.org/topic/10944/using-fog-to-pxe-boot-into-your-favorite-installer-images/4

Windows 10 BIOS/UEFI 2021 edition

as i have installed a samba server on my fog server following your guide also there and also done the winpe one, how do i do step 14 as isnt that for a windows share and not a linux share

@lucycle Take a look at the first couple of lines of this script: https://github.com/FOGProject/fogproject/blob/master/utils/FOGiPXE/buildipxe.sh

@pevecg said in Fog Deploy stuck on "rebooting system as task is complete":

The interesting part is that when setting this setting, we had to once fully power cycle the PC before the setting was applied/started to work.

I’m not sure I understand. I get the idea that this setting “ahci=off reboot=warm” is causing problems after the system is imaged?? If that is what you say its not possible. These are instructions to the FOS Linux kernel. Once the kernel reboots and/or the computer is repowered there is no way those settings would still impact the computer.

@rhodesj2314

Thank you. I figured it out and added the tftp server to the dhcpd.conf file on mu Ubuntu server.

https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_NFS
Creating & verifying .mntcheck files
.mntcheck is a hidden and empty file that a FOG client uses during image capture and image download/deployment to verify an NFS share is mounted correctly.

To create these files, on the FOG server:

touch /images/.mntcheck
touch /images/dev/.mntcheck
Verify these files with:

ls -laR /images | grep .mntcheck