Posts made by quinniedid

@george1421 The VMware version that we are running is 6.5 Build 5973321

@Sebastian-Roth This is what it is getting hung up on:

I removed the SCSI controller, in this case the LSI controller that it was complaining about and the long delay has now been resolved.

What I don’t understand is why this happens only on an UEFI boot vs a BIOS boot. The BIOS boot doesn’t have issues with the SCSI hard drive nor the SCSI controller.

Any ideas on that?

Officially, it will work if the controller on the VM hard drive is set to use SATA instead of the default SCSI. SCSI works on BIOS but not on EFI.

Is there a way to reduce the timeout on the smbus issue? It really is close to 10 minutes before it does anything.

@Wayne-Workman @Sebastian-Roth Finally able to get a fresh VM built. I am getting the same error that it cannot find the HardDisk. I will try changing the controller and see what happens. Its just strange that this behavior exists on EFI and not on BIOS.

I will do some testing with a single VM no configuration with EFI.

As for the controller it should be an LSI SCSI adapter. This does work and I am able to capture the UEFI image if I switch back to BIOS to run the capturing for the VM. It does not work so far with UEFI booting FOG.

PXE booting using EFI is not an issue. It is able to advance and Windows loads as expected. The issue is when capturing an image we get the following error after about 10 minutes of a black screen:

Then we get the following error:

We are using 4.11.0 for the bzImage. We are running FOG version 1.4.4 Rev:6077

Any ideas on what I could do to resolve this?

@Tom-Elliott @george1421 Moving those folders and running the installer again has resolved the issues. Thank you again!

@george1421 Here is the results of a manual registration and deploy:

#!ipxe
set fog-ip 10.86.96.177
set fog-webroot fog
set boot-url http://${fog-ip}/${fog-webroot}
kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 web=10.86.96.177/fog/ consoleblank=0 rootfstype=ext4 acpi=off mac=00:26:55:3f:14:45 ftp=10.86.96.177 storage=10.86.96.177:/images/ storageip=10.86.96.177 osid=9 irqpoll hostname=TEST-PC chkdsk=0 img=DISTWIN10 imgType=n imgPartitionType=all imgid=1 imgFormat=0 PIGZ_COMP=-9 hostearly=1 type=down acpi=off
imgfetch init_32.xz
boot

@george1421 Here are the settings that are currently configured.

@Troye-Johnson If you have that PC registered, would you try adding in the Host Kernel Arguments: acpi=off

You can find that by going to Host Management and selecting the individual host and applying that option.

I have found that to be a big deal with these HP workstations.

@george1421 Apologies for the vague details. The menu comes up now and is able to boot to the first hard drive. It was not able to do that till yesterday which you helped me with resolving. Now the issue is after I select Deploy Image and login, I do get a list of all the images. It is not until I select an image to deploy that this message comes up.

@george1421 This is the same PC’s that I have used before in the past to image, should be BIOS. For DHCP, I am using undionly.kpxe.

@george1421 I have run into one more problem. I cannot image anything. This is the error that I am getting:

Could not select: Exec format error (http://ipxe.org/2e008001)
Could not boot: Exec format error (http://ipxe.org/2e008001)
Chainloading failed, hit’s for the iPXE shell

Any ideas?

@george1421 That was it!!!

Thank you so much for your time on this!!!

@george1421 I think we found it!

Is there supposed to be anything else populated in those fields?

The fields are all populated in settings. I even clicked on save changes again and checked the file and it is still showing the same thing.

That is correct. This PC along with hundreds of others that are the same have all been working. It is just as of late nothing is now working in regards to FOG. In fact we just went through a huge re-image process over the course of a month with FOG. Now can’t get it past the iPXE menu nor for it to allow me to select an image to deploy.

There was some changes in regards to the global kernel arguments and I was trying to activate the advanced menu but have since moved those settings back to default.

#!ipxe
set fog-ip
set fog-webroot
set boot-url http://${fog-ip}/${fog-webroot}
cpuid --ext 29 && set arch x86_64 || set arch i386
goto get_console
:console_set
colour --rgb 0x00567a 1 ||
colour --rgb 0x00567a 2 ||
colour --rgb 0x00567a 4 ||
cpair --foreground 7 --background 2 2 ||
goto MENU
:alt_console
cpair --background 0 1 ||
cpair --background 1 2 ||
goto MENU
:get_console
console --picture http:///fog/service/ipxe/hp.png --left 100 --right 80 && goto console_set || goto alt_console
: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)
choose --default fog.local --timeout 3000 target && goto ${target}
:fog.local
chain -ar ${boot-url}/service/ipxe/grub.exe --config-file="rootnoverify (hd0);chainloader +1" || goto MENU
:fog.memtest
kernel memdisk initrd=memtest.bin iso raw
initrd memtest.bin
boot || goto MENU
:fog.reginput
kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 web=/ consoleblank=0 rootfstype=ext4 acpi=off storage=10.86.96.177:/images/ storageip=10.86.96.177 loglevel=4 mode=manreg
imgfetch init_32.xz
boot || goto MENU
:fog.reg
kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 web=/ consoleblank=0 rootfstype=ext4 acpi=off storage=10.86.96.177:/images/ storageip=10.86.96.177 loglevel=4 mode=autoreg
imgfetch init_32.xz
boot || goto MENU
:fog.deployimage
login
params
param mac0 ${net0/mac}
param arch ${arch}
param username ${username}
param password ${password}
param qihost 1
isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
:fog.multijoin
login
params
param mac0 ${net0/mac}
param arch ${arch}
param username ${username}
param password ${password}
param sessionJoin 1
isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
:fog.sysinfo
kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 web=/ consoleblank=0 rootfstype=ext4 acpi=off storage=10.86.96.177:/images/ storageip=10.86.96.177 loglevel=4 mode=sysinfo
imgfetch init_32.xz
boot || goto MENU
:bootme
chain -ar http:///fog/service/ipxe/boot.php##params ||
goto MENU
autoboot

For clarification this is the iPXE menu, in the past it has worked with no issues (last time it worked was a little over a week ago).

Regardless of the selection on the iPXE menu it goes back to the menu. I am using a HP Compaq tower. I also have VM’s that have worked in the past with no issues with the iPXE behaving the same way. I wonder if there is corruption that has happened in the menu items files?

Here is the list of files:

total 38156
drwxr-xr-x 3 fog www-data 4096 Jul 10 12:03 .
drwxr-xr-x 3 www-data www-data 4096 Jun 30 10:42 …
-rw-r–r-- 1 fog www-data 1966 Jun 30 10:42 advanced.php
drwxr-xr-x 2 fog fog 4096 Jul 10 12:03 backup
-rw-r–r-- 1 fog www-data 16272 Jun 30 10:42 bgdark.png
-rw-r–r-- 1 fog www-data 21280 Jun 30 10:42 bg.png
-rw-r–r-- 1 fog www-data 922 Jun 30 10:42 boot.php
-rwxr-xr-x 1 fog fog 0 Jul 10 11:59 bzImage
-rwxr-xr-x 1 fog fog 0 Jul 10 12:03 bzImage32
-rw-r–r-- 1 fog www-data 234697 Jun 30 10:42 grub.exe
-rw-r–r-- 1 fog www-data 46896 Apr 26 08:19 hp.png
-rw-r–r-- 1 fog www-data 592 Jun 30 10:42 index.php
-rw-r–r-- 1 fog www-data 18646084 Jun 30 10:43 init_32.xz
-rw-r–r-- 1 fog www-data 19605632 Jun 30 10:43 init.xz
-rw-r–r-- 1 fog www-data 25340 Jun 30 10:42 memdisk
-rw-r–r-- 1 fog www-data 1839104 Jun 30 10:42 memtest.bin
-rw-r–r-- 1 fog www-data 20976 Jun 30 10:42 refind.conf
-rw-r–r-- 1 fog www-data 205192 Jun 30 10:42 refind.efi

Server

• FOG Version: 1.4.4
• OS: Ubuntu 16.04.2 LTS

Client

• Service Version:
• OS:

Description

I am having an issue to where when the client PC’s PXE boot the background image is not loaded but the menu does appear. The issue is any selection from the menu results in it going back to the menu making a never ending loop as boot to hard disk is supposed to be selected. The kernel versions in my GUI are showing up blank. Tried to download the latest kernel and even went back to 4.11 and is still failing to appear. I have also tried to run the installer again to see if it would have fixed the issue.

Is there any logs that I can collect? I am totally at a loss at this point, so anything would be greatly appreciated!

Thank you!

@george1421 I have removed the the global parameters and still exhibiting the same behavior. It is weird that this happened right after I made that change. I think something might have gotten corrupted, but I am not sure what to do at this point.