REFInd-Initializing - hangs
-
@sebastian-roth Hi Sabastian, thank you so much for the save with fog, it is now back up and I am happy to say we still have the refind issue, happy I can be at that point. On testing it is just saying Chainloading failed , hit S. Should I still rename the file refind_x64.efi to refind.efi and copy that over. I am using the user I would normal use to log into the server with, then I run sudo -s to allow me to do things, the Winscp has the user details that I would normally log into the server with but I guess without sudo -s bit, it wont be able to do anything?
-
This post is deleted! -
@sebastian-roth I have now carried out everything you have listed and still have the same error with refind Chain loading failed hit s. As this is a new version of fog I will check all the other exit types, you never know!
-
@sebastian-roth Not sure if you get any of the donations but if you do, have a beer on me
-
@sebastian-roth having now tried all the various options of exit in the latest version of FOG I have had no luck, this is with the rEFInd.efi renamed and the latest X64 REFInd file copied over it (0132) and named rEFInd.efi. Should I now revert everything back to standard? Any advice as always gratefully accepted. To note, once it was using the REFInd exit version (the 0132 one) it still hung at initializing
-
This post is deleted! -
@trev-lchs said in REFInd-Initializing - hangs:
having now tried all the various options of exit in the latest version of FOG I have had no luck, this is with the rEFInd.efi renamed and the latest X64 REFInd file copied over it (0132) and named rEFInd.efi.
The case of the filenames do actually matter on Linux systems!! Not sure but that could be the problem now.
Beside that it’s very hard to help without knowing what exactly has been done. Maybe run the following commands and post output here so we know what it looks like at the moment:
ls -al /var/www/ ls -al /var/www/html/ ls -al /var/www/html/fog/service/ipxe/ -
@sebastian-roth HI Sabastian
please see belowroot@fog-03:~# ls -al /var/www/ total 20 drwxr-xr-x 4 root root 4096 Jul 23 14:23 . drwxr-xr-x 16 root root 4096 Dec 1 2016 .. drwxr-xr-x 10 www-data www-data 4096 Jul 23 14:25 fog drwxr-xr-x 2 root root 4096 Jul 23 10:00 html -rw-r--r-- 1 www-data www-data 52 Jul 23 14:23 index.phproot@fog-03:~# ls -al /var/www/html/ total 20 drwxr-xr-x 2 root root 4096 Jul 23 10:00 . drwxr-xr-x 4 root root 4096 Jul 23 14:23 .. lrwxrwxrwx 1 root root 13 Dec 1 2016 fog -> /var/www/fog/ -rw-r--r-- 1 root root 11321 Jul 23 10:00 index.htmlroot@fog-03:~# ls -al /var/www/html//fog/service/ipxe/ total 59412 drwxr-xr-x 3 fogproject www-data 4096 Jul 23 16:09 . drwxr-xr-x 3 www-data www-data 4096 Jul 23 14:23 .. -rw-r--r-- 1 fogproject www-data 1966 Jul 23 14:23 advanced.php drwxr-xr-x 2 fogproject fogproject 4096 Jul 23 16:09 backup -rw-r--r-- 1 fogproject www-data 16272 Jul 23 14:23 bgdark.png -rw-r--r-- 1 fogproject www-data 21280 Jul 23 14:23 bg.png -rw-r--r-- 1 fogproject www-data 1139 Jul 23 14:23 boot.php -rwxr-xr-x 1 fogproject fogproject 8950400 Jul 23 16:09 bzImage -rw-r--r-- 1 fogproject www-data 8398784 Jul 23 14:24 bzImage32 -rw-r--r-- 1 fogproject www-data 234697 Jul 23 14:23 grub.exe -rw-r--r-- 1 fogproject www-data 592 Jul 23 14:23 index.php -rw-r--r-- 1 fogproject www-data 20591048 Jul 23 14:24 init_32.xz -rw-r--r-- 1 fogproject www-data 21178512 Jul 23 14:24 init.xz -rw-r--r-- 1 fogproject www-data 25340 Jul 23 14:23 memdisk -rw-r--r-- 1 fogproject www-data 1839104 Jul 23 14:23 memtest.bin -rw-rw-r-- 1 www-data www-data 254216 Jul 23 07:46 refind2.efi -rw-r--r-- 1 fogproject www-data 202624 Jul 23 14:23 refind_aa64.efi -rw-r--r-- 1 fogproject www-data 29719 Jul 23 14:23 refind.conf -rw-r--r-- 1 fogproject www-data 262592 Jul 23 14:23 refind.efi -rw-r--r-- 1 fogproject www-data 201600 Jul 23 14:23 refind_ia32.efi -rw-r--r-- 1 fogproject www-data 208776 Jul 23 14:23 refind_x64.efiHope this is what you wanted, as always thanks for your help.
-
@sebastian-roth I am running about getting PCs ready to go before the next lot arrive, this is still important to us, but I am juggling things now, just so you don’t think I am not keen to get it fixed.
-
@Trev-lchs Ok, filesnames and paths all seem fine. Not sure what else you can try. As I said, some hardware does play with rEFInd and some don’t.
-
@sebastian-roth Thats a shame, I can capture from the PC and also write the Image to the PC, so I will just have to turn off boot from network until a refind file comes along that works I guess. Unless there are any other suggestions out there.
Sebastian thank you for all your time with this, if you should hear of anything or find out from another user what the fix might be, please do drop me a line if you can. Are you able to see the email address of members?
-
@Trev-lchs Have you played with the mentioned refind.conf yet? Search the forum for more hints in this topic.
Which versions of rEFInd have you tried? All of them?
-
@sebastian-roth Thanks Sebastian, to be honest, most of them, with exactly the same result. I will try the conf file and see if that is the answer. I have been busy unpacking and installing PCs for the last few days, I will let you know how I get on.
-
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.
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”. -
@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.
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”.As I’m not allowed to edit my own posts …
I’ve seen this issue on ProDesk 400G5, none the less I think it’s the same problem.
HPs EFI is a real PITA and besides the problem you observed you will (most likely) also stumble upon a changed boot order, once you deployed images to your hardware.There is a setting for WOL in the “internal devices” section in the EFI, where you most likely will want to setup “PXE” instead of “normal boot”. This way you will be able to remotely work with a machine by shutting it down, waking it up and have it reliably booting to FOG menu/task.
-
@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.
-
I did some testing with 0.13.2 and 0.11.4 and BOTH did not work.
0.11.4 files are dated “12.11.2018 21:13:xx”, size of the refind_x64.efi file 208 776 Bytes.
The binary in the FOG 1.5.5 package (refind.efi) is dated “15.11.2018 20:42:17”, size 205 192 Bytes.
Those are not the same files.
-
@peterl Thank you Peter, I will endeavor to do as suggested, currently I have settled for no general pxe boot/network boot on all the PCs, this is a pain, but just means I have to go to a pc locally to boot into fog to deploy an image and I cant just do it from the fog GUI.
-
@peterl Ton of thanks to you. I have the exact same model here and I have had this problem.
Now downgraded to rEFInd of fogproject-1.5.5 it is not stuck anymore on “rEFInd-Initializing…”, but it is stuck now on “Scanning for new boot loaders; Please wait…”
Have you made any changes to the refind.conf file?
Mine is set at:.... scanfor internal .... timeout -1 .... scan_delay 5 ....It is an improvement, we’re getting somewhere now and soon will solve this. So, thanks for sharing!
-
@Trev-lchs We are an all HP shop. We have to use rEFInd version 0.10.9 for all of our systems to boot correctly. This is definitely something with HP’s EFI setup.
I ran into this problem myself, which you can reference the post https://forums.fogproject.org/topic/11993/refind-pxe-booting-issue
Let me know if you were able to get this working with this version
