@Hongyun I have this exact same error but in my case the UUID not found is my / which is my boot partition. Too bad your post remains unanswered. BTW, if you are still around, are your partition(s) EXT by chance? I’m using Rocky 8.10.

FOG iPXE meu is doing cert validation check at some point. Where would I need to change so it can verify my cert?
I’m on Rhel 9 running apache 2.4. No error on any of the log file.

Please help!!!

@robertkwild This is ours, it boots into Windows automatically, where FOG starts (using the startup script) and renames the PC and adds to domain

<?xml version="1.0" encoding="utf-8"?> <unattend xmlns="urn:schemas-microsoft-com:unattend"> <settings pass="windowsPE"> <component name="Microsoft-Windows-International-Core-WinPE" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <SetupUILanguage> <UILanguage>en-GB</UILanguage> </SetupUILanguage> <InputLocale>en-GB</InputLocale> <SystemLocale>en-GB</SystemLocale> <UILanguage>en-GB</UILanguage> <UILanguageFallback>en-US</UILanguageFallback> <UserLocale>en-GB</UserLocale> </component> <component name="Microsoft-Windows-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <DiskConfiguration> <WillShowUI>OnError</WillShowUI> <Disk wcm:action="add"> <CreatePartitions> <CreatePartition wcm:action="add"> <Order>1</Order> <Size>500</Size> <Type>Primary</Type> </CreatePartition> <CreatePartition wcm:action="add"> <Order>2</Order> <Type>EFI</Type> <Extend>false</Extend> <Size>100</Size> </CreatePartition> <CreatePartition wcm:action="add"> <Order>3</Order> <Size>16</Size> <Type>MSR</Type> </CreatePartition> <CreatePartition wcm:action="add"> <Extend>true</Extend> <Order>4</Order> <Type>Primary</Type> </CreatePartition> </CreatePartitions> <ModifyPartitions> <ModifyPartition wcm:action="add"> <Format>NTFS</Format> <Label>WinRE</Label> <Order>1</Order> <PartitionID>1</PartitionID> <TypeID>DE94BBA4-06D1-4D40-A16A-BFD50179D6AC</TypeID> </ModifyPartition> <ModifyPartition wcm:action="add"> <Format>FAT32</Format> <Label>System</Label> <Order>2</Order> <PartitionID>2</PartitionID> </ModifyPartition> <ModifyPartition wcm:action="add"> <Order>3</Order> <PartitionID>3</PartitionID> </ModifyPartition> <ModifyPartition wcm:action="add"> <Format>NTFS</Format> <Label>Windows</Label> <Letter>C</Letter> <Order>4</Order> <PartitionID>4</PartitionID> </ModifyPartition> </ModifyPartitions> <WillWipeDisk>true</WillWipeDisk> <DiskID>0</DiskID> </Disk> </DiskConfiguration> <ImageInstall> <OSImage> <InstallTo> <DiskID>0</DiskID> <PartitionID>4</PartitionID> </InstallTo> </OSImage> </ImageInstall> <UserData> <ProductKey> <Key>**REDACTED**</Key> </ProductKey> <AcceptEula>true</AcceptEula> <Organization>**REDACTED**</Organization> </UserData> <Display> <HorizontalResolution>1920</HorizontalResolution> <VerticalResolution>1080</VerticalResolution> </Display> </component> </settings> <settings pass="specialize"> <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <ComputerName>*</ComputerName> <RegisteredOwner>**REDACTED**</RegisteredOwner> <RegisteredOrganization>**REDACTED**</RegisteredOrganization> <TimeZone>GMT Standard Time</TimeZone> </component> </settings> <settings pass="oobeSystem"> <component name="Microsoft-Windows-International-Core" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <InputLocale>en-GB</InputLocale> <SystemLocale>en-GB</SystemLocale> <UILanguage>en-GB</UILanguage> <UILanguageFallback>en-US</UILanguageFallback> <UserLocale>en-GB</UserLocale> </component> <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <OOBE> <HideEULAPage>true</HideEULAPage> <HideOEMRegistrationScreen>true</HideOEMRegistrationScreen> <HideOnlineAccountScreens>true</HideOnlineAccountScreens> <HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE> <ProtectYourPC>1</ProtectYourPC> </OOBE> <UserAccounts> <LocalAccounts> <LocalAccount wcm:action="add"> <Password> <Value>**REDACTED**</Value> <PlainText>false</PlainText> </Password> <Description>Admin</Description> <DisplayName>Admin</DisplayName> <Group>Administrators</Group> <Name>Admin</Name> </LocalAccount> </LocalAccounts> </UserAccounts> <Display> <HorizontalResolution>1920</HorizontalResolution> <VerticalResolution>1080</VerticalResolution> </Display> <AutoLogon> <Password> <Value>**REDACTED**</Value> <PlainText>false</PlainText> </Password> <Username>Admin</Username> <LogonCount>1</LogonCount> <Enabled>true</Enabled> </AutoLogon> <FirstLogonCommands> <SynchronousCommand wcm:action="add"> <CommandLine>C:\Windows\Setup\scripts\SetupComplete.cmd</CommandLine> <Order>1</Order> <RequiresUserInput>false</RequiresUserInput> </SynchronousCommand> </FirstLogonCommands> </component> </settings> <cpi:offlineImage cpi:source="wim:c:/customise/win10/sources/install11edu.wim#Windows 11 Education" xmlns:cpi="urn:schemas-microsoft-com:cpi" /> </unattend>

@JJ-Fullmer said in HTTPS Redirect Web GUI:

https redirect

I had this issue, but wanted to add to the Copilot answer that works on RHEL 8.10 running the latest Apache and FOG 1.5.10.1634 (this assumes you installed FOG with NO HTTPS option, in other words HTTPS disabled by default):

To redirect all HTTP requests on port 80 to HTTPS on port 443 using your provided certificate and key, you can use the following configuration:

Create a new configuration file in the /etc/httpd/conf.d/ directory, for example, redirect.conf:

<VirtualHost *:80> ServerName ip.of.fog.server ServerAlias hostnameOfFogServer RewriteEngine On RewriteCond %{HTTPS} off RewriteRule ^(.*)$ https://%{HTTP_HOST}$1 [R=301,L] </VirtualHost>

Update your SSL configuration in the /etc/httpd/conf.d/ssl.conf file to include your certificate and key:

<VirtualHost *:443> ServerName ip.of.fog.server ServerAlias hostnameOfFogServer DocumentRoot /var/www/html/ SSLEngine on SSLCertificateFile /opt/fog/ssl/UNIQUE-FOR-ME/MYCERT.cer SSLCertificateKeyFile /opt/fog/ssl/UNIQUE-FOR-ME/MYCERT.key <Directory /var/www/html/fog/> DirectoryIndex index.php index.html index.htm AllowOverride All Require all granted </Directory> <FilesMatch "\.php$"> SetHandler "proxy:fcgi://127.0.0.1:9000/" </FilesMatch> RewriteEngine On RewriteCond %{REQUEST_METHOD} ^(TRACE|TRACK) RewriteRule .* - [F] RewriteCond %{DOCUMENT_ROOT}/%{REQUEST_FILENAME} !-f RewriteCond %{DOCUMENT_ROOT}/%{REQUEST_FILENAME} !-d RewriteRule ^/fog/(.*)$ /fog/api/index.php [QSA,L] </VirtualHost>

Restart Apache to apply the changes:

sudo systemctl restart httpd

This configuration will redirect all HTTP requests to HTTPS and use the provided certificate and key for SSL. Make sure to replace ip.of.fog.server and hostnameOfFogServer with your actual server IP and hostname.

Lastly, When enrolling a cert I used the FQDN and plain hostname as a “Subject Alternative Name”. For my company, this means internal use only (.pvt). This takes care of both redirects (prob could have also talked to the DNS team to redirect the hostname to the FQDN eg hostname.blah.pvt as well. But it’s better (and faster) in the cert if you can do it that way.

@Tom-Elliott i had the exact same error on another pc i wanted to image, you were right Tom, as the CMOS battery died it had the wrong date/time so i amde it correct and voila

thanks for pointing me in the right direction!!!

@Tom-Elliott Which information would help you to understand the problem more?

Secure Boot is disabled at the moment.

@robertkwild ok i read you can do 10 or other so fine, il close

Hi @Tom-Elliott. Do you know which settings do I need to change so outgoing email is not coming from Apache?
I changed the outgoing email for FROM EMAIL and EMAIL BINARY in the web UI to donotreply@mydomain.com. Notification email went out as apache@myfogserver.localdomain. I then set myorigin = mydomain.com in main.cf, I received the notification from donotreply@mydomain.com which looks correct but according to maillog, and full header of the email, the email was sent from apache@mydomain.com.

@Tom-Elliott I have tried what you said without success. I still get the TFTP error

@Tom-Elliott
The last problem was tha windows main partition ! Now it works perfectly ! Thx for your precious help.

Solved 🙂

@NoIPName

Hey !

like @Tom-Elliott says , 1.5.10-x is the good way but if your problem is still present so i would ask you this :

from Fog GUI could you export in CSV your actual hosts list ? could you add in this CSV a new line changing the hostname and mac values could you clean all your hosts from Fog GUI could you import the CSV that you exported

is it working ?

@rodluz

@Erika said in Issue : EFI Stub: initrd data into pcr 9:

@rodluz said in Issue : EFI Stub: initrd data into pcr 9:

@Erika I would like to try the newer 6.12 kernel to see if this issue would get resolved. I will have a kernel for you to try later today.

My colleague and I tried this morning,
It doesn’t work.

bzimage 6.12.png
6.12.png

efi stub: loaded initrd from linux_efi_initrd_media_guid device path
measured initrd data into pcr 9

Does’nt works on this video : (hosted 2 day)
https://streamable.com/dlqhin

When it works normally, it should go to this step as in the video :
https://streamable.com/esg8f0

@rogalskij said in OS Details no longer working:

For those experiencing the same issue on mainstream linux distros, navigate to your “resolv.conf” config file located in /etc/resolv.conf and add your individual search domains. Test a ping to a DNS name via command line on the box itself, then check your GUI again. Took about 2 minutes for it to reflect and show for me.

I’ve just done this, and now noticing a remarkable increase in performance of the 1.6 web page. Thank you!

First of all, sorry for resurrecting this old thread. However … I was experiencing this issue with HP machines with BIOS U62 Ver.01.01.21 07/01/2024.

The only way I was able to workaround the issue is by using refind binaries from FOG 1.5.5 as @PeterL says in their answer:

@PeterL said in REFInd-Initializing - hangs:

Your issue with rEFInd is because of HPs EFI.
I have exactly the same issue with ProDesk 400 for quite some time.
The workaround to get those systems booting via rEFInd was a downgrade of the rEFInd binaries.

For me a downgrade to rEFInd out of the FOG 1.5.5 package did the trick.

FOG 1.5.5

Path in the ZIP archive: fogproject-1.5.5.zip\fogproject-1.5.5\packages\web\service\ipxe\refind.efi

The binary is dated 15.11.2018

On a Debian system place the file in /var/www/html/fog/service/ipxe
Once as “refind.efi” and a second time as “refind_x64.efi”.

But I’ve tried with latest rEFInd version from sourceforge as @george1421 points in their answer

@george1421 said in REFInd-Initializing - hangs:

@peterl FWIW the refind files can be located here: https://sourceforge.net/projects/refind/files/

For a very log time FOG shipped with 0.11.0 version of refind. This was a very stable, but old release. Based on the image date you referenced that must be the 0.11.4 release of refind. You might also want to try 0.13.2 (newest at the time of writing). To see if the very latest version of refind works for you.

but even this latest version isn’t able to boot the EFI partition from the internal disk. So weird, not sure how may I help to diagnose this issue for rEFInd project … but I’d like to help. Can’t find a way to increase verbosity for rEFInd despite I’ve tried some config directives in refind.conf

Thank you for this helpful post guys 😛

@aurfalien I’m sorry, I am generally working in working-1.6 and even there I was mistaken.

The file you’re looking for is likely /var/www/fog/lib/fog/host.class.php.

It follows similar rules though the line you’d want changed would be at 2199 I think.

Hopefully this helps?

Hey @george1421 , Thanks for the quick reply, sorry for the missing details.

What device is your dhcp server? (manufacturer and version)

DHCP (and DNS) is running on an Active Directory 10.0.20348.1668, Windows Server 2022 Standard

Is it on the same subnet as the FOG server? You mentioned the VM and FOG server was on the same subnet.

This applies to any machine I’ve tried to deploy to from fog, for example fog is on subnet 100, unless the target of the deploy is specifically on subnet 101 it will fail to boot into the PXE server. Even with a Workstation/VM on subnet 100 (exactly the same subnet as the fog server) it will without fail time out this will happen on any subnet other than 101. In our case VLANs will correspond to Subnets.

Any machine on the 101 subnet can pxe boot to fog to capture and deploy with no issue with both UEFI and BIOS.

What hypervisor are you using?

We have found that we will see this issue whether on a VM or a Workstation so this isn’t limited to the hypervisor in question.

I assume when you say “run PXE” you are saying you are trying to pxe boot the VM?

Yes, correct.

Is the VM in bios or uefi mode?

We have tried both with the same result for either.

What specifically do you have defined for dhcp option 66 and 67?

For the two DHCP Policies we have in place for fog we have the following options set for 66d and 67:

FOG snponly.efi policy
66: 10.2.100.103 (IP address of our fog server)
67: snponly.efi

FOG ipxe.efi
66: 10.2.100.103 (IP address of our fog server)
67: ipxe.efi

@AUTH-IT-Center Hi thanks for the reply.

Yes I’ve read that link, my problem is that I’ve done the password migrations “backwards” - ie I’ve copied the passwords from the database to .fogsettings instead of the other way around as specified on that link.

@wilsol you’re downgrading the kernel version, not FOG. These versions exist and while generally having the bleeding edge is fine, sometimes the bleeding edge is … well… problematic. Will there be a fix? Most likely, when we know exactly what’s causing and can produce a patch, notify the kernel development team what we find, or disable the offending piece once we know what it is and what (if any) it impacts by being disabled. Until then, using the slightly older version is the workaround/fix.