@george1421 I was able to change that file to an earlier version and it appears to have fixed our UEFI issue on our newer HP PC’s
@JJ-Fullmer Please let me know what I can provide in testing if needed
@george1421 I was able to change that file to an earlier version and it appears to have fixed our UEFI issue on our newer HP PC’s
@JJ-Fullmer Please let me know what I can provide in testing if needed
@george1421 @JJ-Fullmer I am more than happy to do some testing. Please provide me instruction on what is needed and the debug information that is needed and I can provide some time to testing. Thanks for all of your help.
And to answer the question I am unsure how to change the rEFId version in FOG to make this work for this hardware but we do have a workaround by using BIOS for now till we get this issue resolved.
@JJ-Fullmer We have found something very interesting. If we use rEFInd version 0.10.9 we are able to get the menu and we are able to select Windows from there with no issues. If we go to 0.11.X or higher we run into issues of it not finding Windows and would get stuck on “Scanning for boot loader”. We even went so far to copy the refind.conf file that was on fog our to our rEFInd USB and it booted to Windows without any issues. We have also tried the other things that you have posted with no further of a result.
@george1421 So now that we finally had access to the menu and to the shell we were able to issue the command that you requested
@jj-fullmer We tried to make the recommended changes to the refind.conf file and have tried several paths based on the navigation we used through the BIOS side to the .efi file and all results have come back with it not being able to find anything. Tried both: \EFI\Microsoft\Boot\bootmgfw.efi and \EFI\boot\bootx64.efi
@george1421 @JJ-Fullmer Thank you all for the info. To provide the most accurate information from the tech. There never was a menu option from rEFInd. The menu that was being accessed was from the HP BIOS to which there was no Windows Boot Manager to select but instead we had to drill down to the file and select it to boot. Normally without network boot it would boot just fine.
From what JJ was saying it appears that this is a known issue with these boxes and that we would instead have to use a local version of rEFInd. We have tried using a USB for this and has failed as well to find any boot devices and is simply hanging on Initializing. We have taken the HDD out of the ProDesk and into a known working PC and Windows did boot with network boot without any issues. This really points its finger back at the ProDesk.
If there is anything else you would recommend that we try at this point to troubleshoot? I will try to prob the rEFInd community as well to see if they have some solutions.
George we are working on gathering that information and I will post back with that information shortly. From what I have seen we never have any menu or options to select from like you described but we will try to find that or at least try to figure out how to make the menu appear.
@Szeraax I appreciate you pointing that out. Normally this would be a concern but what we have found is when you install Windows 10 on a new hardware, even if the hardware is the same, Windows 10 will go into a getting your PC ready setup. EDIT (CORRECTION): When configuring the image we will not activate Windows with its key but continue to use the generic key that is associated with Windows 10 for our golden image. We also utilize MAK keys which is not a concern for us in that regard.
@george1421 So it appears that installing 1803 has not fixed this issue that we are experiencing. I have tried to add that path to the refind.conf file for it to find something to boot with but it has failed. What else would you recommend us to try at this point?
@george1421 Okay. So I downloaded that ISO and it still is doing the exact same thing. For more clarification after talking with the technician, it appears that Windows Boot Manager does not show up in the boot menu of the PC. Instead he has to select boot from file, find the driver and drill down to EFI/boot folder to start Windows. What is interesting is that when remove network boot out of the equation it boots straight to the operating system without any issue. We are currently in the process of installing 1803 on the PC to see if it resolves this issue. But so far I am guessing that it won’t as something else is going on with UEFI for some reason on this box.
@george1421 0_1528141994949_refind.conf.txt
This is the latest one which because we just updated FOG I do believe is the default. I have just downloaded the refind and will test that and see what the results are. I will also see what directory we have to go to. I just saw where we can specify that in the refind.conf
@george1421 No. What we usually end up having to do was hit ESC and it went to the boot menu and we had to select boot from file, and navigate down to the .efi boot file.
@george1421 I am having issues getting stuck on “rEFInd - Initializing and scanning for drives”. Do you think what you mentioned in https://forums.fogproject.org/topic/12016/stuck-on-ipxe-initializing-devices/9 will work for us? Or is that different?
@Zer0Cool Our process is we have a domain account already setup on the “golden” image. All we do to prepare the OS for being imaged is simply remove it from the domain and pull the image. It is actually really nice this way. When the PC is joined back to the domain on whatever PC it gets put on all of the user settings and customization is still in place for that domain user. We have a local administrator account that we setup so that we can always login to the PC regardless.
Also when you join a computer to the domain it will automatically perform a gpupdate. In fact this happens every time a PC is restarted. Also, unless you have a GPO that block you from being able to login to a local account, you can always login even after being joined to the domain. You can do this with either .\USERNAME
or COMPUTERNAME\USERNAME
@Zer0Cool Have you thought about not using sysprep at all? Get a clean image without AD, and just take that base image and apply it to all your computers that are identical.
We do this specifically with Windows 10 as we have applications that will not work with sysprep and we can put the image on whatever hardware we want; great feature to Windows 10. Windows 7 is a bit more finicky and that if too much is different it will just blue screen.
We have a HP ProDesk 600 G3 and it is failing to PXE boot and we are getting stuck on the rEFInd - Initializing page. The OS boots just fine if we do not network boot. We have made several changes to refind.conf to try and get around this but have been unsuccessful.
This refind.conf is working great on our other new HP Pavilion 570-p015z, but it seems that we might be running into hardware issues.
We have tried making some changes that was done from this post: https://forums.fogproject.org/topic/11897/boot-loop-after-imaging-uefi/29
We are running fog 1.5.3
Kernel versions:
bzImage Version: 4.16.6
bzImage32 Version: 4.16.6
0_1527786960910_refind.conf.txt
Let me know what other information you would like me to gather.
Thank you for the help. It is greatly appreciated.
@Sebastian-Roth Yes it does return. I even see a ton of data being downloaded. I have cut off the data towards the end due to the length of the capture.
563 13.682607 10.86.96.177 10.85.195.199 TCP 74 50514 > 8080 [SYN] Seq=0 Win=29200 Len=0 MSS=1460 SACK_PERM=1 TSval=1729539897 TSecr=0 WS=128
569 13.742557 10.85.195.199 10.86.96.177 TCP 78 8080 > 50514 [SYN, ACK] Seq=0 Ack=1 Win=65535 Len=0 MSS=1460 SACK_PERM=1 TSval=400875488 TSecr=1729539897 WS=64
570 13.742594 10.86.96.177 10.85.195.199 TCP 66 50514 > 8080 [ACK] Seq=1 Ack=1 Win=29312 Len=0 TSval=1729539912 TSecr=400875488
571 13.742693 10.86.96.177 10.85.195.199 HTTP 161 CONNECT fogproject.org:443 HTTP/1.1
575 13.801898 10.85.195.199 10.86.96.177 TCP 66 [TCP Window Update] 8080 > 50514 [ACK] Seq=1 Ack=1 Win=771008 Len=0 TSval=400875548 TSecr=1729539912
576 13.864407 10.85.195.199 10.86.96.177 HTTP 105 HTTP/1.1 200 Connection established
577 13.864424 10.86.96.177 10.85.195.199 TCP 66 50514 > 8080 [ACK] Seq=96 Ack=40 Win=29312 Len=0 TSval=1729539942 TSecr=400875608
579 13.87112 10.86.96.177 10.85.195.199 TLSv1.2 583 Client Hello
582 13.992592 10.85.195.199 10.86.96.177 TLSv1.2 1414 Server Hello
583 13.992609 10.85.195.199 10.86.96.177 TCP 166 8080 > 50514 [PSH, ACK] Seq=1388 Ack=613 Win=771008 Len=100 TSval=400875738 TSecr=1729539944 [TCP segment of a reassembled PDU]
584 13.992616 10.86.96.177 10.85.195.199 TCP 66 50514 > 8080 [ACK] Seq=613 Ack=1488 Win=32128 Len=0 TSval=1729539974 TSecr=400875738
585 13.992893 10.85.195.199 10.86.96.177 TCP 1414 8080 > 50514 [ACK] Seq=1488 Ack=613 Win=771008 Len=1348 TSval=400875738 TSecr=1729539944 [TCP segment of a reassembled PDU]
586 13.992908 10.85.195.199 10.86.96.177 TCP 166 8080 > 50514 [PSH, ACK] Seq=2836 Ack=613 Win=771008 Len=100 TSval=400875738 TSecr=1729539944 [TCP segment of a reassembled PDU]
587 13.992916 10.86.96.177 10.85.195.199 TCP 66 50514 > 8080 [ACK] Seq=613 Ack=2936 Win=35072 Len=0 TSval=1729539974 TSecr=400875738
588 13.992928 10.85.195.199 10.86.96.177 TLSv1.2 640 Certificate, Server Key Exchange, Server Hello Done
589 13.995298 10.86.96.177 10.85.195.199 TLSv1.2 192 Client Key Exchange, Change Cipher Spec, Encrypted Handshake Message
593 14.114585 10.85.195.199 10.86.96.177 TLSv1.2 117 Change Cipher Spec, Encrypted Handshake Message
594 14.114752 10.86.96.177 10.85.195.199 TLSv1.2 182 Application Data
598 14.237584 10.85.195.199 10.86.96.177 TCP 1414 8080 > 50514 [ACK] Seq=3561 Ack=855 Win=771008 Len=1348 TSval=400875988 TSecr=1729540005 [TCP segment of a reassembled PDU]
599 14.237599 10.85.195.199 10.86.96.177 TCP 166 8080 > 50514 [PSH, ACK] Seq=4909 Ack=855 Win=771008 Len=100 TSval=400875988 TSecr=1729540005 [TCP segment of a reassembled PDU]
600 14.237607 10.86.96.177 10.85.195.199 TCP 66 50514 > 8080 [ACK] Seq=855 Ack=5009 Win=40704 Len=0 TSval=1729540036 TSecr=400875988
......
.....
....
...
@Sebastian-Roth Sorry. I was able to download them from the GUI before and now I am getting that error but it was a while since I last updated the kernels. So I am not sure which version of fog this issue was introduced. I want to say I was able to download new kernel through the GUI for the GUI look changed…
@Sebastian-Roth Yes we do on the proxy aspect. wget does work as I had already set the proxy for wget on the server. I just didn’t know where the kernels were to download. Thank you for the info. I was able to download the new kernels. Just not sure why I was able to before and not now…
[Wed May 23 10:45:06.684444 2018] [mpm_prefork:notice] [pid 5789] AH00163: Apache/2.4.33 (Ubuntu) OpenSSL/1.1.0h configured -- resuming normal operations
[Wed May 23 10:45:06.684485 2018] [core:notice] [pid 5789] AH00094: Command line: '/usr/sbin/apache2'
[Wed May 23 11:45:42.336598 2018] [proxy_fcgi:error] [pid 14134] [client 10.86.96.177:35102] AH01071: Got error 'PHP message: PHP Notice: A non well formed numeric value encountered in /var/www/fog/status/bandwidth.php on line 109\nPHP message: PHP Notice: A non well formed numeric value encountered in /var/www/fog/status/bandwidth.php on line 109\nPHP message: PHP Notice: A non well formed numeric value encountered in /var/www/fog/status/bandwidth.php on line 110\nPHP message: PHP Notice: A non well formed numeric value encountered in /var/www/fog/status/bandwidth.php on line 110\n'
[Wed May 23 11:45:43.510798 2018] [proxy_fcgi:error] [pid 14578] [client 10.86.96.177:35106] AH01071: Got error 'PHP message: PHP Notice: A non well formed numeric value encountered in /var/www/fog/status/bandwidth.php on line 109\nPHP message: PHP Notice: A non well formed numeric value encountered in /var/www/fog/status/bandwidth.php on line 109\nPHP message: PHP Notice: A non well formed numeric value encountered in /var/www/fog/status/bandwidth.php on line 110\nPHP message: PHP Notice: A non well formed numeric value encountered in /var/www/fog/status/bandwidth.php on line 110\n'
[Wed May 23 11:45:44.667104 2018] [proxy_fcgi:error] [pid 14616] [client 10.86.96.177:35110] AH01071: Got error 'PHP message: PHP Notice: A non well formed numeric value encountered in /var/www/fog/status/bandwidth.php on line 109\nPHP message: PHP Notice: A non well formed numeric value encountered in /var/www/fog/status/bandwidth.php on line 109\nPHP message: PHP Notice: A non well formed numeric value encountered in /var/www/fog/status/bandwidth.php on line 110\nPHP message: PHP Notice: A non well formed numeric value encountered in /var/www/fog/status/bandwidth.php on line 110\n'
[Wed May 23 11:45:45.839950 2018] [proxy_fcgi:error] [pid 14578] [client 10.86.96.177:35114] AH01071: Got error 'PHP message: PHP Notice: A non well formed numeric value encountered in /var/www/fog/status/bandwidth.php on line 109\nPHP message: PHP Notice: A non well formed numeric value encountered in /var/www/fog/status/bandwidth.php on line 109\nPHP message: PHP Notice: A non well formed numeric value encountered in /var/www/fog/status/bandwidth.php on line 110\nPHP message: PHP Notice: A non well formed numeric value encountered in /var/www/fog/status/bandwidth.php on line 110\n'
[Wed May 23 11:45:47.010823 2018] [proxy_fcgi:error] [pid 14619] [client 10.86.96.177:35118] AH01071: Got error 'PHP message: PHP Notice: A non well formed numeric value encountered in /var/www/fog/status/bandwidth.php on line 109\nPHP message: PHP Notice: A non well formed numeric value encountered in /var/www/fog/status/bandwidth.php on line 109\nPHP message: PHP Notice: A non well formed numeric value encountered in /var/www/fog/status/bandwidth.php on line 110\nPHP message: PHP Notice: A non well formed numeric value encountered in /var/www/fog/status/bandwidth.php on line 110\n'
[Wed May 23 11:53:25.534623 2018] [proxy_fcgi:error] [pid 10213] [client 10.4.137.110:60924] AH01071: Got error 'Primary script unknown\n'
[Wed May 23 11:53:25.881624 2018] [core:error] [pid 10188] [client 10.4.137.110:60956] AH00135: Invalid method in request NQVVSJ / HTTP/1.1
[Wed May 23 11:53:33.995252 2018] [proxy_fcgi:error] [pid 13933] [client 10.4.137.110:33712] AH01071: Got error 'Primary script unknown\n'
[Wed May 23 12:07:34.390353 2018] [php7:error] [pid 16290] [client 10.86.100.10:47518] script '/var/www/html/fog/service/oucheck.php' not found or unable to stat
[Wed May 23 12:08:32.234661 2018] [proxy_fcgi:error] [pid 16784] [client 10.86.96.179:4774] AH01071: Got error 'PHP message: PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 20480 bytes) in /var/www/fog/lib/fog/fogcontroller.class.php on line 125\n', referer: http://10.86.96.177/fog/management/index.php?node=host&sub=edit&id=10
[Wed May 23 12:08:51.587106 2018] [proxy_fcgi:error] [pid 16838] [client 10.86.96.179:4784] AH01071: Got error 'PHP message: PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 16384 bytes) in /var/www/fog/lib/fog/fogcontroller.class.php on line 260\n', referer: http://10.86.96.177/fog/management/index.php?node=host&sub=edit&id=10
[Wed May 23 12:09:00.066726 2018] [proxy_fcgi:error] [pid 16829] [client 10.86.96.179:4793] AH01071: Got error 'PHP message: PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 16384 bytes) in /var/www/fog/lib/fog/fogcontroller.class.php on line 260\n', referer: http://10.86.96.177/fog/management/index.php?node=host&sub=edit&id=193
[Wed May 23 12:38:48.981164 2018] [proxy_fcgi:error] [pid 19398] [client 10.86.96.177:39210] AH01071: Got error 'PHP message: PHP Notice: A non well formed numeric value encountered in /var/www/fog/status/bandwidth.php on line 109\nPHP message: PHP Notice: A non well formed numeric value encountered in /var/www/fog/status/bandwidth.php on line 109\nPHP message: PHP Notice: A non well formed numeric value encountered in /var/www/fog/status/bandwidth.php on line 110\nPHP message: PHP Notice: A non well formed numeric value encountered in /var/www/fog/status/bandwidth.php on line 110\n'
[Wed May 23 12:38:50.148312 2018] [proxy_fcgi:error] [pid 19523] [client 10.86.96.177:39214] AH01071: Got error 'PHP message: PHP Notice: A non well formed numeric value encountered in /var/www/fog/status/bandwidth.php on line 109\nPHP message: PHP Notice: A non well formed numeric value encountered in /var/www/fog/status/bandwidth.php on line 109\nPHP message: PHP Notice: A non well formed numeric value encountered in /var/www/fog/status/bandwidth.php on line 110\nPHP message: PHP Notice: A non well formed numeric value encountered in /var/www/fog/status/bandwidth.php on line 110\n'
[Wed May 23 12:38:51.323148 2018] [proxy_fcgi:error] [pid 19522] [client 10.86.96.177:39220] AH01071: Got error 'PHP message: PHP Notice: A non well formed numeric value encountered in /var/www/fog/status/bandwidth.php on line 109\nPHP message: PHP Notice: A non well formed numeric value encountered in /var/www/fog/status/bandwidth.php on line 109\nPHP message: PHP Notice: A non well formed numeric value encountered in /var/www/fog/status/bandwidth.php on line 110\nPHP message: PHP Notice: A non well formed numeric value encountered in /var/www/fog/status/bandwidth.php on line 110\n'
[Wed May 23 12:38:52.492377 2018] [proxy_fcgi:error] [pid 19398] [client 10.86.96.177:39224] AH01071: Got error 'PHP message: PHP Notice: A non well formed numeric value encountered in /var/www/fog/status/bandwidth.php on line 109\nPHP message: PHP Notice: A non well formed numeric value encountered in /var/www/fog/status/bandwidth.php on line 109\nPHP message: PHP Notice: A non well formed numeric value encountered in /var/www/fog/status/bandwidth.php on line 110\nPHP message: PHP Notice: A non well formed numeric value encountered in /var/www/fog/status/bandwidth.php on line 110\n'
[Wed May 23 12:38:53.666840 2018] [proxy_fcgi:error] [pid 19397] [client 10.86.96.177:39232] AH01071: Got error 'PHP message: PHP Notice: A non well formed numeric value encountered in /var/www/fog/status/bandwidth.php on line 109\nPHP message: PHP Notice: A non well formed numeric value encountered in /var/www/fog/status/bandwidth.php on line 109\nPHP message: PHP Notice: A non well formed numeric value encountered in /var/www/fog/status/bandwidth.php on line 110\nPHP message: PHP Notice: A non well formed numeric value encountered in /var/www/fog/status/bandwidth.php on line 110\n'
[Wed May 23 12:38:54.842805 2018] [proxy_fcgi:error] [pid 19522] [client 10.86.96.177:39236] AH01071: Got error 'PHP message: PHP Notice: A non well formed numeric value encountered in /var/www/fog/status/bandwidth.php on line 109\nPHP message: PHP Notice: A non well formed numeric value encountered in /var/www/fog/status/bandwidth.php on line 109\nPHP message: PHP Notice: A non well formed numeric value encountered in /var/www/fog/status/bandwidth.php on line 110\nPHP message: PHP Notice: A non well formed numeric value encountered in /var/www/fog/status/bandwidth.php on line 110\n'
[Wed May 23 12:38:56.030016 2018] [proxy_fcgi:error] [pid 19397] [client 10.86.96.177:39256] AH01071: Got error 'PHP message: PHP Notice: A non well formed numeric value encountered in /var/www/fog/status/bandwidth.php on line 109\nPHP message: PHP Notice: A non well formed numeric value encountered in /var/www/fog/status/bandwidth.php on line 109\nPHP message: PHP Notice: A non well formed numeric value encountered in /var/www/fog/status/bandwidth.php on line 110\nPHP message: PHP Notice: A non well formed numeric value encountered in /var/www/fog/status/bandwidth.php on line 110\n'
[Wed May 23 13:05:32.918482 2018] [proxy_fcgi:error] [pid 21993] [client 10.86.96.177:41402] AH01071: Got error 'PHP message: PHP Notice: A non well formed numeric value encountered in /var/www/fog/status/bandwidth.php on line 109\nPHP message: PHP Notice: A non well formed numeric value encountered in /var/www/fog/status/bandwidth.php on line 109\nPHP message: PHP Notice: A non well formed numeric value encountered in /var/www/fog/status/bandwidth.php on line 110\nPHP message: PHP Notice: A non well formed numeric value encountered in /var/www/fog/status/bandwidth.php on line 110\n'
So far nothing useful or related from what I have seen.
I have tried some of the other things that were related to an earlier Kernel update issue. I validated that the password were the same between the TFTP server and the Storage Node. I also verified that the folder path to where the kernel sits is correct as well.
We are behind a proxy server as well. I have verified that the information is in the GUI in the Proxy Settings section.
Fog: 1.5.2
bzImage Version: 4.15.2
bzImage32 Version: 4.15.2
@jemerson93 Would you please provide what you did to resolve this issue?