Quick or Full Host Registration fails - screen goes black

[kinger37]

@george1421 Hi George - I just had it work - without doing an updates - not sure what changed. The only that i did try was doing the Legacy boot after scheduling a task to capture the image. I am going to try a straight from the factory 7040 and see what happens.

If it fails again though I will update firmware and FOG trunk.

Thanks again for all your help!

[Wayne Workman]

Just my personal experience - FOG Trunk from a month ago and a 7040sff out of the box worked fine. We are using them in UEFI mode, but are using legacy for network booting.

[kinger37]

@george1421 @Wayne-Workman I have just updated to the latest SVN 5858 and updated the firmware of the 7040 to 1.4.4 - wasnt getting a plain black screen anymore but kept failing on registration “An Error has been detected” “Cannot find disk on system”

Solution to that issue was in my BIOS\UEFI settings - under Device Config-Sata Operation: Raid On was enable and I had to change it to AHCI.

Testing deploying a image right now.

[Wayne Workman]

@kinger37 #wiki worthy

[kinger37]

@kinger37 Deployment was successful - I think I have it working now - thank you for everyones help.

@TOM ELLIOTT On my first time booting into FOG PXE menu I receive the chainloading error, but after rebooting and going back in - it doesnt show up again.

[george1421]

@kinger37 said in Quick or Full Host Registration fails - screen goes black:

@TOM ELLIOTT On my first time booting into FOG PXE menu I receive the chainloading error, but after rebooting and going back in - it doesnt show up again.

I have to say I saw that at random when I was testing too. I was doing 3 things at a time and just thought I missed something when I turned back. The time I actually watched the booting process it booted normally. So there may be a timing issue that is just on the edge of working. It will be interesting to know your production experience with this configuration.

[Tom Elliott]

How many hosts are there in your environment both of you?

I don’t think it’s timing but kind of is. If there were an error in code it would show up everytime for all machines. It would not show up randomly on even the same machine. Just a guess but I believe what you guys are seeing is inability to connect to the database due to meeting max connection limits of db and/or Apache max limits.

[george1421]

@Tom-Elliott In my case it was on the dev box so only 2 or 3 systems were connected. Unfortunately I did not see what the error was only when I turned around I saw the chain loading error. I rebooted it without turning it off and watched it and the iPXE menu came up. Could have been a fluke or the update to the latest trunk today, or booting these 7040s in efi mode. I don’t do efi on any system in our production environment so I can’t comments other than I saw the results of the error twice during iPXE booting.

[Tom Elliott]

Do you see the same thing if booting in legacy mode? I’m going to guess a network uplink bug may be present and can’t load up the nic to enable it to get to network. This means it can’t boot to find the menu and subsequently gets an error returned causing it to fail. I wonder if this only happens on these systems from cold boot status?

[george1421]

@Tom-Elliott I still have my test system setup. I’ll try different combinations in the morning to see if I can get it to fail while I’m watching it.

[kinger37]

@Tom-Elliott Sorry for the delay - I am on an isolated network for my FOG Server - so right now only 3 machines in the FOG environment.