To create a menu in the advanced one, you must fill it in under iPXE General Configuration -> Advanced Menu Settings > Advanced Menu Commands

example:

:urls
set msdart-url http://192.168.1.155/2-MSDART
:MENU
menu
colour --rgb 0xff0000 0 ||
cpair --foreground 1 1 ||
cpair --foreground 0 3 ||
cpair --foreground 4 4 ||
item --gap -- -------------------------------------
item fog.local Boot from hard disk
item msdart6x86 Microsoft DaRT for Windows Vista 32bit
item msdart6x64 Microsoft DaRT for Windows Vista 64bit
item msdart7x86 Microsoft DaRT for Windows 7 32bit
item msdart7x64 Microsoft DaRT for Windows 7 64bit
item msdart81x86 Microsoft DaRT for Windows 8.1 32bit
item msdart81x64 Microsoft DaRT for Windows 8.1 64bit
item fog.return Return to previous menu
choose --default fog.local --timeout 5000000 target && goto ${target}
:fog.local
sanboot --no-describe --drive 0x80 || goto MENU
:msdart6x86
initrd ${msdart-url}/MSDaRT60x86.iso
chain memdisk iso raw
:msdart6x64
initrd ${msdart-url}/MSDaRT60x64.iso
chain memdisk iso raw
:msdart7x86
initrd ${msdart-url}/MSDaRT70x86.iso
chain memdisk iso raw
:msdart7x64
initrd ${msdart-url}/MSDaRT70x64.iso
chain memdisk iso raw
:msdart81x86
initrd ${msdart-url}/MSDaRT8.1x86.iso
chain memdisk iso raw
:msdart81x64
initrd ${msdart-url}/MSDaRT8.1x64.iso
chain memdisk iso raw
:fog.return
chain http://${fog-ip}/${fog-webroot}/service/ipxe/boot.php?mac=${net0/mac} ||
prompt
goto MENU

I’m guessing the Windows 10 installations are UEFI based, so change the UEFI boot to hard drive. I think rEFInd is most commonly used for UEFI.

I got the same error on Windws 7 machines trying to clone them using Resizable. Single disk Multiple Partition worked fine and since they were all the same systems it worked out for me, though still curious why Resizable was having issues.

I’m on latest RC as per usual. (1.5.0-RC9), although it was a few RC’s back when this happened I believe.

edit: I should note that these weren’t prepared in the ‘usual way’, that is to say, I first deployed W7 to them and then installed updates and created an additional user and such. No sysprep either.

You’re not supposed to edit the init files.

Intead, you should go to the FOG Webui, FOG Configuration -> iPXE Menu Item Settings and then click on fog.deployimage and add

set username foglogin
set password foglogin

To the very beginning

@jonathan-cool Dynamic or Static? (Dynamic could cause issues, not to mention it’s slow)

You do seem to have a lot of empty space in your virtual environment, but this shouldn’t really impact the deployment process, imo.

Resizable image type should be able to resize it correctly.

Don’t try to mount it on your FOG server (it won’t work), just configure the Storage Node page with the relevant info of the NAS itself. (ip, FTP username and password, images location) and it should work fine.

@sebastian-roth I have had the same issue on a Windows 7 installation (had been in use for maybe a year) which we had to clone as it was.

Non-resizable worked fine, resizable failed with the inode message.

edit: Sorry I can’t be more helpful than that, it was the only instance I could recall and of course I am not sure what they did on those computers.

edit2: It could have been hardware related, they had been in use for a while, after all. (although SMART certainly didn’t complain). And of course did chkdsk /r and such with no change. (and no errors found)

@sebastian-roth Probably a good idea to include that in the announcement when it comes.

In boot.php do you see your item listed under the :MENU: entry?

@zer0cool Not what I mean. In Boot.php there is a :MENU entry that will have a structure like so:

:MENU
menu
colour --rgb 0xff0000 0 ||
cpair --foreground 1 1 ||
cpair --foreground 0 3 ||
cpair --foreground 4 4 ||
item --gap Host is NOT registered!
item --gap -- -------------------------------------
item fog.local Boot from hard disk
item fog.memtest Run Memtest86+
item fog.reginput Perform Full Host Registration and Inventory
item fog.reg Quick Registration and Inventory
item fog.deployimage Deploy Image
item fog.multijoin Join Multicast Session
item fog.sysinfo Client System Information (Compatibility)

If your entry isn’t part of the :MENU then it will never show in PXE boot.

Perhaps a silly question, but is there sufficient room left on your partitions? (df -h)

@nuit It is probable that SELinux is the culprit here. I believe it is disabled by default on Debian (correct me if I’m wrong).

Maybe the SELinux configuration for vsftpd isn’t set correctly.

Try setenforce 0 and see if that helps. May have to restart the ftp service.

@sebastian-roth I don’t know if I’m interpretating the files incorrectly, but shouldn’t d1.minimumpartitions
and d1.partitions files be different under resizable in terms of size for the partitions? It looks like it noted the same size in both scenarios for the Data partitions, so the problem seems to be that during capture the system thinks it can’t resize it.

@dhenken Only one way to figure out. Uninstall Deep Freeze and see if that changes the situation after capture.

There’s a good chance that’s what’s blocking though.

Probably https://github.com/FOGProject/fogproject/commit/8c3e8e006c31449fb8334f532bfb46a80fa0f407 these changes to Apache configuration.

As far as I understand, if the file or directory isn’t found by Apache it will redirect to fog/api/index.php
(which will redirect to fog/management/index.php if it’s not an API request afaik)

Make sure ownership and permissions match the other folders (check with something like ls -la)

It seems like a lot of requests are getting 302 redirected, not sure if that’s intentional.

@zer0cool I think it will redirect anything with url/fog so try going one directory higher.

@lebrun78 1.4.4 FOG installer doesn’t have support for PHP-FPM on Rhel based systems (or if it does, it’s missing fixes introduced later afaik).

It should be possible to get it sorted manually, something like this:

https://forums.fogproject.org/topic/10717/can-php-fpm-make-fog-web-gui-fast

Is that 24.5GB of RAM?

And apache2 is using most of it?

What about php or php-fpm?

Did you manually change some of the apache settings?

What does apache2ctl -l show?

Seems to be the same problem as experienced here:

https://forums.fogproject.org/topic/12036/centos7-fog-1-5-3-image-capture-fails-with-incorrect-date-timezone-info

@zer0cool Can you create a phpinfo page?

Something like

nano /var/www/html/fog/phpinfo.php

<?php
phpinfo();
?>

Save and exit, then navigatie to your fogserver/fog/phpinfo.php

Do ctrl+f ‘timezone’ and tell me what you see in that section.

I’m kind of scratching my head over here, because things are working fine for me, though php reports my timezone being blank.