OP is using Windows 7 as capture image, so Fast Boot won’t be able to cause issues here (since it doesn’t have that option anyway).

I recommend running a chkdsk /f on the Windows partition to start with. Might also want to do a SMART check as some sectors may be defective.

I’ll post a script to make your own WinPE on Monday. It does require you to have Windows AIK, but you can just download that from Microsoft.

It allows you to automatically map your network drive and even launch setup with arguments. It all depends on what kind of setup you want of course, but hopefully you’ll at least get some insight in how to approach the situation with it.

It will always say to update the database scheme, even if it’s not necessary, you can just continue.

I’m not 100% sure, but I believe you will not be on RC11 unless it’s specifically instructed to install that, since it’s still being worked on and not ready for release.

It might be worthwhile to try a different boot file (eg ipxe.pxe instead of undionly.kpxe) as well.

Some devices need a different boot binary to load correctly.

Try ipxe.pxe instead of undionly.kpxe for example

@echo off

rem The fileserver IP
set FILESERVER=192.168.1.155

rem Share on the fileserver.
set SHARE=INSTALLERS\ISOFILES\0-WINPE

rem Username for the share
set SHAREUSER=root

rem Password for the share
set SHAREPASS=root

rem amd64 or x86
set ARCH=amd64

rem Path to hold working files. Needs about 500MB of free space.
set PEPATH="c:\winpe_%ARCH%"

rem ##########################################################
rem     Don't edit anything below here
rem ##########################################################
 
echo Creating the PE image
call copype.cmd %ARCH% %PEPATH% > NUL
 
echo Mounting the image
dism /Mount-Wim /WimFile:%PEPATH%\media\sources\boot.wim /index:1 /MountDir:%PEPATH%\mount /quiet
 
echo Adding commands to the startup script in PE
echo. >> %PEPATH%\mount\windows\system32\startnet.cmd
echo ping %FILESERVER% >> %PEPATH%\mount\windows\system32\startnet.cmd
echo net use z: \\%FILESERVER%\%SHARE% %SHAREPASS% /u:%FILESERVER%\%SHAREUSER% >> %PEPATH%\mount\windows\system32\startnet.cmd
echo z: >> %PEPATH%\mount\windows\system32\startnet.cmd
echo z:\64.bat >> %PEPATH%\mount\windows\system32\startnet.cmd
 
echo Creating the pxeboot directory
mkdir %PEPATH%\pxeboot > NUL
mkdir %PEPATH%\pxeboot\Fonts > NUL
copy /y %PEPATH%\mount\windows\boot\Fonts\*.* %PEPATH%\pxeboot\Fonts\ > NUL
copy /y "%WinPERoot%\%ARCH%\Media\Boot\boot.sdi" %PEPATH%\pxeboot\ > NUL
copy /y "%WinPERoot%\%ARCH%\Media\Boot\BCD" %PEPATH%\pxeboot\ > NUL
 
echo Unmounting the image
dism /unmount-Wim /MountDir:%PEPATH%\mount /Commit /quiet
 
echo Optimizing the image
imagex /EXPORT %PEPATH%\media\sources\boot.wim 1 %PEPATH%\pxeboot\boot.wim > NUL
 
 
echo.
echo All the files you need for your PXE server are in: %PEPATH%\pxeboot\

This script needs to be called from the Deployment and Images Tool Environment command prompt.

I based myself on http://www.wcooke.org/wiki/Installing_Windows_using_PXELINUX but modified it since certain things didn’t work (it would create a corrupt BCD when there’s a perfectly fine working one included with WinPE) and other things were unnecessary.

If you make changes to the script and call it again make sure to delete the target directory first or your startnet.cmd will get messed up!

edit: Added ping command to give network drivers time to load before attempting to mount the network location.

@apathetic_admin I recommend doing the SQL query Wayne suggested instead.

UPDATE `hosts` SET `hostEnforce`='1';

@jj-fullmer https://www.rodsbooks.com/refind/configfile.html

Sets the volume that's used for subsequent file accesses (by icon and loader, and by implication by initrd if loader follows volume). You pass this token a filesystem's label, a partition's label, a partition's GUID, or a volume number. A filesystem or partition label is typically displayed under the volume's icon in file managers and rEFInd displays it on its menu at the end of the boot prompt string. If this label isn't unique, the first volume with the specified label is used. The matching is nominally case-insensitive, but on some EFIs it's case-sensitive. If a filesystem has no label, you can use a partition GUID number. You can also use a volume number followed by a colon, such as 0: to refer to the first filesystem or 1: to refer to the second. The assignment of numbers is arbitrary and may not be consistent across boots, though. It might change if you insert an optical disc or plug in a USB flash drive, for instance. If this option is not set, the volume defaults to the one from which rEFInd launched.

It’s possible I read too much into it and assumed that the “aribtrary” part had to do with the boot order in BIOS, maybe it has more to do with how refind interprets it instead?

Is Bitlocker enabled?

Any specific reason for using this over resizable?

@george1421 You don’t need the FOG storage node installer to make storage nodes work, but some functionality (like the available size pie chart) won’t be available. If you have NFS and FTP properly setup you can use the device as storage node pretty much, at least in my experience.

@davido38 I was able to replicate the issue on my end, seems like a bug, unless I’m missing something.

Try has_usb_nic=1 as a host kernel argument under the host settings.

@Fimlore You have to change the path in a couple of places

The storage node image path has to be adjusted on the WebGUI of the server.

Then on the server itself:

/opt/fog/.fogsettings : storageLocation

If you let FOG build exports automatically, then just rerun the installer after that change.

If not, you have to edit /etc/exports

Do be careful of ownership and permissions in a shared image location.

@Varion Am I correct in assuming you followed instructions on this page: https://wiki.fogproject.org/wiki/index.php/Installation_on_Debian_Lenny to install fog?

You might want to (temporarily) disable firewall on FOG server to see if that helps.

A note about other Linux distribution

If you are using other Linux distribution such as Debian / Ubuntu / Suse / Slakcware Linux etc., try the following generic procedure. First, save the current firewall rules, type:
iptables-save > /root/firewall.rules

OR
$ sudo iptables-save > /root/firewall.rules

Next, type the following commands (login as the root) as bash prompt:

iptables -F
iptables -X
iptables -t nat -F
iptables -t nat -X
iptables -t mangle -F
iptables -t mangle -X
iptables -P INPUT ACCEPT
iptables -P OUTPUT ACCEPT
iptables -P FORWARD ACCEPT

Mod edited to use code box.

@Tom-Elliott My guess is he has already edited it so that the problem doesn’t appear anymore.

I just checked, and the default french layout does have problems on login page.

However, the better solution, imo, would be to edit the css

Specifically

#login-form label

Its width is coded to 80px right now, setting it instead to 100% seems to work much better.

It will rearrange it so the labels are on top of the fields, which may not be desirable, however. But it seems the translations to French make the content of the labels too big for the current layout.

Because they’re marked as ODD, they might be on a different controller altogether and possibly with more limited functionality too.

Virtualbox does not support UEFI PXE booting.

You can still capture an UEFI image by disabling EFI mode and booting into PXE as per usual.

@Sebastian-Roth It’s likely caused by the autofill feature of certain browsers, would it be possible to add that to the wiki so people are aware that every time they make changes to the storage nodes that they have to enter their actual password?

You have set two different nodes as master node in the same Storage Group. This will cause all sorts of issues, only one node can be master node in a group.

@bigjim Your dnsmasq config is outdated if you’re using the a newer version. (and UEFI + BIOS proxydhcp didn’t work at all on older versions)

dhcp-boot=tag:UEFI32,i386-efi/ipxe.efi,10.5.0.240

dhcp-boot=tag:UEFI,ipxe.efi,10.5.0.240

dhcp-boot=tag:UEFI64,ipxe.efi,10.5.0.240

The syntax tag: is no longer valid and needs to be replaced with net:

https://wiki.fogproject.org/wiki/index.php?title=ProxyDHCP_with_dnsmasq#Install_dnsmasq_on_CentOS_7 for reference

It’s confusing because there’s info on both older versions of dnsmasq and the newer ones, but likely this is the cause.