Posts made by Killklli

@george1421 It’s really a rather fascinating issue. Absolutely nothing but iPXE seems to be the case. I really wonder what section of the iPXE boot slows it down, please update this when you get a chance haha.

@george1421 Went and spent some time on it.

About 3-4 seconds for load into ipxe
Everything plugged in, basic UEFI launch - 28 seconds
things unplugged. Video card still in - 29 seconds.

USB EFI boot - Unable to get boot. Tried both making a file and downloading the existing ipxe file from webserver. Stalls at iPXE initializing devices.
Unsure what to do.

USB FOS -

Made from Fog Server- Unable to boot through UEFI, only legacy. (Does that have to do with the fog server running legacy?) Instant, no delay.
Second install from UEFI Ubuntu- UEFI boots. Almost instant boot time.

Both boots from legacy or UEFI both load these at about the same pace.

Takes about 3 seconds to load the kernel and virtual drive
About 4 seconds to get to the network loading
About 3 seconds to load the network
About 1s for the rest.

It just seems rather strange with such a jump in time. I’m seeing the DHCP packet and download at relatively the same rate as legacy. It’s just the rate at IPXE boot. It just seems strange that the same device that it boots in legacy are adding such a large amount of time to the boot in UEFI.
While I would just not have it in the boot order and do it legacy just for imaging, I’m a student at a college in the Comp Sci department. We have a room of just our computers and at the rate these things get re imaged to different operating systems, its simpler to have in the boot order.
I feel like the next step I should try is disconnecting everything including the hard drive to see if I can see a discernible difference in boot time from either peripheral hardware or if its based off the board itself.

So I have a dhcp proxy that is pushing out the UEFI and Legacy boot files.
( https://github.com/FOGProject/node-dhcproxy )
Everything works fine no transfer issues, nothing.

However, I am wondering. The time that it takes Legacy to go from ipxe initializing devices is much faster compared to the UEFI version.
It all works, I just find it strange that the UEFI version takes about 8-15 seconds longer compared to the Legacy version.
I’ve tried with multiple versions of the boot files. Has anyone found a quicker boot file? or some sort of setting that would speed up the UEFI boot time? (Other than going back to legacy)

@Junkhacker I had multiple hard drives I was trying to image at once and once this issue started popping up I actually did switch to re sizable but it was still having that issue strangely.

@Uncle-Frank That seems to be the case. The drives themselves had DBAN run on them so it might just assume pre existing partitions. Not default info.

@Uncle-Frank After doing some heavy messing around with the images I was deploying it seems that for some reason the size of the image was an issue. Even though every computer has the same hard drive and have all been wiped, lowering the image size by 50 more GB (instead of leaving the 10gb padding I had before) fixed it. I used 50GB as a brute test to see it it worked and its strange that it did. Considering the 1tb drive should have taken over no matter what. So I put the 1tb drive in another computer and it imaged fine in there. It seems to just be a strange image size issue.

@sudburr I’ve tried DBAN on both. I’d be surprised if both started failing at the exact same time.

@Uncle-Frank

@Uncle-Frank

@Wayne-Workman Its a Multiple Partition Image - All Disks (Not Re sizable) It was made on the 250 @Uncle-Frank I’ll check in the morning.

@Uncle-Frank For some reason gdisk -l does not like me. @Wayne-Workman The two hard drives I have are a 250gb ssd and a 1tb HDD all of the other machines have the same drives. I tried rotating through the sata cables to see if order mattered but it did not work.

@Tom-Elliott Doing a FULL wipe fixed it for me. Wiping my database and everything and starting over fixed it.

@Uncle-Frank I’ll try to get an image but here is the exact process of what happens.

1. I set the task for the computer to download the image and it WOL’s the computer
2. The computer loads up to PXE and loads ipxe
3. The computer boots into the usual imaging options (Before it gets to the blue Imaging screen)
4. All of the sub options say done almost instantly and the client says the imaging is complete and it is restarting.
5. When I go back to the web interface the task is no longer on the task list as if the process was successful.

EDIT
The image was hard to get because it happens within a few seconds.

On one computer out of a mass of 10 computers that are all the same specs is having an issue where it loads and loads the imaging options but when I go to image it says done to all of the steps instantly and restarts without actually imaging but clears it from the task list. I’m using the latest SVN trunk and Ubuntu 14.04

@Tom-Elliott Even as is with updating multiple times since then. (Both on Git and SVN) I’m still having the issue.

@Tom-Elliott I think you want the error log? error.log Its while two machines are stuck trying to download an image. All of the other files on this thread just seem to be renditions of that file as far as I can tell.

@Tom-Elliott Jumping on the wagon a bit right here. I’m still having the issue as well. I just upgraded the GIT version and am still having the checking in timeout and tried the SVN version as well and it has the same issue.

@Wayne-Workman Just for when you get back to this. It still didn’t work. Still getting PXE-E18: Server Response Timeout for UEFI machines. But Legacy Works.

@Wayne-Workman I’m still confused that for whatever reason I’m not even seeing the UEFI boot grabbing IP’s. I just get a server timeout.