@vtl.victor I am not saying it’s impossible to do. It just needs work and we don’t seem to find the time to work on this. Your quickest way to achieve what you want is capture/deploy an image at your FOG network site. Don’t let the deployed host boot into the OS (add kernel parameter shutdown=1 to that host). Then boot that same host up with Clonezilla (for example) and for taking a backup that can be deployed at an offline site on USB - no FOG server needed there - just the Clonezilla boot media and image on portable drive. (cross references: 1, 2, 3)

If that’s not what you want you need to dive into the details. Just quoting Junkhacker’s postfrom another topic here:

FOG image capture and deploy are multi-step processes. each are several commands that rely on scripts and programs in the FOG OS (FOS) and change based on what options you have selected. FOG images are not designed to be used stand alone. Using FOG images without a FOG server will require steps that were expected to be automated and there really isn’t a quick way around it.

So if you or anyone else is keen, you want to start looking at the commands to do this here:

Clear old partition table: https://github.com/FOGProject/fos/blob/master/Buildroot/board/FOG/FOS/rootfs_overlay/usr/share/fog/lib/funcs.sh#L2012 Apply new partition table: https://github.com/FOGProject/fos/blob/master/Buildroot/board/FOG/FOS/rootfs_overlay/usr/share/fog/lib/funcs.sh#L2041 Loop to do the restore: https://github.com/FOGProject/fos/blob/master/Buildroot/board/FOG/FOS/rootfs_overlay/usr/share/fog/lib/funcs.sh#L2376 Finally call partclone deploy the image files one by one: https://github.com/FOGProject/fos/blob/master/Buildroot/board/FOG/FOS/rootfs_overlay/usr/share/fog/lib/funcs.sh#L760 Restore UUID information: https://github.com/FOGProject/fos/blob/master/Buildroot/board/FOG/FOS/rootfs_overlay/usr/share/fog/lib/partition-funcs.sh#L25 Possibly more things I have missed…

And that’s just the simple case without resizing partitions!

It’s all open source, it’s all yours!

@faboulous said in 20.04 autoinstall:

If someone manage to do so, it would be interesting to check what is_casper_path and matches_uuid does and return.

I don’t have a setup to dive in this right now and so I just started looking at the code. But maybe that’s of any help to you too.

Looking at the definition of is_caspar_path I get the impression that there is no possible way for this to return 0 (true in bash logic) to actually proceed to the next check.

Edit: Ok, forget what I said here. This is using bash globbing to expand filenames when a file exists matching the glob used.

Anyhow, I figured out why it would not return successful from the do_nfsmount() call. It checks UUIDs that are stored within the ISO in path .../.disk/casper-uuid*. Now when we prepare things and copy contents from the ISO we are missing that hidden folder (starting with a dot)! To fix that run the following command on your FOG server with the ISO mounted in /mnt/loop:

cp -R /mnt/loop/.disk /images/os/mint/20

I’m able to PXE boot into the Mint20 XFCE Live system with that fix on a VirtualBox VM (hosted on Debian 10) with only 768 MB of RAM set for the VM.

@george1421 We might think about switching to rsync -a /mnt/loop/ /images/os/... in your great tutorials on PXE booting installers to prevent that from happening. What do you think?

@londonfog I just tried Ubuntu Server 20.04 as well and it is working fine too - even using kernel and initrd from the ISO and not download the netboot ones! The important part is that you need to copy the .disk folder over as mentioned above.

@george1421 : Right !

I removed all offending spaces and voilà !

Thank you very much .

PS : By the way i noticed the error also occurs when i select multiple entries as : default item.

@sebastian-roth we may have found a workaround since we have a uefi/bios co-existence setup, we are trying to legacy boot to capture/deploy the uefi image. It appears to have worked. I am not sure I want to pursue this issue further since it is a very old model and a one off case.

I appreciate your help on the matter regardless, thank you.

@rodluz you can try this, https://forums.fogproject.org/topic/6463/expose-fog-host-and-image-properties-to-post-install-scripts?_=1620751811503 and make a review of host, image and hostinventory items…

@fernando-gietz thanks

@adamhyla89 said in 11th Gen Intel Kernel:

it states cannot open ` /var/www/fog/service/bzImage’ (no such file or directory)

Better copy & paste the commands to not miss anything. So again: file /var/www/html/fog/service/ipxe/bzImage* /var/www/fog/service/ipxe/bzImage*

The install on the VM is only command line, no GUI for Ubuntu.

There is no GUI (for Ubuntu) needed as you can access the FOG web UI from another computer. I guess you have used it already because how would you manage FOG or even get past the schema update when you don’t access the FOG web UI.

@ice4192 Like this?
https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence

@SomeWeirdRandomDude Please post the full fog.log from that client here.

By the way, which version of FOG and the fog-client do you use?

@wayne-workman said in FOG Project call for engagement:

For the exact OSs graph, only the top 20 are shown. I can change it to show more, but the graph bars will start getting really thin.

Ah, good to know. I think the top 20 will do.

@sebastian-roth yes, right… and just FYI, I got it working once I followed the instructions on the link you’ve sent me, thanks man!

@colej Which version of FOG do you use?

@ngriffith29 With FOG you usually register hosts (at least you need to if you want FOG to rename them) and there you define the hostname it will use after deployment. So it’s just up to you to name the hosts accordingly.

@fred06 You need to use an imaging Task. You selected “Debug” task, which was not what @george1421 was requesting.

Host -> Tasks -> Deploy -> Check the box for Schedule as Debug

@greg-plamondon I’m looking at the iso image and I think we should be able to pxe boot it.

In the tftp root directory create a dir to hold your files.

mkdir -p /tftpboot/os/port

Copy from the iso image /boot/vmlinuz and /boot/initrd.xz to /tftpboot/os/port on the fog server.

Then you will want to create a new FOG iPXE menu similar to this

Menu Item: os.Porteus.Kiosk
Description: Porteus Kiosk 5.2.0
Parameters:
kernel tftp://${fog-ip}/os/port/vmlinuz
initrd tftp://${fog-ip}/os/port/initrd.xz
imgargs vmlinuz initrd=initrd.xz quiet first_run
boot || goto MENU
Menu Show with: All Hosts

Lets see what that does for you. We may have to tweak the image args because I see a parameter of http_server= in the syslinux config but its not in the grub config.

@d2freak82 said in Certificate Nightmare:

on install if I select HTTPS it will not install because of the certificate error.

Even when using the updated SmartInstaller mentioned below?

Where exactly do you see the certificate error? Can you post a screenshot? Possibly it’s something we can/need to fix in the fog-client setup.

@sborgne said in (503) Service unavailable:

Proxy parameters bad config is to be blamed…

Wow, something I would not have thought of right away! Good you found why it fails!

No there are no proxy configuration settings in fog-client. We use simple C# .NET WebClient calls. That seams to be using your system proxy settings. Can you set your systemwide proxy settings to not use the proxy server if connecting to your FOG server?

@john3892 Assuming you installed FOG via git, please run:

cd /path/to/fogproject #change this to where it is actually located git checkout dev-branch git pull cd bin ./installfog.sh -y

This issue should be addressed.

Thank you,