@sebastian-roth
Thank you for the appreciation!

Also maybe I just overlooked something, maybe edited wrong host, as I had multiple tabs and didn’t keep track of it. Otherwise I don’t see any other reason for it not working on the first try.

@sebastian-roth unfortunately I do not get shell after pressing enter. This is what I get instead

@sebastian-roth try this https://drive.google.com/file/d/1I_LFCwT0INMzg8vHbbi60KSqvYHtNDKN/view?usp=sharing

@wayne-workman Yes thank you, video answer alot.

@lcsmd Thank you for reporting back on how to get it working. When adding it to the wiki I figured out it uses the “ASIX AX88179” chip and we had some of the Startech devices listed in the “Notes” column already. So I added your USB31000SPTB to that list as well to be found by others - including the hint to use a different iPXE binary.

I have to say the list is not really up to date. Mainly the notes are not because it’s a lot of work to keep it up with information from forum posts only. Nor do we have time and resources to test all the hardware ourselves.

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

@krishna Using a random screenshot and not explain it costed you two days by pointing to the wrong direction. The clearer your information is the more we are able to help you.

OK, so this is a normal single master FOG node setup and we can rule out routing because FOG server and PXE booting clients are all in the same subnet?

So you have the firewall disabled in the FOG server?

Where clients ever able to PXE boot to the menu? If yes, when did it work last and what changed since then?

About the access.log - I just figured that Ubuntu moved to a different name at some point. Please run tail -f /var/log/apache2/*.log while you PXE boot one client to see if it shows up in the log.

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

if [ "$(echo $path/$LIVE_MEDIA_PATH/*.squashfs)" != "$path/$LIVE_MEDIA_PATH/*.squashfs" ] || ...

This just doesn’t make sense to me. How would those two strings ever be different?! The extra echo should not make a difference. But maybe this is some bash hack I don’t understand. Tested in a simple script is_casper_path just never returns 0 for me.

@Tom-Elliott so I truncated the tables and re-created the jobs - one I created via Basic Tasks -> Advanced -> Wake up, and one I created through the Power Management window. Here’s the resulting database entries for Day of Week and Day of Month from both:

MariaDB [fog]> select stDOM,stDOW from scheduledTasks\G *************************** 1. row *************************** stDOM: * stDOW: 1-5 1 row in set (0.001 sec) MariaDB [fog]> select pmDom,pmDow from powerManagement\G *************************** 1. row *************************** pmDom: * pmDow: 1-5 1 row in set (0.000 sec)

So it’s looking good now. As you can see in my previous database entry, I had 1-5 entered under pmDom, which was likely the issue. I’m giving this point to user error.
Thanks again for your help!

@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

@aloniada Interesting. I have not tried it myself as I don’t use live OS booting. Just trying to help with what I find on the web. I would imagine the parameter can go pretty much anywhere in the imgargs line.

When you moved it to different positions, did you always get the exact same error message. I can’t think of why iPXE would grab that out of the imgargs line…

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